Fix up NSS links or delete #3290
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hamishwillee
commented
Mar 19, 2021
| @@ -43,7 +43,7 @@ <h3 id="What_platforms_and_development_environments_are_supported.3F">What platf | |||
|
|
|||
| <h3 id="What_cryptography_standards_are_supported.3F">What cryptography standards are supported?</h3> | |||
|
|
|||
| <p>NSS supports <a href="/en-US/docs/Glossary/SSL">SSL v2 and v3</a>, <a href="/en-US/docs/Glossary/TLS">TLS</a>, <a href="/en-US/docs/Glossary/PKCS_.235">PKCS #5</a>, <a href="/en-US/docs/Glossary/PKCS_.237">PKCS #7</a>, <a href="/en-US/docs/Glossary/PKCS_.2311">PKCS #11</a>, <a href="/en-US/docs/Glossary/PKCS_.2312">PKCS #12</a>, <a href="/en-US/Glossary/en-US/docs/Glossary/S.2FMIME">S/MIME</a>, and <a href="/en-US/docs/Mozilla/Security/x509_Certificates">X.509 v3</a> certificates. For complete details, see <a class="external" href="http://www-archive.mozilla.org/projects/security/pki/nss/nss-3.11/nss-3.11-algorithms.html">Encryption Technologies Available in NSS 3.11</a></p> | |||
| <p>NSS supports <a href="/en-US/docs/Glossary/SSL">SSL v2 and v3</a>, <a href="/en-US/docs/Glossary/TLS">TLS</a>, <a href="https://tools.ietf.org/html/rfc8018">PKCS #5</a>, <a href="https://tools.ietf.org/html/rfc2315">PKCS #7</a>, <a href="https://www.oasis-open.org/committees/documents.php?wg_abbrev=pkcs11&show_descriptions=yes">PKCS #11</a>, <a href="https://tools.ietf.org/html/rfc7292">PKCS #12</a>, <a href="https://en.wikipedia.org/wiki/S/MIME">S/MIME</a>, and <a href="/en-US/docs/Mozilla/Security/x509_Certificates">X.509 v3</a> certificates. For complete details, see <a class="external" href="http://www-archive.mozilla.org/projects/security/pki/nss/nss-3.11/nss-3.11-algorithms.html">Encryption Technologies Available in NSS 3.11</a></p> | |||
There was a problem hiding this comment.
Links to RFCS where they can be found. Changed S/MIME to wikipedia - not worth doing a "proper job" of a normal glossary entry.
|
@chrisdavidmills This was a while ago now. Perhaps if they have already taken their snapshot we should just close? |
|
Crikey, I don't recall ever seeing this one. Sorry @hamishwillee . Yeah, we should just close this. The team have already been sent a snapshot of the docs. |
|
Yoiks. Let us never speak of this again :-0 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Continues: #2669
Fix up remaining NSS broken links. In some cases by finding new external links, in others by deleting the links.
Also created VERY basic stub docs for the fundamental types. They are populated with the minimal info from the header, and link to the header. I have not tried to do this properly - these are just to fix links and give people a starting point (IMO if they are useful the NSS team should expand them, and if not, they should delete them and remove the inter-links)