On Thu, 17 Sep 2015, grarpamp wrote:
Is there some reason "freebsd.org" and all it's subdomains don't immediately 302 over to https foreverafter?
Is there a reason to encrypt something that is completely public? Perhaps to allow the visitor to conceal the fact that they are interested in FreeBSD? That won't work, since the IP address of the server can't be encrypted. I feel like I am missing something.
dan feenberg _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "[email protected]"
