/r$
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Thanks.
/r$
--
Senior Architect, Akamai Technologies
IM: richs...@jabber.at Twitter: RichSalz
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
Sorry,
I sent the wrong patch.
--
Boyd Gerber <[EMAIL PROTECTED]>
ZENEZ 3748 Valley Forge Road, Magna Utah 84044
*** Configure.org Thu Dec 6 06:11:39 2001
--- Configure Fri Dec 28 16:39:23 2001
***
*** 421,427
# SCO 5 - Ben Laurie <[EMAIL PROTECTED]>
ask on the ietf TLS list.
At 12:28 PM 1/15/01 -0500, Tom Biggs wrote:
>Ideally I'd want to be on [EMAIL PROTECTED],
>but of course there is no such list, and I doubt many people
>would sign up for it if there were.
__
OpenSSL P
that I've asked some very dumb questions
because I overlooked something obvious in the code or
documentation.
Still, I am soloing the software side of this project, and it's
always good to have other programmers to compare notes
with. And (sorry EAY!) the code can be quite obscure at
times -
I have a small suggestion for the openssl.org website -
Perhaps the openssl-dev maillist could be described
a bit differently? I think that many people are making
an honest mistake when they sign up for this list to
ask questions about how to develop applications with
OpenSSL. They think of th
I forgot to mention, I'm runing OpenSSL 0.9.3a. Thanks again.
-Jef
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Srry,
I dont't know why I did posted the WRONG patch to the ca.c (old one that do
not works correctly with dates).
Please use this instead.
(Patch to the latest SNAP 05-10-99)
See you,
Massimiliano Pala ([EMAIL PROTECTED])
--- ca.cMon May 10 14:51:06 1999
+++ ca-patched.c
> Neither. I exported documentation and user-level
> specifications. I didn't export source because we felt it would be
> technical assistance.
I exported source, because that's what the Open Software Foundation did.
I worked on DCE, an authenticated/secure RPC system that used
Kerberos.
> > My interpretation (and C2Net's attorneys interpretations when
> > advising C2Net) is that "encryption commodities or software" applies
> > to the entire product, not just specific source files.
>
> Did you export source or executables? I thought the latter.
> My experience is with the fo
> My interpretation (and C2Net's attorneys interpretations when
> advising C2Net) is that "encryption commodities or software" applies
> to the entire product, not just specific source files.
Did you export source or executables? I thought the latter.
My experience is with the former.
___
> (c) Technical assistance by U.S. persons with respect to
> encryption commodities or software as described in 744.9 of theEAR.
>
> Now, there are various ways to consider this; Sameer is paying for a lawyer
> to perform one analysis. Thanks. In anticipation of this, I encourage
> A recent note by Sameer alluded to the following. The EAR issued on
> 30-dec-96 transferred crypto from US Dept of State to Commerce.
> It loosened some requirements, but added this (chilling) addition
> to the list of items controlled:
> (c) Technical assistance by U.S. persons with resp
A recent note by Sameer alluded to the following. The EAR issued on
30-dec-96 transferred crypto from US Dept of State to Commerce.
It loosened some requirements, but added this (chilling) addition
to the list of items controlled:
(c) Technical assistance by U.S. persons with respect to
15 matches
Mail list logo
