Closed (fixed)
Project:
Asymmetric (private/public) Keys
Version:
1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Dec 2024 at 14:56 UTC
Updated:
12 Jan 2026 at 16:44 UTC
Jump to comment: Most recent
Comments
Comment #3
john franklin commented@roderik, can you take a look at this MR?
Comment #4
roderikAdded review comments.
I also had a voice in the back of my mind that we should be really careful how we use keys created in this way, because we can't trust that the webserver has a good openssl configuration. (I think I read that somewhere.) But I'm probably being paranoid, because I can't find any docs saying that, anymore / we're not doing anything special / PHP's OpenSSL extension is likely good.
But... how about e.g. adding this to the README (near the top, as the first 'separate section')?
(And add a 4th point at the top:
- a screen to create a new key pair.)Comment #5
roderikComment #6
john franklin commentedThanks for the review. I'll go through these today and update the MR.
Comment #7
roderikI don't know of anything else. From my tests, it works well, and does not get in the way of theoretical future extension work.
Comment #8
john franklin commentedAddressed the remaining issues.
Comment #9
john franklin commentedAlso added #3564920: Support creating a cert when creating a key pair to cover the certificate generation half of this issue.
Comment #10
roderikTested the last change. Don't know if I should RTBC or just merge :-)
Added a README adjustment.
Comment #11
john franklin commentedUpdating the title of this issue. The certificate part will be done under #3564920: Support creating a cert when creating a key pair.
I say just merge. RTBC is usually for non-maintainers to show a patch is ready for the maintainers to merge.
Comment #12
roderikI'm merging... after sneaking in another commit that only changes comments on a method that is never called. (Removes TODOs.)
Comment #14
roderik