Ben Collins <[EMAIL PROTECTED]> writes: > Yes, you can package it, so long as you don't link it with SSL. Note, > openldap can also be linked with SSL and Kerberos (as do many other > programs), but the binaries aren't linked, and can go safely into us/main.
I have to ask: there is a difference between statically and dynamically linking. If it is being dynamically linked, Mr. Nelson is not exporting any encryption technology from the USA, and neither is Debian. It has already been established that "hooks" (in the form of system() calls to PGP/GPG or whatever) are legal and valid, so I see no reason why this should not be. However, it brings up a technical issue in that the internal integrity of the dependency tree of main would be compromised. I don't know of a good answer to that one, unless someone comes up with a "libunssl" or something. > That support does not contain any crypto. The crypto is in the libraries > with which it *could* be linked with. So if you don't link, then you are > not breaking any crypto laws, whatsoever. I would say the same if you do link dynamically. > > Ben > > -- > -----------=======-=-======-=========-----------=====------------=-=------ > / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ > ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' > `---=========------=======-------------=-=-----=-===-======-------=--=---' > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- John Goerzen <[EMAIL PROTECTED]> www.complete.org Sr. Software Developer, Progeny Linux Systems, Inc. www.progenylinux.com #include <std_disclaimer.h> <[EMAIL PROTECTED]>
