Hi Jacek, thanks for the detailed reply.
On Fri, Mar 29, 2013 at 3:02 AM, Jacek Caban <ja...@codeweavers.com> wrote: > Each protocol has two kinds of enable/disable flags: "enabled" and > "disabled by default". Those have different default values for each > protocol and there are registry setting allowing to change each of them. > Only "enabled" protocols are used at all. This patch limits "enabled" > protocols to those that we can really support. If an application asks > schannel to use default set of protocols (which I'd expect them to do > unless they have a good reason), schannel will use all "enabled" protocols > that are not "disabled by default". An alternative to default set of > protocols is listing each allowed separately. > > This means that if protocol is "enabled" and "disabled by default" it > won't be used unless application explicitly asks for it. SSL2 is such a > protocol by default. Do you think we should do this differently? > Yes, my suggestion here is to explicitly disable SSL2 support altogether. GnuTLS doesn't support it, and having behavior that differs between Linux and Mac can be kind of maddening. I can imagine something like, "embedded browser doesn't work for game X", with lots of "works for me" reports and the occasional "fails here too", only to discover that it works on Mac but not Linux. The additional cost of a difference in behavior doesn't seem worth it, especially when the protocol itself really should have died long ago. --Juan
