>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of David Schwartz
>Sent: Wednesday, April 12, 2006 4:10 PM
>To: openssl-users@openssl.org
>Subject: RE: Licenses...
>
>
>
>> This was the same argument used by the Linux people to get
>the University
>> of Cali
On 4/12/06, Ted Mittelstaedt <[EMAIL PROTECTED]> wrote:
> Hey I have an idea. Why doesen't the OpenSSL community tell the GPL
> to modify it's license to be compliant to the OpenSSL license? That
> seems
> to be a mirror of what the GPL people are demanding. What's sauce for
> the goose is sauce
Ted Mittelstaedt <[EMAIL PROTECTED]> wrote:
> What I still have not seen from the "pro-advertisement-clause-removal"
> camp is a logical explanation of why someone cannot use OpenSSL because of
> the so-called "advertising-clause"
If someone is a development community, then no, there's no
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Richard
>Levitte - VMS Whacker
>Sent: Monday, April 10, 2006 11:43 PM
>To: openssl-users@openssl.org; [EMAIL PROTECTED]
>Subject: Re: Licenses...
>
> I've come into this project with the vision that
>OpenSSL
I'm new to the OpenSSL/FIPS discussion and I am not familiar with
OpenSSL for FIPS
but I do have some experience with FIPS certification.
First of all I assume that we are talking about FIPS 140-2 [or 3 but
that's not mandatory anywhere yet].
There are also FIPS publications on the cryptographic
It seems to me that the question is this: can an application use two
FIPS-certified toolkits at the same time? For example, a FIPS certified
device for doing private key operations, and FIPS software for doing
symmetric key operations. The answer is yes. (There will be issues and
difficulties
On Wed, Apr 12, 2006, Robert Stober wrote:
> Good Afternoon,
>
> I solved one of my problems, and banged my head against the wall all day
> trying to figure out how to get the OS to select a port for my
> application. Every example I see shows the port being explicitly set,
> whereas I need the O
Good Afternoon,
I solved one of my problems, and banged my head against the wall all day
trying to figure out how to get the OS to select a port for my
application. Every example I see shows the port being explicitly set,
whereas I need the OS to do this so that I can be sure the port is free.
I
On 4/12/06, Lyon, Jay <[EMAIL PROTECTED]> wrote:
> Kyle, thanks for your response. If you don't mind answering one more
> question, it will help clarify things for me.
>
> Assume a hypothetical crypto toolkit; OpenEXX has recently emerged and
> is a leader in a crypto technology that is useful for
Kyle, thanks for your response. If you don't mind answering one more
question, it will help clarify things for me.
Assume a hypothetical crypto toolkit; OpenEXX has recently emerged and
is a leader in a crypto technology that is useful for memory constrained
devices. It has been recently FIPS va
> This was the same argument used by the Linux people to get the University
> of California, Berkeley to revoke it's "advert clause"
>
> However, once that happened the GPL people simply grabbed what bits they
> wanted and ran off. Berkeley software hasn't seen any additional
> attention or
> ben
It's my mistake, I believe. AES does specify 128, 192, and 256-bit
keylengths, but only 128-bit block lengths. (I misread something on
the CSRC website.)
(I'm copying this back to the list because it's something that I
should clear up.)
-Kyle H
On 4/12/06, Wes Kussmaul <[EMAIL PROTECTED]> wrot
Forwarded to respective mailing lists
Regards,
Lutz
- Forwarded message from Thomas Schulz <[EMAIL PROTECTED]> -
X-Original-To: [EMAIL PROTECTED]
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Date: Wed, 12 Apr 2006 14:42:27 -0400 (EDT)
From: Thomas Schulz <[EMAI
Hi Jeffrey, long time!
In message <[EMAIL PROTECTED]> on Mon, 10 Apr 2006 22:28:22 -0400, Jeffrey
Altman <[EMAIL PROTECTED]> said:
jaltman> Tyler MacDonald wrote:
jaltman>
jaltman> > And it's not always even that simple: for example, the
jaltman> > freeradius project's postgresql plugin li
hi
i'm having problems trying to build OpenSSL 0.9.8a on an Intel based Mac OS X
10.4.6.
if i've understood correctly, building goes fine up to the point where the
openssl binary is
being linked. at that point i get lots of errors about undefined symbols and
the build
terminates (see attache
This should probably be clarified: The application must only use
FIPS-approved modules for all cryptography. However, most
FIPS-approved modules cost a lot of money -- there are two that do
not, but OpenSSL is the only one available for UNIX systems that does
not, and it's the only one that can be
Good Morning,
I'm currently creating a socket that can accept remote connections using
conn = BIO_new_accept(PORT) and then binding that port using
BIO_do_accept(conn).
But what I want is for the system to choose an ephemeral port for me,
and then I want to find out what that port number is.
1.
"Sara978 (sent by Nabble.com)" <[EMAIL PROTECTED]> writes:
> I have tried to write:
>
> patch -p1 < ts-20060225-0_9_8a-patch.gz
You have to uncompress the patch file first:
gunzip ts-20060225-0_9_8a-patch.gz
patch -p1 http://www.openssl.org
User Support Mailing Listo
I have tried to write:
patch -p1 < ts-20060225-0_9_8a-patch.gz
But I have this error:
bash-3.00$ patch -p1 < ts-20060225-0_9_8a-patch.gz
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|Index:
In message <[EMAIL PROTECTED]> on Wed, 12 Apr 2006 07:10:23 -0700 (PDT),
"Sara978 (sent by Nabble.com)" <[EMAIL PROTECTED]> said:
lists> gzip -cd ts-20060225-0_9_8a-patch.gz | patch -p1
lists>
lists> but I have this error:
lists>
lists> ts-20060225-0_9_8a-patch.gz: not in gzip format
lists> pat
Hi,
I have download and installed openssl with cygwin (I have openssl 0.9.8a
version)
Now I have download openssl patch ts-20060225-0_9_8a-patch.gz in
C:\cygwin\tmp
I want to extract this file with command:
gzip -cd ts-20060225-0_9_8a-patch.gz | patch -p1
but I have this error:
ts-20060225-
21 matches
Mail list logo