Make extra sure connections can never be sslv3 closes #1957

Right. The thing is, in order to support 256 bits, we need to have unlimited strength policy files in place. Those aren't normally shipped by default because there are still export restrictions for their use. Beyond that, Schneier also argues that 256 bit AES is actually less secure that 128 bit AES at various rounds. He [says](https://www.schneier.com/blog/archives/2009/07/another_new_aes.html):

> And for new applications I suggest that people don't use AES-256. AES-128 provides more than enough security 
> margin for the forseeable future.

So this makes us both at least equally secure and removes the hassle of dealing with unlimited strength policy files. We also don't ship with unlimited strength policy files regardless, so the 246 bit code path was never executed.