Ethereal-users: [Ethereal-users] Re: Linking against OpenSSL

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Wes Hardaker <wjhns36@xxxxxxxxxxxxx>
Date: Fri, 04 Jun 2004 07:28:04 -0700
>>>>> On Fri, 4 Jun 2004 11:47:57 +0200 , Biot Olivier <Olivier.Biot@xxxxxxxxxxx> said:

Biot> |Still, (UCD|Net)-SNMP depends on OpenSSL for SNMPv3 support, 
Biot> |which affects us when using "--with-(ucd|net)-snmp".

Biot> But then either *-SNMP has a license that complies with the OpenSSL
Biot> license, or they have the same issue we have. Either way, we have a
Biot> problem.

[FYI, I'm the lead developer of Net-SNMP]

We actually chose OpenSSL because it wasn't GPL (heh...  we had the
reverse issue) and didn't really bother or BSD requirement.

One option you could think about is to refuse to link against the snmp
library if it was linked with openssl.  Net-SNMP doesn't always link
against openssl, it only links against it if it was compiled that
way.  In short, SNMPv3 has optional support SHA1, DES and AES.  If the
user didn't have openssl around, they don't get support for those
three functions.  You can check for this easy enough, assuming a
fairly recent version of Net-SNMP, but running "net-snmp-config
--libs" and checking for -lcrypto in the output.  If it exists,
ac_error out with an error mentioning licensing incompatibility.

I'm not sure this would work or not, of course, as IANAL.  But it's
food for thought.

[note that in ucd-snmp we didn't have such a tool that let you easily test]
-- 
Wes Hardaker
Sparta