Closed elijh closed 11 years ago
Oh wows, I was about to submit a patch for this. Let's get this change out!
So far, crickets from cchandler. At some point, it might be time to fork. There are a bunch of other patches I would like to submit, but I have held off until life appears again in this project.
It looks like your patch will break if the CSR is loaded from a file and to_x509_csr is called. Raising an error on lack of private key would at least prevent that. Of course that behavior probably falls outside of the use case for this gem.
Sorry! I've been an OSS jerk :-). I had an overly aggressive email filter... Let me try and take a solid look at this, this weekend.
Cool! No worries. Glad to hear you are back.
Thanks for the contribution! Merged.
For a CSR to be valid, it must be signed by the private key that corresponds to the CSR.
There is a handy tool to validate CSRs here: http://certlogik.com/decoder/
This small patch ensures that the CSR is signed.