ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

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

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

From: Devin Heitmueller <dheitmueller@xxxxxxxxxxx>
Date: Thu, 03 Jun 2004 15:42:06 -0400
On Thu, 2004-06-03 at 15:15, Thomas Anders wrote:
> If we can afford it (in terms of licensing), I'd prefer to see
> Ethereal making more *use* of OpenSSL (for decrypting packets)
> rather than disabling it by default. YMMV, though.

We've been through this a few times on the mailing list already.  The
answer seems to be a resounding "no".  This is what prompted me to
import crypt-*.[ch] into Ethereal.  It's also why I said "WTF?" when I
saw that Ethereal was including OpenSSL anyway...

I would love to use OpenSSL to provide ssldump like functionality in
Ethereal.  Given that we couldn't because of the licensing, I spent an
entire three-day-weekend trying to figure out Mozilla's NSS library
(Netscape Security Services) to perform the equivalent functions.  I
pretty much gave up after I couldn't even get the private key imported
into an keystore (documentation is scarce/incorrect and the only real
example to reference that uses NSS is Mozilla itself).

At this point, I'm debating just writing the code with OpenSSL and
distributing a patch against Ethereal on my website.  Then anyone who
wants the functionality can get the patch, apply it against the Ethereal
source and recompile.  This would get around the license issue, at least
as far as I can see, since nobody would be distributing a "combined
product".

-- 
Devin Heitmueller
Senior Software Engineer
Netilla Networks Inc.

Attachment: signature.asc
Description: This is a digitally signed message part