| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
defines - do not rely on another heading making those available for us.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Both functions are listed in <openssl/asn1.h>
and in OpenSSL doc/man3/d2i_X509.pod.
After reading the code, i'm not amused. You wouldn't think that
it might take eight stack levels to decode a constant sixteen bit
value that does not even allow a single content octet, or would
you? Nota bene, this is an average of four stack levels for each
non-zero bit decoded... :-(
|
|
|
|
|
|
| |
commit 67adf0a7c273a82901ce8705ae8d71ee2f1c959c
Author: Markus Triska <triska@metalevel.at>
Date: Sun Dec 25 19:58:38 2016 +0100
|
|
|
|
|
| |
encoding functions from scratch. All 46 functions are listed
in OpenSSL doc/man3/d2i_X509.pod.
|
| |
|
| |
|
|
|
|
| |
both listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
|
|
|
|
|
| |
d2i_X509_REVOKED(3), and i2d_X509_CRL_INFO(3), all listed in
<openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
|
|
|
|
|
| |
Use simpler standard wordings.
Add X.509 references.
|
| |
|
|
|
|
|
|
| |
Improve the one-line description.
Use the standard wordings in some places.
Complete the RETURN VALUES section.
|
|
|
|
|
| |
from scratch. All six functions are listed in <openssl/x509.h>
and in OpenSSL doc/man3/d2i_X509.pod.
|
|
|
|
|
|
| |
in this page - but do include documentation for immediate
subobjects that are used nowhere else. All six functions
listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
|
|
|
|
|
|
|
|
|
|
| |
Improve .Nd.
Sort functions.
Use the same parameter names as in ASN1_item_d2i(3).
Point to ASN1_item_d2i(3) for all he details.
Delete all the information that's now in ASN1_item_d2i(3).
Add missing entries to the RETURN VALUES section.
Add STANDARDS section.
|
|
|
|
|
|
|
|
|
|
|
| |
Also document d2i_PKCS8_bio(3), i2d_PKCS8_bio(3), d2i_PKCS8_fp(3),
and i2d_PKCS8_fp(3) while here, listed in <openssl/x509.h>
and in OpenSSL doc/man3/d2i_X509.pod.
No, these functions have nothing to do with the many other d2i_PKCS8*(3)
functions all around, and nothing with PKCS#8 at all in the first place.
Read the BUGS section. I couldn't make this stuff up.
|
|
|
|
|
|
| |
with i2d_PKCS8PrivateKeyInfo_bio(3).
While here, polish the cross references.
|
|
|
|
|
|
|
|
| |
listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
These functions are very similar to i2d_PrivateKey(3) but very
different from i2d_PKCS8PrivateKey_bio(3), that's why they go into
this manual page and not into the other one. When the naming was
decided, somebody clearly considered too briefly or too long.
|
|
|
|
|
| |
These six function are listed in <openssl/x509.h>
and in OpenSSL doc/man3/d2i_X509.pod.
|
|
|
|
|
| |
from scratch. All these functions are listed in <openssl/ocsp.h>
and in OpenSSL doc/man3/d2i_X509.pod.
|
|
|
|
|
| |
from scratch. All functions listed in <openssl/ts.h>
and in OpenSSL doc/man3/s2i_X509.pod.
|
| |
|
| |
|
|
|
|
| |
preprocessor output, excluding line numbers and newlines.
|
|
|
|
| |
preprocesssor output.
|
|
|
|
|
| |
nothing but markers for utils/mkstack.pl... and we removed the code that
generated more macros from these markers in 2014.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
line numbering and new lines.
|
| |
|
| |
|
|
|
|
| |
listed in <openssl/pkcs7.h> and OpenSSL doc/man3/d2i_X509.pod
|
|
|
|
|
|
| |
It is already referenced by one other manual page.
All these functions are listed in <openssl/pkcs7.h>
and in OpenSSL doc/man3/d2i_X509.pod.
|
|
|
|
|
|
| |
It is already referenced from some other manuals.
All these functions are listed in <openssl/pkcs12.h>
and in OpenSSL doc/man3/d2i_X509.pod.
|
|
|
|
|
| |
found in OpenSSL doc/man3/d2i_X509.pod.
Add STANDARDS references.
|
| |
|
|
|
|
|
|
|
|
|
| |
Simplify one-line description.
List each function with the correct header file.
Use the same parameter names as in ASN1_item_d2i(3).
Point to ASN1_item_d2i(3) for details.
Sort the text.
Add some useful cross references.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
error messages, instead of libssl error strings. This gives us messages
like:
certificate verification failed: certificate has expired
Instead of:
14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
This also lets us always enable peer verification since the no verification
case is now handled via the callback.
Tested by tedu@
ok beck@
|
| |
|
|
|
|
|
|
|
|
| |
unintentionally changed during the CBS/CBB rewrite.
Issue reported by jeremy@ due to failing ruby tests.
Analysis and near identical diff from Kazuki Yamaguchi <k at rhe.jp>.
|