Closed lattera closed 3 years ago
Hi Shawn!
1/ I don't accept PRs, because the page is auto-generated, per the README
2/ As a test...
...fails with an invalid TLS certificate.
3/ I recommend addressing the redirect OR getting a certificate (regrettably, $$$, at the moment. Hopefully this will be fixed soon) and then submit an Issue.
Yeah, the reason for that is due to LetsEncrypt. I force all HTTP to HTTPS on that server. Since LetsEncrypt doesn't support .onion
, yet, the cert is for the actual domain (git-01.md.hardenedbsd.org
and hardenedbsd.org
). Right now, I can't prioritize spending Foundation money on an HTTPS cert we get for free.
So, with HardenedBSD being the only OS to cover the entire ecosystem with Tor Onion Service nodes, what's the best way to keep HardenedBSD listed in this repo without having to spend the financial resources we don't have?
What webserver are you running? Can you disable the coercion from HTTP to HTTPS when the Host:
header is one of your Onions?
(aside: there are ongoing efforts to obtain LetsEncrypt certs for V3 Onions which could use support: https://cabforum.org/pipermail/validation/2019-December/001385.html)
What webserver are you running? Can you disable the coercion from HTTP to HTTPS when the
Host:
header is one of your Onions?
Good idea. I'll give that a try and report back. Shouldn't be difficult. Thanks for the suggestion!
Any web links? Been looking for a good three days now still no luck
closed, integrated.
HardenedBSD has revamped its infrastructure. The old nodes were retired prior to the migration to the new nodes. This commit removes the new-defunct old nodes in favor of thew new ones.
Signed-off-by: Shawn Webb shawn.webb@hardenedbsd.org Reference: https://hardenedbsd.org/article/shawn-webb/2020-01-30/hardenedbsd-tor-onion-service-v3-nodes