aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Wemm <peter@FreeBSD.org>2015-08-27 01:04:03 +0000
committerPeter Wemm <peter@FreeBSD.org>2015-08-27 01:04:03 +0000
commita992a6afe16399f6eea877fb88ec64f34ba5efca (patch)
tree52c2ea280103031b30ea089b89998d087552e618
parent3b0d5fb7f22819e14de62184725224140744e235 (diff)
downloaddoc-a992a6afe16399f6eea877fb88ec64f34ba5efca.tar.gz
doc-a992a6afe16399f6eea877fb88ec64f34ba5efca.zip
Re-add the legacy fingerprints with warnings that they are deprecated.
Notes
Notes: svn path=/head/; revision=47312
-rw-r--r--en_US.ISO8859-1/books/handbook/mirrors/chapter.xml47
1 files changed, 45 insertions, 2 deletions
diff --git a/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml b/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml
index 0db30058ab..81affc4182 100644
--- a/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml
@@ -651,8 +651,9 @@ Comment out for now until these can be verified.
official SSL certificate that will be recognized by
<application>Subversion</application> if the <filename
role="package">security/ca_root_nss</filename> port is
- installed. The legacy self-signed certificates are still
- available, but are now considered deprecated.</para>
+ installed. The legacy self-signed certificates and server
+ names are still available but are deprecated and no longer
+ supported.</para>
</note>
<para>For those without the <filename
@@ -694,6 +695,48 @@ Comment out for now until these can be verified.
or other problems, <literal>svn</literal> is the next choice,
with slightly faster transfers. When neither can be used, use
<literal>http</literal>.</para>
+
+ <para>For those still using deprecated server names, the SHA1
+ and SHA256 fingerprints will be one of:</para>
+
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colwidth="1*"/>
+ <colspec colwidth="1*"/>
+ <thead>
+ <row>
+ <entry>Hash</entry>
+ <entry>Fingerprint</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry>Legacy-SHA1</entry>
+ <entry><literal>1C:BD:85:95:11:9F:EB:75:A5:4B:C8:A3:FE:08:E4:02:73:06:1E:61</literal></entry>
+ </row>
+
+ <row>
+ <entry>Legacy-SHA1</entry>
+ <entry><literal>F6:44:AA:B9:03:89:0E:3E:8C:4D:4D:14:F0:27:E6:C7:C1:8B:17:C5</literal></entry>
+ </row>
+
+ <row>
+ <entry>Legacy-SHA256</entry>
+ <entry><literal>47:35:A9:09:A3:AB:FA:20:33:36:43:C5:1A:D6:E6:FB:EB:C0:C0:83:37:D4:46:9C:A0:AB:89:7F:C2:9C:4C:A3</literal></entry>
+ </row>
+
+ <row>
+ <entry>Legacy-SHA256</entry>
+ <entry><literal>48:3C:84:DB:7C:27:1B:FA:D5:0B:A0:D7:E0:4C:79:AA:A3:8E:A3:FA:84:E6:32:34:7D:EB:30:E6:11:01:CF:BE</literal></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ <para>If you are seeing one of these legacy certificate
+ fingerprints then it is likely you are using a deprecated
+ server name.</para>
</sect2>
<sect2>