I was just thinking about Microsoft and their CryptoAPI. They ship a
lot of documentation and sample code to all the world via the web and
the MSDN distributions and don't seem to have any problems with US
authorities (well not in this case anyway;-))
To me it seems like documentation and sampl
Dr Stephen Henson wrote:
>
> 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 OpenSS
hi all,
well am willing to assist in writing the docs..
previous wrote.. the following howtos and would
use as basis to write the openssl ones..
a- IPFWADM FAQ
b- FIREWALL1 - FAQ
c- SSH 1.xx original FAQ(custodian)
d - INND FAQ
e - SED FAQ
well the offers there anyhow..
must admit no veter
> (anyone wanting to supply a green card for the experiment would be my hero forever)
I know you were being humorous, but are you actually seeking to work in the US?
Bill Michaelson
__
OpenSSL Project
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
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
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
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
> "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
>Why would writing documentation be a problem here?
Yet again. Sigh.
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.
Another pot
Stephen,
Why would writing documentation be a problem here? That's ridiculous. Also, what is
the liability of the openssl
project if someone wants to contribute documentation from the US. Let's not be
completely speculative here, but
instead get down to the brass tacks. If writing documentatio
Leland V. Lammert wrote:
>
> At 07:24 AM 1/11/00 , you wrote:
> >Steve Sobol wrote:
> > >
> > > I like OpenSSL, I want to learn how to use it, and I would love to
> > > get involved in writing some technical documentation so that I could
> > > learn more quickly. I just need to work with someone
> >Unfortunately you're in the US which may well cause problems :-(
> >
> >Steve.
>
> Steve,
>
> Please elaborate. With the current relaxation on US export regulations, I would
>think this no longer a problem??
>
> Lee
There have been no changes in the U.S. Export Laws that I am awa
At 07:24 AM 1/11/00 , you wrote:
>Steve Sobol wrote:
> >
> > I like OpenSSL, I want to learn how to use it, and I would love to
> > get involved in writing some technical documentation so that I could
> > learn more quickly. I just need to work with someone that actually
> > *knows* the library.
Steve Sobol wrote:
>
> I like OpenSSL, I want to learn how to use it, and I would love to
> get involved in writing some technical documentation so that I could
> learn more quickly. I just need to work with someone that actually
> *knows* the library.
>
Unfortunately you're in the US which may
I like OpenSSL, I want to learn how to use it, and I would love to
get involved in writing some technical documentation so that I could
learn more quickly. I just need to work with someone that actually
*knows* the library.
"Mark H. Wood" wrote:
>
> I ought to stay out of this, but...
>
> On Th
Hoping to throw a little cool water on this heated thread, I have just seen a
galley proof of the following:
"SSL & TSL Essentials, Securing the Web"
Author: Steven A. Thomas
Publisher: John Wiley & Sons
ISBN: 0471383546
The book is scheduled for release this month (January 2000
> One thing that is consistently brought up on this list is the need for
> documentation but no one asking for it ever
says that they would help to write it. You certainly don't have to look any
deeper into the phenomena to discover that.
So in this light I would definitely like to help organize
CJ Holmes wrote:
>
> >On Thu, Dec 23, 1999 at 11:53:16AM -0600, Leland V. Lammert wrote:
> > > As a toolkit, OpenSSL can only be used *directly* by a programmer
> > > that knows C/C++, and in that case documentation is not required, as
> > > the programmer has the experience to use the toolkit di
>On Thu, Dec 23, 1999 at 11:53:16AM -0600, Leland V. Lammert wrote:
> > As a toolkit, OpenSSL can only be used *directly* by a programmer
> > that knows C/C++, and in that case documentation is not required, as
> > the programmer has the experience to use the toolkit directly.
>
>As a programmer u
I too think that the OpenSSL needs some GOOD documentation.
What is the point in developing a product, if
others cannot use it?
We were planning to build a OpenSSL based Client and
server communication system for the Windows platform.
The system was to be used by 20,000 clients on the field.
We
On Thu, Dec 23, 1999 at 11:53:16AM -0600, Leland V. Lammert wrote:
> As a toolkit, OpenSSL can only be used *directly* by a programmer
> that knows C/C++, and in that case documentation is not required, as
> the programmer has the experience to use the toolkit directly.
As a programmer using Open
Leland V. Lammert wrote:
> I don't think you have placed OpenSSL in the proper
> perspective. OpenSSL is a *toolkit* used primarily with OTHER
> applications.
Most toolkits have documentation, though. Developers need to know how
to use the product just like anyone else. For an example, see the
At 04:56 PM 12/22/99 , you wrote:
>"Leland V. Lammert" wrote:
>
>i don't want to sound ungrateful, but that document is useless for
>someone
>who wants to learn how to operate the thing. if the openssl people want
>to get
>people to start using it, they've *got* to get some decent introductory
>do
> the compilation and usage docs he repeatedly directed people toward
> this document *before* compiling and using the software.
Your point is well taken. But often it is helpful to compile something
and just play with it in order to learn about it. Learning is not a
straightforward process. I
Mike;
I know it seems a bit upside-down at the moment; really cool software and
pretty much no documentation except for terse function calls; part of the
reason for this is that many people who use the stuff are used to finding
their way around the technical side; another is that you will find a
n
Hi
>> From: Mike Hoegeman <[EMAIL PROTECTED]>
>> i don't want to sound ungrateful, but that document is useless for
>> someone who wants to learn how to operate the thing. if the
>> openssl people want to get people to start using it, they've *got*
>> to get some decent introductory document
Mike Hoegeman wrote:
>
> i realize it's a volunteer effort.. but if i magically became
> the "openssl despot", i'd stop *all* work on development
> and get a decent "get started with openssl document" before
> i did anything else.
>
That unfortunately isn't an option. Well not for me at least.
Good idea.
>From: Mike Hoegeman <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: openssl deperately needs some intro docs
>Date: Wed, 22 Dec 1999 14:56:44 -0800
>
>"Leland V. Lammert" wrote:
> >
> > At 04:55 AM 12/22/99 , you wrote:
> > >Hello all,
> > >
> > >I t
34 matches
Mail list logo
