Talk:Certificate signing request: Difference between revisions
crypto |
No edit summary |
||
Line 9: | Line 9: | ||
: I'm not sure what you mean by this. CSRs are "plain text"; their integrity is protected by a signature. They're normally transferred in some encoded form only because they need to be machine readable anyway, since they contain a digital signature. I've tried to update the introduction to clarify. [[User:Namnatulco|Namnatulco]] ([[User talk:Namnatulco|talk]]) 08:42, 16 February 2017 (UTC) |
: I'm not sure what you mean by this. CSRs are "plain text"; their integrity is protected by a signature. They're normally transferred in some encoded form only because they need to be machine readable anyway, since they contain a digital signature. I've tried to update the introduction to clarify. [[User:Namnatulco|Namnatulco]] ([[User talk:Namnatulco|talk]]) 08:42, 16 February 2017 (UTC) |
||
: There is no SSL certificate. [[SSL]] is an old and insecure protocol for transport layer security. The most famous format is the [[X.509] certificate. |
Revision as of 12:03, 9 October 2020
![]() | Computing: Networking / Software / Security Start‑class Low���importance | |||||||||||||||||||||||
|
![]() | Cryptography: Computer science Unassessed | ||||||||||||
|
The article currently doesn't answer why a CSR is necessary - why don't you just send the information in plain text? Something similar to the following text really needs to be included in the article itself and not just the talk page. — Preceding unsigned comment added by Martinording (talk • contribs) 16:19, 15 February 2017 (UTC)
A CSR or Certificate Signing request is a block of encrypted text that is generated on the server that the certificate will be used on. It contains information that will be included in your certificate such as your organization name, common name (domain name), locality, and country. It also contains the public key that will be included in your certificate. A private key is usually created at the same time that you create the CSR.
A certificate authority will use a CSR to create your SSL certificate, but it does not need your private key. You need to keep your private key secret. What is a CSR and private key good for if someone else can potentially read your communications? The certificate created with a particular CSR will only work with the private key that was generated with it. So if you lose the private key, the certificate will no longer work.
- I'm not sure what you mean by this. CSRs are "plain text"; their integrity is protected by a signature. They're normally transferred in some encoded form only because they need to be machine readable anyway, since they contain a digital signature. I've tried to update the introduction to clarify. Namnatulco (talk) 08:42, 16 February 2017 (UTC)
- There is no SSL certificate. SSL is an old and insecure protocol for transport layer security. The most famous format is the [[X.509] certificate.
- Start-Class Computing articles
- Low-importance Computing articles
- Start-Class Computer networking articles
- Low-importance Computer networking articles
- Start-Class Computer networking articles of Low-importance
- All Computer networking articles
- Start-Class software articles
- Low-importance software articles
- Start-Class software articles of Low-importance
- All Software articles
- Start-Class Computer Security articles
- Low-importance Computer Security articles
- Start-Class Computer Security articles of Low-importance
- All Computer Security articles
- All Computing articles
- Unassessed Cryptography articles
- Unknown-importance Cryptography articles
- Unassessed Computer science articles
- Unknown-importance Computer science articles
- WikiProject Computer science articles
- WikiProject Cryptography articles