Flag modified when X509_req_info_st attribute updated#18879
Flag modified when X509_req_info_st attribute updated#18879gibeom-gwon wants to merge 2 commits intoopenssl:OpenSSL_1_1_1-stablefrom
Conversation
|
This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago |
DDvO
left a comment
There was a problem hiding this comment.
Thanks for your nice error report and fix.
I'm asking for further improvements and two small extensions of this PR.
71b22d6 to
5fceabf
Compare
|
@DDvO Thank you for your review. Edited as requested. By the way, should |
DDvO
left a comment
There was a problem hiding this comment.
Very nice that you reacted that swiftly on the change requests I gave earlier today.
See my follow-up comment and my answer on your good question.
5fceabf to
0755c9f
Compare
|
Edited as requested. I made one more commit for the functions in |
DDvO
left a comment
There was a problem hiding this comment.
A further round of comments.
…a updated We need to reencode X509_req_info_st if member data updated.
0755c9f to
c917e26
Compare
|
Sorry for the multiple mistakes. There will be no more mistakes in this round. (maybe) |
|
@t8m could you please have a look again. |
|
Can these commits be directly cherry-picked to master and 3.0 branches? If not, we'll need PRs against these branches as well before merging this. |
Unfortunately not - I'm preparing a respective PR for 3.0+. |
Done in #19090 and restricted this PR here to 1.1.1, so it can be fully approved now. |
|
@t8m please re-approve (for 1.1.1). |
|
Please merge only along the other PR. |
|
24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually. |
|
Since #19090 has been merged, it seems that this PR can also be merged. |
…a updated We need to reencode X509_req_info_st if member data updated. Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: David von Oheimb <[email protected]> (Merged from #18879)
… successful Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: David von Oheimb <[email protected]> (Merged from #18879)
|
Merged - thanks @t8m for the OTC approval |
…a updated We need to reencode X509_req_info_st if member data updated. Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: David von Oheimb <[email protected]> (Merged from openssl#18879)
… successful Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: David von Oheimb <[email protected]> (Merged from openssl#18879)
This is a variant of openssl/openssl#18879 for 3.0 and master, rebasing that PR from 1.1.1. On this occasion, I added a further commit that to add some NULL parameter checks and improve coding style in crypto/x509/{x509_req,x_all}.c Include 3 commits: X509 x509_req.c: Set 'modified' flag when X509_req_info_st member data updated X509 x_all.c: Set 'modified' flag when ASN1_item_sign{,_ctx} call was successful crypto/x509/{x509_req,x_all}.c: add some NULL parameter checks, improve coding style (Merged from openssl/openssl#19090)
If
X509_REQis created byPEM_read_X509_REQand only the attribute is changed, it is not exported as intended byPEM_write_X509_REQBecause the non-updatedencis used.This patch turns on the modified flag when an attribute change occurs.
To reproduce:
edited.csrRequested Extensions