-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chaps and Chapesses
Is it my overworked imagination, or did I read here a while ago that
someone has a draft spec for a DH certificate?
Jon
-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.0.2i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, for my next question:
Where are they specified?
Jon
- -Original Message-
From: Ben Laurie [SMTP:[EMAIL PROTECTED]]
Sent: Monday, May 17, 1999 2:54 PM
To: [EMAIL PROTECTED]
Subject:Re: DH Cert
Jon Parry-McCulloch wrote
Construct a memory BIO and write your cert to it. You can then read straight
out of this memory BIO into a buffer.
Summat like this:
/***
Function: get_certificate_as_buffer()
Input : const char*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
People,
Party time:
U.S. export limits on encryption are unconstitutional, the Ninth
Circuit Court of Appeals ruled in a
precedent-setting decision today.
See
http://www.news.com/News/Item/0,4,0-36217,00.html?st.ne.lh..ni
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
you have to also put in the machine architecture
Sigh... yes,I worked this out about .1 nanoseconds after sending
my reply. To compound my idiocy, I found I was linking with cc but I
had built OpenSSL with gcc.
It didn't like it much.
Jon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -Original Message-
From: Albert Max Lai [SMTP:[EMAIL PROTECTED]]
Sent: Saturday, March 27, 1999 9:45 AM
To: [EMAIL PROTECTED]
Subject:Re: 0.9.2b Sparc problem
On Fri, 26 Mar 1999, Ed Kubaitis wrote:
perl ./Configure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any ideas?
Yes, I'm a moron.
Don't ask... it's _far_ too embarrassing.
Jon
-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.0.2i
iQA/AwUBNv+izngWiDO86u4+EQIzKQCeLVGgBCnlvPw8HJiLWqfCWU+vK6AAnioE
XErPNztWJ1YPtSYBmCn5OVl1
=4r3V
I ahve an RSA license also and there's alot of stuff you can and
can't say
because of the contract. I'd double check, and if you can have an
attorney check what you say before sending it. I can't even
comment on
how restictive the contract is.
Oh. Then
Greetings,
Lots of you have said you'd be interested in the results [of my experiences
with RSA BSAFE SSL-C], so unless anyone objects I'll post them here and on
the ssl-users list. Eventually they'll make way onto my website.
However, I may not get very far because one thing I _can_ say is
rsa won't be too pleased
i'd check the licience
You think the licence contains stuff that stops me from saying "it
was easy to use and it worked a treat" or "it was hard to use and I couldn't
get it to do anything?".
I doubt that. Isn't RSA an
Once the library contains crypto code of American origin,
it is
covered by the American reexport regulations. That means
that everyone
who distributes it internationally will violate US law.
This is true, but who outside the US gives a
11 matches
Mail list logo
