>From STATUS:
>o The installation under "make install" produces a very
> installation layout: $prefix/certs and $prefix/private dirs.
> That's not nice. Ralf suggests to move the two certs and
> private dirs either to $prefix/etc/, $prefix/lib/ or $prefix/share.
> Alt
On Thu, 31 Dec 1998, Ralf S. Engelschall wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> > Does the OpenSSL team also intend to adopt/coordinate the development
> > of the SSL client applications like SSLtelnet and SSLftp. Or are they
> > only interested in apache-ssl?
>
> > It would be a go
In article <[EMAIL PROTECTED]> you wrote:
> On Thu, 31 Dec 1998, Ralf S. Engelschall wrote:
>> In article <[EMAIL PROTECTED]> you wrote:
>> > Does the OpenSSL team also intend to adopt/coordinate the development
>> > of the SSL client applications like SSLtelnet and SSLftp. Or are they
>> > only
In article <[EMAIL PROTECTED]> you wrote:
>>From STATUS:
>>o The installation under "make install" produces a very
>> installation layout: $prefix/certs and $prefix/private dirs.
>> That's not nice. Ralf suggests to move the two certs and
>> private dirs either to $prefix/
What about those old/working files Eric left in the SSLeay 0.9.1b source tree
and which are still part of our CVS tree? These old/* (e.g. crypto/bn/old/)
and other working files (e.g. those .works files) spreaded over the tree are
not needed except for our history in case of problems. So I think
Hmm lets try this again...
I've just uploaded v0.53a of my PKCS#12 program. It should compile under
the latest OpenSSL tree. It probably will *not* compile under OpenSSL
0.9.1X.
It will compile under SSLeay still.
It's still under test and OpenSSL may change to break it so consider it
"experime
Ralph,
> > bin <-- openssl program
> > etc <-- openssl.cnf, certificates, private keys
> > include <-- header files
> > lib <-- library files
>
> This is a small top-level layout which then fits into all dedicated
> hierarchies and 99% of all shared hierarchie
Dr Stephen Henson wrote:
>
> Hmm lets try this again...
What was wrong with the first attempt?
Cheers,
Ben.
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition
In article <[EMAIL PROTECTED]> you wrote:
>> > bin <-- openssl program
>> > etc <-- openssl.cnf, certificates, private keys
>> > include <-- header files
>> > lib <-- library files
>>
>> This is a small top-level layout which then fits into all dedicated
>> h
> > Yes, this is much better. How about (possibly) temporarily generated
> > files? Should there be a standard location that OpenSSL enforces the
> > apps that use it to put tmp files? By temporary, I mean anything that
> > could last a few minutes to a few weeks.
>
> Do we have OpenSSL dist
On Sat, 2 Jan 1999, Ralf S. Engelschall wrote:
> I want to propose a less spreaded layout like and the use of a
> openssl.cnf instead of ssleay.cnf:
>
> > bin <-- openssl program
> > etc <-- openssl.cnf, certificates, private keys
> > include <-- header files
> > li
On Sat, 2 Jan 1999, Ralf S. Engelschall wrote:
>
> What about those old/working files Eric left in the SSLeay 0.9.1b
> source tree and which are still part of our CVS tree? These
> old/* (e.g. crypto/bn/old/) and other working files (e.g. those
> .works files) spreaded over the tree are not need
Clifford Heath wrote:
>
> > 3. Has anyone tried RSA product called "SSL-C", which is a set of object
> > libraries for developing software using the SSL protocol or has anyone tried
> > the SSLPlus?
>
> I got an eval. It's an enhanced version of SSLeay with some of the API
> entry points hidden.
Hi,
I have just finished a first patch for the cipher selection and sorting
improvements, especially for 56bits.
It features a separate long int for "export state" and cipher strength.
I have also made some small change to make the use of the SSL_IS_EXPORT...
and SSL_C_IS_EXPORT... etc macros mor
Hi there,
About April Ben made a change to crypto/x509/by_file.c to with adding CRLs
to the X509_LOOKUP as well as certs. However, the return value of that
function has me a bit confused - after that chance, the function
considered it an error unless the file contained a cert AND a CRL. I would
h
Geoff Thorpe wrote:
>
> Hi there,
>
> About April Ben made a change to crypto/x509/by_file.c to with adding CRLs
> to the X509_LOOKUP as well as certs. However, the return value of that
> function has me a bit confused - after that chance, the function
> considered it an error unless the file co
On 03 Nov 1999 20:04:07 EST, William M. Perry wrote:
> "Ramsay, Ron" <[EMAIL PROTECTED]> writes:
>
> > I don't have an opinion on producing LDAP DNs but I think you should use
> > the v3 form (RFC 2253) rather than the v2 form.
>
> Well, 1485 is obsoleted by 1779, which is then in turn obsoleted
17 matches
Mail list logo
