>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Michael Sierchio
>Sent: Wednesday, July 13, 2005 1:26 PM
>To: openssl-users@openssl.org
>Subject: Re: Algorithm licensing
>
>
>Ted Mittelstaedt wrote:
>
>> Actually, rega
Ted Mittelstaedt wrote:
Actually, regardless of the cipher you use, unless you have
a truly random source of numbers, your going to undermine the
strength of your encryption. For an embedded system, such a
thing has to be designed in from the get-go, as a software
PRNG is generally nowhere near
nally published
>>not patented. That's all I know. With Cisco IPSec work just
>about all
>>configs use md5, sha,
>>des and 3des and Cisco isn't known for liking to pay royalties to
>>anyone. If I were you I
>>would stick with md5, des and 3des.
>
ck with md5, des and 3des.
Ted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kramer, Mat
Sent: Monday, July 11, 2005 1:34 PM
To: openssl-users@openssl.org
Subject: Algorithm licensing
Hello,
We are using OpenSSL in an embedded device. I have been told t
PROTECTED] Behalf Of Kramer, Mat
Sent: Monday, July 11, 2005 1:34 PM
To: openssl-users@openssl.org
Subject: Algorithm licensing
Hello,
We are using OpenSSL in an embedded device. I have been told that
some of the cipher suites include patented algorithms that must be
licensed. The Open
uld
stick with md5, des and 3des.
Ted
-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On
Behalf Of Kramer, MatSent: Monday, July 11, 2005 1:34
PMTo: openssl-users@openssl.orgSubject: Algorithm
licensing
Hello,
We are using OpenSSL in an
Hello,
We are using OpenSSL in an embedded device. I have
been told that some of the cipher suites include patented algorithms that must
be licensed. The OpenSSL FAQ is intentionally vague about what algorithms
are protected, although it recommends a specific configuration to remove R
