| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
It's the only way to be sure.
|
|
|
|
|
| |
invoked will cause breakage. US Users - DO NOT try to turn on
IDEA - the sources are not included.
|
|
|
|
|
|
| |
IDEA fix earlier today.
Bring back IDEA from the dead (but not compiled by default).
|
|
|
|
| |
(To avoid patent hassles).
|
| |
|
|
|
|
|
|
| |
via syslog instead.
Reviewed by: jkh
|
| |
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| | |
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| | |
|
| |
| |
| |
| |
| | |
Submitted by: Ben Rosengart <ben@narcissus.net>
Matthew D. Fuller <fullermd@futuresouth.com>
|
| |
| |
| |
| | |
jamming new chapters in front of it :)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the librsa* library and reports which version of the library (OpenSSL/RSAREF)
is being used.
This is then used in openssh to detect the failure case of RSAREF and a RSA key
>1024 bits, to print a more helpful error message than 'rsa_public_encrypt() fai
led.'
This is a 4.0-RELEASE candidate.
|
| |
| |
| |
| |
| |
| | |
RSA library.
Reviewed by: peter, jkh
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Reorganize and unify libcrypto's interface so that the RSA implementation
is chosen at runtime via dlopen().
This is a checkpoint and may require more tweaks still.
|
| |
| |
| |
| |
| |
| |
| | |
Reorganize and unify libcrypto's interface so that the RSA implementation
is chosen at runtime via dlopen().
This is a checkpoint and may require more tweaks still.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the rsa stubs for libcrypto. libcrypto.so now uses dlopen() to
implement the backends for either the native or rsaref implemented
RSA code.
This involves:
- unifying the libcrypto and openssl(1) source so there is no
#ifdef RSAref variations.
- using weak symbols and dlopen()/dlsym() routines to access the
rsa method vectors.
Releases will enable the user to choose International, US (rsaref) or
no RSA code at install time.
'make world' will DTRT depending on whether you have the international
or US source. For US users, you must either install rsaref (the port
or package) or (if you don't fear RSA Inc) use the (superior)
International rsa_eay.c code.
This has been discussed at great length by the affected folks and even
we have a great deal of confusion. This is a checkpoint so we can tune
the results. This works for me in all permutations I can think of and
should result in a CD/ftp 'release' just about doing the right thing now.
|
| |
| |
| |
| |
| | |
needs some more thought for the static case. Should we provide weak
error-generating stubs for static binaries if -lrsaref was forgotten?
|
| | |
|
| | |
|
| |
| |
| |
| | |
but simply lets us sync up on the solution as it's evolved.
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
cryptography here.
|
| |
| |
| |
| | |
'VENDOR-crypto-openssl'.
|
| | |
|
| |
| |
| |
| | |
Reviewed by: Ben Laurie <ben@openssl.org>
|
| | |
|
| | |
|
|\ \
| |/
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| | |
infringement reasons.
|
|/
|
|
| |
places), and we don't want people to get in trouble just for having it.
|
|
|