So, I'm lame, and I haven't been paying too much attention to
this list. I realized today, however, that it would be legit for me to
work on documentation for OpenSSL. So what's the status on
documentation? I'm thinking it would be appropriate to setup another
CVS repo
Appended two corrections, one extension and one new manpage.
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129
Universitaet
Hello,
I have two suggestions about the documentation.
First suggestion, a minor one about INSTALL.W32. Every time I go to
change ./ms/do_ms.bat so I can enable debugging symbols I change the
line
perl util\mk1mf.pl no-asm VC-WIN32 >ms\nt.mak
I add 'debug' in last place
Here's a patch for d2i_SSL_SESSION.pod, pointing out a pitfall when using
i2d_SSL_SESSIONdiff -U3 -r1.1.1.2 d2i_SSL_SESSION.pod
--- doc/ssl/d2i_SSL_SESSION.pod 2002/07/30 18:26:08 1.1.1.2
+++ doc/ssl/d2i_SSL_SESSION.pod 2004/05/05 22:06:44
@@ -20,7 +20,10 @@
i2d_SSL_SESSION() transforms the SSL_S
While I'm currently on the way creating the first cut of a real documentation
set, I recognized that the stuff under doc/ is really a horrible mess, 80%
obsolete and more a joke than everything else. So my idea is to assemble all
the various .doc files into a single doc/ssleay.txt file.
Good point. There are certainly several folk in the US who
would/could help with that.
At 01:09 AM 1/19/99 -0800, you wrote:
> So, I'm lame, and I haven't been paying too much attention to
>this list. I realized today, however, that it would be legit for me to
>work o
t proof; and
(c) starting down a slippery slope that OpenSSL really should avoid --
setting up mechanisms to help "enforce" every participating country's
crypto export rules?
I totally agree that "writing documentation" should be foisted off to
us whenever possible, free
sameer wrote:
>
> So, I'm lame, and I haven't been paying too much attention to
> this list. I realized today, however, that it would be legit for me to
> work on documentation for OpenSSL. So what's the status on
> documentation? I'm thinking it wo
[EMAIL PROTECTED] wrote:
>
> I don't understand why US people can't be given access to the source
> tree.
I didn't understand that, either, but it didn't seem worth quibbling,
because there are other reasons, anyway...
> Is it because of a desire to "prove" that nobody from the US exported
> so
nnot
commit to the non-documentation stuff (export!), but access to openssl/doc/
sounds good to me, too.
> Is it because of a desire to "prove" that nobody from the US exported
> source code? Surely that's (a) too big a hammer (we can, e.g., con-
> tribute to the ASN1 engine
e source tree in general? Sure, we should perhaps make sure they cannot
> commit to the non-documentation stuff (export!), but access to openssl/doc/
> sounds good to me, too.
>
> > Is it because of a desire to "prove" that nobody from the US exported
> > source code?
rticipating country's
> crypto export rules?
>
> I totally agree that "writing documentation" should be foisted off to
> us whenever possible, freeing up those capable of doing crypto code to
> do so.
> /r$
>
>
>
In article <[EMAIL PROTECTED]> you wrote:
> Ralf S. Engelschall wrote:
[...]
>> IMHO it's ok to not give them access to the non-documentation stuff, because
>> this way we don't have to make sure people don't violate their export laws.
> I'm totall
Ben Laurie <[EMAIL PROTECTED]> wrote:
> I'm totally against this. We have no responsibility to enforce the USG's
> stupid export laws, and I see no reason we should take that
> responsibility on.
Once the library contains crypto code of American origin, it is
covered by the American reexport reg
Ralf S. Engelschall wrote:
>
> In article <[EMAIL PROTECTED]> you wrote:
> > Ralf S. Engelschall wrote:
>
> [...]
> >> IMHO it's ok to not give them access to the non-documentation stuff, because
> >> this way we don't have to make sure people
>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
Anonymous wrote:
>
> Ben Laurie <[EMAIL PROTECTED]> wrote:
>
> > I'm totally against this. We have no responsibility to enforce the USG's
> > stupid export laws, and I see no reason we should take that
> > responsibility on.
>
> Once the library contains crypto code of American origin, it is
>
In article <[EMAIL PROTECTED]> you wrote:
> Ralf S. Engelschall wrote:
>>
>> In article <[EMAIL PROTECTED]> you wrote:
>> > Ralf S. Engelschall wrote:
>>
>> [...]
>> >> IMHO it's ok to not give them access to the non-documentatio
From: Jon Parry-McCulloch <[EMAIL PROTECTED]>
> >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 damn?
It's not just an issue for those outside the US. Its an issue
for multinational companies that wish to ship strong cryptography
products worldwide. If there's a company that does business in the US,
then they won't be able to u
>
> b) US law doesn't apply to me (at least while I'm not in US territory)
> or OpenSSL, AFAIK, regardless of the code's origin.
>
US law may not apply to you, but it applies to many of the
people who are using OpenSSL outside the United States. If its your
intention that multinationals
> US law may not apply to you, but it applies to many of the
>people who are using OpenSSL outside the United States.
Hmm, is it your contention that if a US person exports crypto code,
then the US govt will come after non-US citizens who uses that code?
The export regulations say that US
Sameer Parekh wrote:
>
> >
> > b) US law doesn't apply to me (at least while I'm not in US territory)
> > or OpenSSL, AFAIK, regardless of the code's origin.
> >
>
> US law may not apply to you, but it applies to many of the
> people who are using OpenSSL outside the United States. If it
At 11:08 AM 1/22/99 , [EMAIL PROTECTED] wrote:
>> US law may not apply to you, but it applies to many of the
>>people who are using OpenSSL outside the United States.
>
>Hmm, is it your contention that if a US person exports crypto code,
>then the US govt will come after non-US citizens who u
We may be misunderstanding each other. Let me outline my
position in pieces so we can see where we agree and where we
disagree, more specifically.
a) I would like the OpenSSL project to protect the codebase from being
polluted with export-restricted code, US or otherwise.
b) I would lik
Sameer Parekh wrote:
>
> We may be misunderstanding each other. Let me outline my
> position in pieces so we can see where we agree and where we
> disagree, more specifically.
>
> a) I would like the OpenSSL project to protect the codebase from being
> polluted with export-restricted cod
salzr> The export regulations say that US persons can't export. They
salzr> are silent on what happens after the code has gone offshore.
I don't think that's quite correct. What it says is that strong
encryption code can't be exported from the US, except to Canada.
Thenationality of the person h
Sameer Parekh wrote:
>
> d) The OpenSSL project should not allow US persons to contribute to
> the OpenSSL source code.
>
This would be the easiest way to handle things but it might be regarded
as over cautious.
There are some non crypto areas of OpenSSL where US persons might be
able to contr
>
> Examples would be certificate extension code, message digest algorithms
> or stuff related to authentication only (e.g. DSS).
>
> Or do you think even contributions of this sort could cause problems?
I beleive that this would be a problem because that would be a
US person providing
> My problem with this is that it requires the OpenSSL project to be aware
> of export restrictions in other jurisdictions. If we really have to be
> aware, then so be it, but I'd be _much_ happier if we could only worry
> about our own. Can we not protect the codebase simply by asking that
> peop
> I don't think that's quite correct. What it says is that strong
> encryption code can't be exported from the US, except to Canada.
> Thenationality of the person has nothing to do with it. Otherwise, it
> would just be for any company in the US to ask some foreign consultant
> to come to the s
Sameer Parekh wrote:
> > > b) I would like the OpenSSL project to require that all contributors
> > > warrant that the code they are contributing does not violate export
> > > controls.
> >
> > So long as _I_ don't have to collect these warranties, I can't see why
> > this should be a problem. I d
ben> I suspect that there are people around who are going to disagree on what
ben> can and can't be exported, though, and I really am not at all sure how
ben> we can judge who is correct. For starters, we already see one camp that
ben> says "any source in OpenSSL is unexportable", and another that
[good faith]
>
> OK. Is this explicitly stated somewhere, or is it an interpretation of
> regs? Has it been tested in court?
As far as I know it has not been tested in court. The regs on
export restricted web sites *do* explicitly mention good faith
effort. I think that the use of good f
> I suspect that there are people around who are going to disagree on what
> can and can't be exported, though, and I really am not at all sure how
> we can judge who is correct.
You can't. That's perhaps the biggest problem with the US export
regulations: all the "interesting" cases are decided
Sameer Parekh wrote:
> > Anyone got any suggestions as to how we resolve this?
>
> My suggestion is that we find a US export lawyer (I know a few
> =) willing to provide the group with some advice pro bono, and the
> group can create guidelines based on that advice.
I'll go with that. Gi
> No. Its my contention that if a US person exports crypto code >illegally,
>the US government will go after a US-related firm (i.e. a >multinational)
>who uses that code internationally. This is based on statements from
>government officials and discussions with export control attorneys.
M
OK, you have a good point. Let me try again. A US-related firm
will not use illegally exported cryptography code for fear of stock
market and government retribution. I have direct experience with large
US-related firms for whom this has been an issue.
> > No. Its my contention that if
> A US-related firm
>will not use illegally exported cryptography code for fear of stock
>market and government retribution.
Okay, that makes sense to me.
__
OpenSSL Project http://www.open
> My discussions have had other conclusions, saying they'd be "foolish" to go
> after a big company. I think they were just trying to inti-
> midate you.
Perhaps. Not all multi-nationals are big however - Open Software Associates
in such an example. We still want to be able to use OpenSSL witho
On 22-Jan-99 Ben Laurie wrote:
> Sameer Parekh wrote:
>>
>> We may be misunderstanding each other. Let me outline my
>> position in pieces so we can see where we agree and where we
>> disagree, more specifically.
>>
>> a) I would like the OpenSSL project to protect the codebase from bein
Dear Developer,
I found a "documentation" error by compiling openssl.
in the Makefile.ssl file, one can read:
# If you change the INSTALLTOP, make sure to also change the values
# in crypto/location.h
... but I can't find the file crypto/location.h
The INSTALL file seems m
I'm just starting to work with SSL and openSSL. Is there any coherent
documentation out there
that might elucidate how openSSL can be used. Any example programs?
Anything?
Cheers.
> Amin Manji
>
> EDCU IT
CREDIT | FIRST Credit Suisse First Boston Securities (Japa
Hello everybody,
Do you know if there's any kind of documentation project
going on for Openssl? I'd like to contribute to that.
If there ain't is someone thinking of putting one together,
I mean, it's almost comparable to medieval alchemy trying
to do anything reasonable wit
functionality but it would not, if there would be a more user friendly
alternative. Can somebody advice a alternative crypto and x509 library?
The documentation on the web page is not enough, of course. There are
documentation systems like doxygen which can generate the documentation.
It will be a
Hi,
I would like to know where I can find documentation on openssl
implementation (not API use for programming others programs, I'm
looking for openssl internals)
I want to correct dtls implementation (I have already sent a little
patch ;) ) and I want to understand implementation organiz
if OpenSSL documentation
would be more complete.
My question is: what about wiki, so that people using OpenSSL could add
documentation as soon as they discover how undocumented functions works?
Regards,
Massimiliano Ziccardi
Is there any good documentation on which calls in which order a Telnet application
should make for an SSL connection ? The documentation on the Openssl web site only
lists the prototypes for each api call.
I was taught a long time ago that a product without documentation is worthless. If
Hi!
Two corrections:
- c_rehash needs a directory as argument
- Unlike all other items the BIO-layer can return "-2". Hence the correct
classification of error return values is "<0" instead of "-1".
Best regards,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU
(Just came back from hiking in the Harz mountains late yesterday evening.)
On Fri, Oct 20, 2000 at 12:37:08PM -0700, john traenky wrote:
> I read you too work on documentation. I would like to
> join the work. How should I start? Should I gather
> notes about SSLeay and OpenSSL and
0.9.6 already has excellent quality (counted by the number of serious
bugs found since the release :-). A lot of serious work was been done by
serious people to reach this state. The documentation must keep up with
these standards :-)
> If you agree, please reply. I will begin creatio ex
> ni
; On Fri, Oct 20, 2000 at 12:37:08PM -0700, john
> traenky wrote:
> > I read you too work on documentation. I would
> like to
> > join the work. How should I start? Should I
> gather
> > notes about SSLeay and OpenSSL and create a user
> guide
> > draft? Who i
Lutz is right, there's lots of bad advice lurking on the email lists;
openssl-dev is better than openssl-users.
On the other hand, I think it will be easier to figure out who's right
and who's not. Whenever you get conflicting feedback, or from someone
you don't know, mark it off as "to be confi
I've investigated lacks of documentation in the current OpenSSL
snapshot.
Method of investigation is quite simple
1. Run util/extract-names.pl on the all pod files in the doc/crypto and
doc/ssl and produce sorted list of all function names referenced in the
NAME sections.
2. Take lis
I've investigated lacks of documentation in the current OpenSSL
snapshot.
Method of investigation is quite simple
1. Run util/extract-names.pl on the all pod files in the doc/crypto and
doc/ssl and produce sorted list of all function names referenced in the
NAME sections.
2. Take lis
Hi all,
I'm trying to develop some new algorithms to use with an openssl applications
we have here. I'M studing about the ENGINE API, but there is so few documentations.
I've already searched on the list history, but I can't see any documentation tha fits
my needs.
On Thursday 06 May 2004 08:45, Jim Schneider wrote:
> Here's a patch for d2i_SSL_SESSION.pod, pointing out a pitfall when using
> i2d_SSL_SESSION
Actually, that wasn't as clear as it should be - pp isn't getting clobbered,
what it points to (*pp) is getting clobbered.
In article <[EMAIL PROTECTED]> you wrote:
> in the Makefile.ssl file, one can read:
> # If you change the INSTALLTOP, make sure to also change the values
> # in crypto/location.h
> ... but I can't find the file crypto/location.h
> The INSTALL file seems more correct and tell me to edit the crypt
Hi,
openssl-0.9.2b:
docu about:
keyUsage (PKIX key usage) takes the flags: .
./doc/openssl.txt (line 206):
keyEncipherment, dataEncipherment, keyAgreement, keyCertSign, cRLCertSign
I think this should read as:
keyEnciphe
Officially I don't think so.
But check out http://www.columbia.edu/~ariel/ssleay/...
which is the most comprehensive documentation I have found so far.
Kim Hellan
> -Oprindelig meddelelse-
> Fra: Tomi J. Nylund [SMTP:[EMAIL PROTECTED]]
> Sendt:16. februar 20
There is a minor discrepancy in the x509 command line
switch that is used to delete extensions from a certificate.
/doc/apps/x509.pod refers to the switch as:
-clrext
/apps/x509.c refers to the switch as:
-crlext
^^
Mike Attili
Amaxo, Inc.
tions, the parameters and comments
widerstand> in the code what is done are missing.
We're well aware the documentation is lacking. We are adding some all
the time. I wish we had the possibility to do *only* that for a
while, but that's not what reality looks like.
In the Open Sourc
files,
widerstand> explanations to the functions, the parameters and comments
widerstand> in the code what is done are missing.
We're well aware the documentation is lacking. We are adding some all
the time. I wish we had the possibility to do *only* that for a
while, but that's not wha
I've used a perl script to convert all the .pod documentation
to XML, docbook format.
Each is a chapter, wouldn't take much to build a wrapper
which included them all in a 'book'
Attached is an example. x509_new.pod
in html format, from the xml.
docbook to pdf is also avail
No. OpenSSL documents the OpenSSL API, not the Telnet Protocol. The
Telnet START_TLS option is currently documented as an IETF
Internet-Draft published by the TN3270E Working Group.
> Is there any good documentation on which calls in which order a Telnet application
>should make for
On Fri, Sep 29, 2000, Jeff Roberts wrote:
> I know where telnet is documented. Where is Openssl documented ?
http://www.openssl.org/docs
If you didn't know that, where did you get the source code and the
address of this mailing list?
> I.E. Where is SSL_connect() documented ??
http://www.op
At 01:10 PM 9/29/00 -0400, someone wrote:
>... The documentation on the Openssl web site only lists the prototypes
>for each api call.
>
>I was taught a long time ago that a product without documentation is
>worthless.
>If we have no documentation, we have nothing !
OK
Hi there, new to the list, just wanted to *wave* :)
Are there any good sources of documentation on openssl? The man page gives
some information, and I've found some examples in the list archives, but not
quite what I'm looking for.
Basically I've been tasked to write a s
Hi,
I've found an explanation in the SSL on-line documentation that should be
corrected.
In http://www.openssl.org/docs/ssl/SSL_get_session.html#,
"If the data is to be kept, SSL_get1_session() will increment the reference count and
the
session will stay in memory until explicitly
Hello. I'd like to report a possible documentation error in OpenSSL
0.9.6c...
In the INSTALL.W32 file, the following is listed in the Tweaks section of
the Visual C++ instructions:
(line 79)
There are various changes you can make to the Win32 compile environment.
By
default the library i
Just a small typo:
--- doc/crypto/ripemd.pod~ 2006-10-27 21:59:48.0 +
+++ doc/crypto/ripemd.pod 2008-11-08 23:13:22.0 +
@@ -13,7 +13,7 @@
unsigned char *md);
int RIPEMD160_Init(RIPEMD160_CTX *c);
- int RIPEMD160_Update(RIPEMD_CTX *c, const vo
Hello,
I have two suggestions about the documentation.
First suggestion, a minor one about INSTALL.W32. Every time I go to
change ./ms/do_ms.bat so I can enable debugging symbols I change the
line
perl util\mk1mf.pl no-asm VC-WIN32 >ms\nt.mak
I add 'debug' in last place
[[EMAIL PROTECTED] - Wed Oct 2 10:07:43 2002]:
> Hello,
>
> I have two suggestions about the documentation.
>
> First suggestion, a minor one about INSTALL.W32. Every time I go to
> change ./ms/do_ms.bat so I can enable debugging symbols I change
the
> line
>
>
[levitte - Fri Oct 4 14:32:48 2002]:
> As for the POD files, I'll ponder a little more about your proposed
> change.
No time to get that into 0.9.7, I'll move this to 0.9.7a.
--
Richard Levitte
__
OpenSSL Project
Either implementation or documentation of the EVP_SealInit
function is incorrect as the iv Parameter is an output
parameter not an input parameter of the function.
0.9.6g and 0.9.7 both have this inconsistency but
since the C-code had been updated in 0.9.7 and the
documentation had not, I decided
Here's a patch for d2i_SSL_SESSION.pod, pointing out a pitfall when using
i2d_SSL_SESSION
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]> you wrote:
> openssl-0.9.2b:
> docu about:
> keyUsage (PKIX key usage) takes the flags: .
> ./doc/openssl.txt (line 206):
> keyEncipherment, dataEncipherment, keyAgreement, keyCertSign, cRLCertSign
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
After a particularly frustrating day of having to reverse-engineer the
openssl.conf configuration file from the source code. I decided to
write some documentation for it.
I have attached a draft version, written with too little sleep and
after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please find attched the openssl.conf documentation that I wrote a
while ago. I have tidied it up a little since I last posted it a
few months back, but there have been no real changes.
There was a bit of debate when I previously posted it on what
"Hellan,Kim KHE" wrote:
>
> Officially I don't think so.
>
> But check out http://www.columbia.edu/~ariel/ssleay/...
>
> which is the most comprehensive documentation I have found so far.
Actually, Ulf, Bodo and Steve have been doing great work on docco
l
I don't know if this is the proper place to bring this up, or if a
project fork would be more appropriate (given the investment that
exists in the current API/ABI)...
I would like to be able to determine and document what parameters of a
cryptographic object passed to any given library function m
Another small chunk of manual pages,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129
Universitaetsplatz 3-4, D-03044 Cott
I know where telnet is documented. Where is Openssl documented ? I.E. Where is
SSL_connect() documented ?? I see a prototype of it, but I don't see and type of
description on what it performs, what other openssl calls are prerequisites , etc
Thank You,
Jeff Roberts
Thank you, I am new to this. Can you tell me what application reads a POD file ?
jeff
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Aut
Right off the main openssl web page. I looked in the most obvious place, under the
"Documents" link of the openssl home page and did not find it !
__
OpenSSL Project http://www.openssl.org
Devel
Hi!
Some manual pages about SSL_CTX_load_verify_locations() and friends.
Best regards,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel.
Hi!
attached are manual pages for SSL_CTX_set_verify() and friends including
the *_set_verify_depth() functions as of the discussion about the exact
functionality.
I have also added some more information to SSL_CTX_load_verify_locations()
as the result of a discussion on openssl-users, where exp
ve* :)
>
>Are there any good sources of documentation on openssl? The man page gives
>some information, and I've found some examples in the list archives, but not
>quite what I'm looking for.
>
>Basically I've been tasked to write a server that will communicate with
On 28 Nov, Alan wrote:
> Are there any good sources of documentation on openssl? The man page gives
> some information, and I've found some examples in the list archives, but not
> quite what I'm looking for.
Wy do you need man pages when you can read source code? ;-)
>
On 28-Nov-2000 les wrote:
> I'm not sure if it's in every distro but in the latest stable release in
> openssl-0.9.6/demos/ssl/ there are two c+ files, cli.cpp and
> serv.cpp. they should give you a good starting point...
Ah, perfect. My appolagies, I'm on a debian system and completely for
These are no more c++ than my dog is president (although he would be
better than the US's other options). These are rote C. The names
should be changed to *.c within the source tree to aleviate linker
errors on several platforms.
--
Andrew
Alan wrote:
>
> On 28-Nov-2000 les wrote:
> > I'm not
On Sun, Nov 18, 2001 at 05:29:31PM -0500, [EMAIL PROTECTED] wrote:
> In http://www.openssl.org/docs/ssl/SSL_get_session.html#,
> "If the data is to be kept, SSL_get1_session() will increment the reference count
>and the
> session will stay in memory until explicitly freed with SSL_SESSION_free(3
ate it.
:-)
> As for the POD files, I'll ponder a little more about your proposed
> change.
In the meantime, I would like to help out with any documentation tasks.
Whether it is a documentation issue that hasn't been gotten to due to
lack of time, or a wish-list thing like "
ll
> other options.
Danke schön. I and all the other easily confused putzes appreciate it.
:-)
> As for the POD files, I'll ponder a little more about your proposed
> change.
In the meantime, I would like to help out with any documentation tasks.
Whether it is a documentation issue
Hello Openssl Developers,
Could you please update the documentation on BIO_read, particularly the BIO_read.pod
file!?
There is a paragraph in the file:
---
A 0 or -1 return is not necessarily an indication of an error. In particular when the
source/sink is non-blocking or of a
On Thursday 06 May 2004 08:45, Jim Schneider wrote:
> Here's a patch for d2i_SSL_SESSION.pod, pointing out a pitfall when using
> i2d_SSL_SESSION
Actually, that wasn't as clear as it should be - pp isn't getting clobbered,
what it points to (*pp) is getting clobbered.
___
Hi,
I was reading the documentation for SSL_shutdown() and noticed an error
on the beggining of the 4th paragraph of the section NOTES.
It reads:
"...will only send the alert and the set the SSL_SENT_SHUTDOWN flag..."
I believe it should be:
"...will only send the alert a
Done, thanks for the report.
Steve.
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAI
Is there API documentation available for OpenSSL? The fragments at
www.openssl.org/docs/ are somewhat minimalistic, alas.
Thank you,
tr.
__
OpenSSL Project http://www.openssl.org
Development
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please find attached a second draft of the openssl.conf
documentation. This version fixes several errors in the X.509v3
extensions section documentation.
Comments?
Regards,
Damien Miller
- --
| "Bombay is 250ms from New York in the new
1 - 100 of 179 matches
Mail list logo
