Ethereal-dev: Re: [Ethereal-dev] kerberos update, new test version for those that are brave

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Ronnie Sahlberg" <ronnie_sahlberg@xxxxxxxxxxxxxx>
Date: Sat, 7 Feb 2004 20:44:09 +1100
From: "Eric Wedel"
Sent: Saturday, February 07, 2004 7:35 AM
Subject: RE: [Ethereal-dev] kerberos update, new test version for those that
are brave


> afaik, nettle should work fine, but that still leaves an intermediate
> layer to be implemented.

I understand.

Would that intermediate layer require more than a few hundred lines if one
only wants to implement
support for the 4-5 most popular encryption/hashes to start with? Im not
afraid of implementing stuff as long as it takes
less than ten thousand lines. (and even then those limits are "vague" as
packet-h225 and packet-h245 shows.)
I feel Ethereal could really use this.
That might not be as important as :  I personally and colleagues REALLY NEED
to open the tickets!!!



I am not clear on what exactly the licence is for MIT-Kerberos but since it
is crypto and developed in the us one might want to stay
way clear of it.
Heimdal would be an option (and is probably more common than MIT anyway) but
it pulls in so much extra junk in the libs that ethereal would
never need.
Nettle is also redistribution unencumbered, is small, and implements almost
all popular cryptos and hashes.