Am I blind or is there no link to a FAQ anywhere on the website?
If someone would be so kind as to send me the link for the FAQ I would
appreciate it.
--Adam
__
OpenSSL Project http://www.openssl
need someone to write it just give me the data and i will spend the
time to write() them..
On Wed, 12 Jan 2000, you wrote:
> "Salz, Rich" wrote:
> >
> > >Why would writing documentation be a problem here?
>
> > The current regulations prohibit US persons from providing technical
> > assistance
Global Exports of Commercial Encryption Source Code and Toolkits
Encryption source code which is available to the public and
which is subject to an express agreement for the payment of a
licensing fee or royalty for commercial production or sale of
any product developed using the source code (suc
I downloaded OpenSSL0.9.4( or OpenSSL0.9.3a) on Unix machine.
And
%./config gcc$B!!(B( or config )
Operating system: sun4m-sun-solaris2
This system (solaris-sparcv8-gcc) is not supported. See file INSTALL for detail
Do I have to define hardware,operating system?
Or can't sun4m use OpenSSL0.9.
On Wed, 12 Jan 2000, you wrote:
[...]
> Well then what about doing the documentation on the mailing list. We can
> collaborate on a functional documentation on an openssl-docs list and it gets
> posted as a major revision once a week. Let's get creative here. There's more than
> one way to skin t
> i don't know if this is related to openssl, but every time
> i run the following code on redhat 6.1 it will receive a SEGV.
Please post compilable source code and specify which OpenSSL version
you are using.
__
OpenSSL Project
Rich Salz wrote:
> > > The current regulations prohibit US persons from providing technical
> > > assistance to anything that would be export-controlled if it were inside the
> > > US. Pretty obviously, this would include diff's and documentation.
> >
> > Then even responding to openssl-users
the WebSite with the regulations. read 'em and sleep[sic]
--- eric
Eric S. Johansson[EMAIL PROTECTED][EMAIL PROTECTED]
This message was composed almost entirely using NaturallySpeaking
--- begin forwarded text
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: BXA press release URL; a
the rules changed but have they changed enough? Notice about where to
get the regulations to follow.
Eric S. Johansson[EMAIL PROTECTED][EMAIL PROTECTED]
This message was composed almost entirely using NaturallySpeaking
-- Forwarded message --
To: [EMAIL PROTECTED], [EMAI
There is another issue as well whatever the interpretation of the laws
some companies and organisations take an ultra cautious line.
For example one organisation at one point was considering not using
OpenSSL because there was a (false) rumour that the OpenSSL group had
encouraged anonymous contr
On Wed, 12 Jan 2000, Michael Sierchio wrote:
> Documentation is probably protected speech, while diffs are actually
> program instructions. We'll see where it goes. Meanwhile, all this
> fear-mongering about draconian US export laws is nauseating -- is a
> single person in a US prison for ITAR
kevin> I'm not an expert on international law, but I was under the
kevin> impression that technical assistance would fall under the same
kevin> category as source code and information related to it - not
kevin> export controlled.
It seems that in the US, a crucial factor is the form in which it i
Hi everyone,
Sorry I did not read the entire "openssl desperately needs some intro docs"
thread (busy busy busy), just wanted to ask if the effort would still be
appreciated?
If so, I think I can "create" the time to make it provided I get some
assistance with the requirements (and I think I am
hi,
i don't know if this is related to openssl, but every time
i run the following code on redhat 6.1 it will receive a SEGV.
it doesnt happen with older versions of glibc (tested 2.0.7),
and it'll run just fine on aix and solaris:
#define BUFFER 512
[...]
unsigned char buf[BUFFER];
int rlen =
> "Salz, Rich" wrote:
> >
> > >Why would writing documentation be a problem here?
>
> > The current regulations prohibit US persons from providing technical
> > assistance to anything that would be export-controlled if it were inside the
> > US. Pretty obviously, this would include diff's and d
"Salz, Rich" wrote:
>
> >Why would writing documentation be a problem here?
> The current regulations prohibit US persons from providing technical
> assistance to anything that would be export-controlled if it were inside the
> US. Pretty obviously, this would include diff's and documentation.
>I'm not an expert on international law, but I was under the impression that
technical assistance would fall under the same category as source code and
information related to it - not export controlled.
You seem to be talking about the proposed new regulations, not the current
regime. "Technical
17 matches
Mail list logo
