| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
ok jsing
|
| |
|
|
|
|
|
|
|
|
| |
As far as I can tell, this way of generating "C code" was only used to add
stuff to pretty regress and even prettier speed "app" and otherwise it just
served to make the library maintainer's lives even more miserable.
ok jsing
|
|
|
|
|
|
|
|
| |
This removes the last in-tree dependency on EC_METHOD_get_field_type()
and EC_GROUP_method_of() and removes some dead code which would generate
code that wouldn't compile if it was reachable.
ok jsing
|
| |
|
|
|
|
|
|
|
| |
/*#define SSL_HOST_NAME "www.netscape.com" */
/*#define SSL_HOST_NAME "193.118.187.102" */
and
/*#define TEST_CERT "client.pem" *//* no default cert. */
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having constant arrays in a header is just stupid (whether the constants
are static or not), and most of the contents of these two headers clearly
belongs into a C file. Since the garbage pile that is speed.c was not ugly
enough, merge all of it there, since it is the only consumer.
discussed with jsing
PS: still waiting for that elusive volunteer who reworks libdes's speed.c
into something resembling C code.
|
| |
|
|
|
|
| |
discussed with jsing
|
|
|
|
|
|
| |
This is an extra header for two stupid constants...
discussed with jsing
|
|
|
|
| |
discussed with jsing
|
|
|
|
|
|
|
| |
The competition whether the code or the standard it implements is worse
is still ongoing, and still has two strong competitors...
ok jsing
|
|
|
|
|
|
|
| |
also remove a few NULL checks before free and drop a cryptic comment about
not needing to free x - hard to free what's not there...
ok jsing
|
|
|
|
|
|
| |
The options were already removed from the manual in 91e7614a.
From Renaud Allard (hand-applied since patch was mangled)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream decided that this nonsense was worth an ABI break and added stuff
to the X509_CTX so they could hang the issuer's public key off it so that
they could adjust the key identifiers as needed. Let's avoid that and do
it the slightly less nasty way by updating the AKI and SKI as needed.
We only do this when force pubkey is in place so we don't change the
semantics of the batshit crazy config language that nobody understands.
ok job
|
|
|
|
|
|
|
| |
secp160r1 and nistp192 are no longer available in libcrypto. Should have
been committed along with disabling these curves, but was missed.
ok jsing
|
| |
|
|
|
|
| |
The public API will be removed. This fixes its only consumer.
|
| |
|
|
|
|
| |
ok beck
|
|
|
|
|
|
| |
The underlying API will be removed, so these commands have to go.
ok beck
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Documentation on what the Microsoft-specific local machine keyset and the
cryptographic service provider are actually good for is hard to find. For
some reason (perhaps one million and two arguments for PKCS12_create() was
considered two too many) these hang off the EVP_PKEY in the attributes
member, which serves no other purpose.
Every use of EVP_PKEY (of which there are far too many) pays extra memory
taxes for this fringe use case. This complication is not worth it.
ok miod
|
| |
|
|
|
|
|
|
|
|
|
| |
This option allows to verify certs in a CMS object against additional
CRLs.
Ported from work by Tom Harrison from APNIC
OK tb@
|
|
|
|
| |
Reduces diff in -portable
|
|
|
|
|
|
| |
remove the re-arming in the handler. Better than using siginterrupt(),
and avoids the errno saving requirement in the handler also.
ok guenther millert
|
| |
|
| |
|
|
|
|
| |
ok jsing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Google killed efforts to have SPKAC in html5 by zapping it from chrome
a decade ago. This effort doesn't look like it's going anywhere:
https://datatracker.ietf.org/doc/draft-leggett-spkac/
Unfortunately, PHP and Ruby still support NETSCAPE_SPKI, so we can't
kill that code, but I see no real reason we need to support this in our
openssl command. If the need should arise we can write a somewhat less
poor version of this.
ok jsing
|
|
|
|
|
|
|
| |
This is very poorly written code and now the only consumer of some
public API that should not have survived the turn of the millenium.
ok jsing
|
|
|
|
|
| |
of type 'volatile sig_atomic_t'
ok tb
|
|
|
|
| |
ok jsing
|
|
|
|
| |
suggested by jsing
|
|
|
|
| |
ok job jsing
|
|
|
|
| |
ok job jsing
|
|
|
|
| |
partly checked by millert@
|
| |
|
| |
|
|
|
|
|
|
| |
Well, it's a toolkit alright, and a terrible one at that, but TLS v1
(which is this beloved toolkit's name for TLS v1.0) is a thing firmly
from the past, so drop the v1.
|
|
|
|
| |
CID 492603
|
|
|
|
|
|
|
|
|
| |
The ts code is its own kind of special. I only sent this diff out to hear
beck squeal. This diff doesn't actually fix anything, apart from (maybe)
appeasing some obscure static analyzer. It is decidedly less bad than a
similar change in openssl's issue tracker.
ok beck
|
| |
|
|
|
|
| |
Noticed by Christian Andersen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This version of GOST is old and not anywhere close to compliant with
modern GOST standards. It is also very intrusive in libssl and
makes a mess everywhere. Efforts to entice a suitably minded anyone
to care about it have been unsuccessful.
At this point it is probably best to remove this, and if someone
ever showed up who truly needed a working version, it should be
a clean implementation from scratch, and have it use something
closer to the typical API in libcrypto so it would integrate less
painfully here.
This removes it from libssl in preparation for it's removal from
libcrypto with a future major bump
ok tb@
|
|
|
|
|
|
|
|
|
| |
The ability to generate a new certificate is useful for testing and
experimentation with rechaining PKIs.
While there, alias '-key' to '-signkey' for compatibility.
with and OK tb@
|
|
|
|
|
|
|
|
| |
The -set_issuer, -set_subject, and -force_pubkey features can be used to
'rechain' PKIs, for more information see https://labs.apnic.net/nro-ta/
and https://blog.apnic.net/2023/12/14/models-of-trust-for-the-rpki/
OK tb@
|