summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* document X509_EXTENSION_dup(3);schwarze2021-10-291-8/+20
| | | | | | while here, add the missing const qualifier to the obj argument of X509_EXTENSION_create_by_OBJ(3) and correct a typo in the argument name of X509_EXTENSION_get_data(3)
* new manual page X509_REQ_print_ex(3),schwarze2021-10-294-6/+184
| | | | also documenting X509_REQ_print(3) and X509_REQ_print_fp(3)
* document X509_REQ_to_X509(3)schwarze2021-10-281-7/+38
|
* unwrap a linetb2021-10-281-3/+2
|
* document X509_to_X509_REQ(3)schwarze2021-10-281-4/+26
|
* sorttb2021-10-281-2/+2
|
* Mechanical KNF in preparation for changingbeck2021-10-2812-1583/+1653
|
* Add headers normally contained in include/openssl, verbatim from 1.1.1beck2021-10-282-0/+554
|
* Import Certificate Transparency verbatim from OpenSSL 1.1.1beck2021-10-2813-0/+2321
| | | | | | | This is not yet hooked up and will not compile. Follow on commits will KNF and then make it build. ok jsing@ tb@
* openssl-ruby tests: rework for x509_alt.c r1.3 and r1.5.tb2021-10-281-6/+9
| | | | | | | ruby can no longer generate certs with bogus wildcards in it to check that they will fail to verify when creating TLS connections. It will throw an error. This change needs openssl-ruby-tests-20211024p0 or later to work.
* Bring back r1.3, ok becktb2021-10-281-3/+47
| | | | | | | | | | | Original commit message from beck: Validate Subject Alternate Names when they are being added to certificates. With this change we will reject adding SAN DNS, EMAIL, and IP addresses that are malformed at certificate creation time. ok jsing@ tb@
* Fix HISTORY section: 6.9 -> 7.0tb2021-10-271-3/+3
|
* new manual page X509_REQ_add_extensions(3)schwarze2021-10-274-4/+148
| | | | documenting six functions for extensions in certification requests
* add some .Xrs involving recently added pagesschwarze2021-10-277-15/+22
|
* minor tweaks to wording and punctuation,schwarze2021-10-271-10/+19
| | | | and add .Xrs to relevant objects
* Minor tweaks:schwarze2021-10-271-9/+12
| | | | | | | | | * Say "number of bytes" instead of "length of bytes". * Remove mention of a BUGS section that exists neither here nor in OpenSSL. * List all authors who contributed Copyright-worthy amounts of text. * Remove years from the Copyright line that saw no non-trivial changes. * Add the year 2014: that's when Emilia wrote the i2d_re_X509_tbs() text. * Improve merge comments.
* Revert version 1.3 - not allowing the creation of bogus certificatesbeck2021-10-271-47/+3
| | | | | | | | | breaks the ruby regression tests that expect to make bogus certificates and see that they are rejected :( I am reverting this for now to make the regress tests pass, and will bring it back if we decide to patch the regress tests to remove the problem cases
* Fix to correctly parse the 'to' time into the to_tmbeck2021-10-271-2/+2
|
* Add ASN1_TIME_diff from OpenSSL.beck2021-10-274-5/+106
| | | | | | The symbol is not yet exposed and will show up with tb@'s forthcoming bump ok tb@ jsing@
* Merge documentation for i2d_re_X509*_tbs(3) from OpenSSL 1.1tb2021-10-261-4/+67
|
* spelling fixes;jmc2021-10-262-4/+4
|
* install X509_get_extension_flags.3 and X509_SIG_get0.3tb2021-10-261-1/+3
|
* Remove a line documenting that X509_get_X509_PUBKEY(3) is missingtb2021-10-261-2/+1
| | | | discussed with schwarze
* Document X509_get0_pubkey.3tb2021-10-261-3/+14
|
* Document new signature of X509_get_X509_PUBKEY() and remove claimtb2021-10-261-5/+3
| | | | | that the API is implemented as a macro. This will change in an upcoming bump.
* Add tlsfeature NIDjob2021-10-262-0/+2
| | | | OK beck@ tb@
* Add RFC 3779 checks to both legacy and new verifierjob2021-10-262-2/+20
| | | | OK beck@
* Free memory on text exit to make asan quieterbeck2021-10-261-53/+83
| | | | ok tb@
* new manual page X509_REQ_add1_attr(3) documenting nine functionsschwarze2021-10-266-8/+199
| | | | for X.501 Attributes in PKCS#10 certification requests
* correct a wrong function name below RETURN VALUESschwarze2021-10-261-3/+3
|
* document X509_REQ_dup(3)schwarze2021-10-261-5/+20
|
* document d2i_X509_PUBKEY(3) and i2d_X509_PUBKEY(3);schwarze2021-10-261-23/+57
| | | | while here, apply the usual conventions for naming d2i and i2d arguments
* Validate Subject Alternate Names when they are being added to certificates.beck2021-10-263-9/+61
| | | | | | | With this change we will reject adding SAN DNS, EMAIL, and IP addresses that are malformed at certificate creation time. ok jsing@ tb@
* Revise regress for removal of SSL_SESSION_INTERNAL.jsing2021-10-261-27/+27
|
* sorttb2021-10-251-17/+17
|
* sort. alphanumerics have lower ASCII values than '_'tb2021-10-251-5/+5
|
* Install SSL_read_early_data.3. I should have done this during the lasttb2021-10-251-4/+2
| | | | libssl bump.
* Revert accidental change.jca2021-10-251-1/+2
| | | | Dunno why this ended up here, cvs is always full of surprises.
* Make brk() and sbrk() weak again as intended.jca2021-10-251-2/+1
| | | | | | Apparently spotted by mortimer@ while working on clang 13 and amd64. No actual change on sparc64 as this architecture still uses ld.bfd. ok kettenis@
* new manual page EVP_PKCS82PKEY(3), also documenting EVP_PKEY2PKCS8(3)schwarze2021-10-256-10/+77
|
* new manual page PKCS8_pkey_set0(3)schwarze2021-10-256-9/+177
| | | | documenting four PKCS#8 PrivateKeyInfo accessors
* Add missing RCS markerstb2021-10-252-0/+2
|
* Zap two unused includesjca2021-10-252-4/+0
| | | | Spotted by egcc. ok tb@
* Garbage collect another unused variable.jca2021-10-251-4/+1
| | | | Spotted by egcc and probably clang 13. ok tb@
* document ASN1_STRING_set0(3)schwarze2021-10-251-6/+29
|
* Add record processing limit to DTLS code.jsing2021-10-252-3/+18
| | | | | | | | This is effectively the same record processing limit that was previously added to the legacy TLS stack - without this a single session can be made to spin on a stream of alerts or other similar records. ok beck@ tb@
* Use ssl_force_want_read() in the DTLS code.jsing2021-10-253-44/+15
| | | | | | Also mop up some mostly unhelpful comments while here. ok beck@ tb@
* Fold SSL_SESSION_INTERNAL back into SSL_SESSION.jsing2021-10-2510-121/+110
| | | | ok beck@ tb@
* Drop two uses of the terrible asn1 kludge spotted by antontb2021-10-251-3/+3
|
* For open/openat, if the flags parameter does not contain O_CREAT, thederaadt2021-10-249-20/+20
| | | | | | | | | | | | | 3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-11 22:40:24 +0000