X509: use V3 when extensions present; certs generated by apps bear X.509 V3 by default#19271
X509: use V3 when extensions present; certs generated by apps bear X.509 V3 by default#19271DDvO wants to merge 4 commits intoopenssl:masterfrom
Conversation
|
The failing |
|
And how about the API level? I suggest adapting |
|
@DDvO could you please try the gost-engine/engine@a6b9052 ? |
Thank you for your immediate handling - with this updated submodule reference it works fine :) |
Will do with the next push. |
7276dc9 to
a3eb6c1
Compare
|
@t8m, ok now? |
Thanks @t8m for your further comments, which I had overlooked so far, but now they are handled. |
fb22f54 to
24cfffa
Compare
|
Rebased to fix merge conflict in Ping for 2nd review. |
24cfffa to
68c853e
Compare
|
Rebased to fix trivial merge conflict in |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago |
|
Adding some more tests would be nice. |
Done. |
|
@t8m wanna reconfirm, now since more tests have been added? |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago |
|
ping for second review |
|
This pull request is ready to merge |
…alues Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Hugo Landau <[email protected]> Reviewed-by: David von Oheimb <[email protected]> (Merged from #19271)
…e function Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Hugo Landau <[email protected]> Reviewed-by: David von Oheimb <[email protected]> (Merged from #19271)
… is given Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Hugo Landau <[email protected]> Reviewed-by: David von Oheimb <[email protected]> (Merged from #19271)
When preparing #19076 I found that by default (when no X.509 v3 extensions are used),
certs generated by the
x509,ca, andreqapps still have X.509 version 1.This is anachronistic and causes various issues, such as missing key identifiers for chain building
and no clear distinction between CA certs and EE certs.
This PR makes sure V3 is used,
with the exception of a new
-x509v1option of thereqapp, which implies the-x509option whileforcingusing V1 unless extensions are given (which requires V3).On this occasion, also
apps/req.c: properly report parse errors byduplicated(); simplify the functionCHANGES.md:'added' -> 'add', 'extended' -> 'extend' for OpenSSL 3.1 entriestest/trace_api_test.c: fix gcc error on-Werror=strict-prototypesChecklist