Comment 6 for bug 1934155

I see that I overlooked the NEWS file. That's more detailed than I'm used to seeing. As I was just now skimming through it, it was clear that moves made to protect users from weak algorithms assumed they're on an untunneled connection, which is not always the case. Sometimes the SSL is just used for verification and the crypto is just redundant.

I should also mention that I struggled with the "no sslcertck" syntax. All the options I've been using to that point were "<key> <value>" format, and "no sslcertck" is an exceptional transpose of it. I first tried "sslcertck no" because I was sure the key-value wouldn't flip. But in fact the "keyword" really included a space. Coupled with the inconsistency of some keywords starting with "set", I felt I couldn't trust the man page. Adding to the confusion, some options take arguments and some do not, but the Keyword/Option Summary table doesn't show any BNF and it omits the <value> token, making so we have to work out from the wording of the "Function" column whether it's unary or takes an argument.

Anyway, I appreciate your help and I hope my feedback helps for future revisions.