crypto/x509: fix certificate request creation with RSA-PSS

[ycongal-smile]

In case of a RSA-PSS algorithm, the hashFunc of CreateCertificateRequest
is embedded in a rsa.PSSOptions struct. Given to key.Sign(), this will
generate a proper RSA-PSS signature.

Pasted from the RSA-PSS handling code in CreateCertificate()

Fixes #45990

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[ycongal-smile]

The corporate CLA is still in the process of being signed. This is frustratingly long but we'll do it.

[ycongal-smile]

@googlebot I signed it!

[ycongal-smile]

Rebased my commits on master and tested again. Still OK.

[cipherboy]

@ycongal-smile (I don't work on Golang). You might need a fresh PR to get it mirrored into the proper PR review queue. They don't use GH so if it doesn't get mirrored into https://go-review.googlesource.com/ it won't be reviewed (and I don't see a link here or it in the search feature there).

[ycongal-smile]

@ycongal-smile (I don't work on Golang). You might need a fresh PR to get it mirrored into the proper PR review queue. They don't use GH so if it doesn't get mirrored into https://go-review.googlesource.com/ it won't be reviewed (and I don't see a link here or it in the search feature there).

Ok I'll try this. Thanks!

[ycongal-smile]

Closing this PR to open a fresh one and hopefully the new one will be picked up by the bots.

[gopherbot]

This PR (HEAD: 2914abc) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/431875 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

[ycongal-smile]

Well this was unexpected... I'll reopen then :)

[gopherbot]

This PR is being closed because golang.org/cl/431875 has been abandoned.

GitHub PR #46029 has been closed.

[cipherboy]

@ycongal-smile Looks like you might need to mark the CL as not abandoned? :/

[ycongal-smile]

I opened a new PR here : #55153