Hi there, SSL support is one of the biggest lacks in dillo for me. To that end, I'm thinking of adding it in. Without knowing the dillo codebase, I see two obvious options: 1) Add a src/IO/https.c file based on src/IO/http.c 2) Move http.c to using openssl's BIO's which can support either encrypted or clear traffic, as well as filters. 1 seems much more straightforward and will result in quicker https support, but will cause there to be a whole hell of a lot of code duplication between http.c & https.c. 2 seems like the more "moral" choice and will make dillo better, at the cost of making openssl necessary for dillo builds. Is anyone currently working on ssl support in dillo? Are you using either of the above two options? If the answer to the first question is negative, do people have feelings about code duplication vs. reliance on openssl? (of course, there's a third option of #ifdef'ing the hell out of http.c, adding BIO support that can be compiled out leaving the current plain socket-based code, but that would probably be more of a nightmare to maintain than 1) above). Cheers, -- Ami Fischman usenet@fischman.org