| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
early attempt at getting kernel-assisted crypto(4) used by libcrypto, before
the engine API existed, and has been #if 0'd out for ages anyway.
No API/ABI change.
|
|
|
|
|
|
|
| |
in a bunch of places inside the TLS engine, to try to keep entropy high.
I wonder if their moto is "If you can't solve a problem, at least try
to do it badly".
ok miod
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
| |
ok deraadt@
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
| |
that it is easier to find code pieces. They are getting in the way.
ok miod
|
|
|
|
|
|
|
| |
an alternative backend for BIGNUM calculations. It is PoC code that
is not enabled in OpenSSL and probably not used by anymore.
ok deraadt@
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
|
| |
could be maintained in an external package.
"it should probably go" beck@
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
| |
makes sense to beck@
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
| |
readable. This pass is whitespace only and can readily be verified using
tr and md5.
|
|
|
|
|
| |
but after cross-checking with 1.0.1g sources, they are not coming from
my change.
|
|
|
|
| |
in my last change.
|
| |
|
| |
|
|
|
|
| |
FPGA-based device is long obsolete.
|
| |
|
|
|
|
| |
external libraries that aren't covered by the same license.
|
|
|
|
|
|
| |
follow soon.
Tweaks from an ok jim@
|
|
|
|
|
|
| |
#if OPENSSL_SYS_NOTYOURS
<whole file>
#endif
|
|
|
|
| |
ok deraadt@
|
| |
|
|
|
|
| |
ok beck deraadt
|
| |
|
|
|
|
|
|
| |
which did shutdown + close, all nasty and surprising. Use the raw
syscalls that everyone knows the behaviour of.
ok beck matthew
|
|
|
|
| |
ok deraadt@
|
|
|
|
|
| |
noticed by mattheew and deraadt
ok deraadt@
|
|
|
|
| |
ok deraadt@
|
|
|
|
| |
ok deraadt@
|
|
|
|
| |
ok miod@, deraadt@
|
|
|
|
|
|
|
| |
know that MS_STATIC doesn't mean it is static? How far can lies
and half-truths be layered? I wonder if anyone got fooled, and
actually returned a pointer..
ok beck
|
| |
|
| |
|
|
|
|
| |
ok deraadt@
|
|
|
|
|
| |
systems, most of which in any sane world will want to do something
more modern anyways.
|
| |
|
|
|
|
| |
ok miod@ deraadt@
|
|
|
|
|
|
|
|
|
| |
relevant anymore. OpenSSL should have a better way to include 3rd
party engines: either completely and free or external. But including
a wrapper for a non-free wrapper in the code base does not make much
sense and could also be provided by the vendor.
ok deraadt@
|
|
|
|
|
|
|
|
|
| |
non-free libraries. OpenSSL should have a better way to include 3rd
party engines: either completely free or external. But including a
wrapper for a non-free wrapper in the code base does not make much
sense and could also be provided by the vendor.
ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
hardware.
The vendor_defns/cswift.h does not specify a copyright and
theoretically defaults to the OpenSSL license, but it also mentions
that it includes parts that have been "clipped" from CryptoSwift's
proprietary headers. This file should better include an explicit
copyright statement or mention OpenSSL's library instead of the
ambiguous "Attribution notice".
ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
| |
The vendor_defns/sureware.h file by Baltimore Technologies Ltd. has a
copyright that does not grant rights!
Vendor files should either include a compatible license in the
copyright statement or use OpenSSL's defaults, but adding a copyright
statement without any terms is not acceptable. It should not have
been included in the first place.
ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The vendor_defns/hw_ubsec.h file has a copyright that does not grant rights!
Vendor files should either include a compatible license in the
copyright statement or use OpenSSL's defaults, but adding a copyright
statement without any terms is not acceptable. It should not have
been included in the first place.
(The ubsec(4) kernel driver is not affected by this change)
ok deraadt@
|
|
|
|
|
|
| |
old PCI accelerator that was EOL'ed in 2005.
ok deraadt@
|