Marek Michalkiewicz writes: > Package: libssl0.9.6 > Version: 0.9.6b-1 > Severity: wishlist > Tags: sid > > Not sure how hard would be to do this, but instead of so many dual > SSL/non-SSL versions of various packages, it might be a good idea > to have a libssl-dummy package (in main) that contains no encryption > code, and can be installed instead of libssl0.9.6 if the latter is > illegal somewhere. Then only build single packages that depend on > libssl or libssl-dummy, and enable SSL at run time if the real libssl > is installed. Unless, of course, Debian decides to follow many other > distributions, and simply include all crypto in main... I don't think that this is possible. Often you have to change the programming logic to enable ssl in an application. So a fallback to just doing nothing would not work. Especially applications which can to both with and without ssl would have a problem. For programs which simply should put a wrapper around the plaintext protocoll you can easily use stunnel. Christoph ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
