Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
Quuxplusone
force-pushed
the
passphrase
branch
from
e022adb to
f78c336
Compare
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
… to the download page. Partly addresses chromium#369. Using a passphrase other than "badssl.com" for the other files would also be great, but is a larger change, I think.
|
Ping! @christhompson perhaps? |
2 participants
Create a "client-nopass.pem" for use with Python requests, and add it to the download page.
Partly addresses #369. The reader will now be alerted to some kind of difference between client.pem and client-nopass.pem, and will be more alert to the "Passphrase" column. (I've also changed the wording from "Password" to "Passphrase" as the latter is what openssl calls it, so it's what people would be Ctrl+F'ing for.)
Using a passphrase other than "badssl.com" (e.g. "hunter2", "correct horse battery staple", "god") for the other files would also be great, but is a larger change, I think.