Mercurial > hg > orthanc-book
comparison Sphinx/source/developers/repositories.rst @ 344:9f82ecc5a422
fingerprint
| author | Sebastien Jodogne <s.jodogne@gmail.com> |
|---|---|
| date | Fri, 27 Mar 2020 07:26:16 +0100 |
| parents | ab1ec4009541 |
| children | 84e3a2612c36 |
comparison
equal
deleted
inserted
replaced
| 343:fff45618262d | 344:9f82ecc5a422 |
|---|---|
| 75 You can then use separate tools such as `TortoiseHg | 75 You can then use separate tools such as `TortoiseHg |
| 76 <https://en.wikipedia.org/wiki/TortoiseHg>`__ to browse the code with | 76 <https://en.wikipedia.org/wiki/TortoiseHg>`__ to browse the code with |
| 77 richer features than the Web interface. | 77 richer features than the Web interface. |
| 78 | 78 |
| 79 | 79 |
| 80 Note for Microsoft Windows | |
| 81 .......................... | |
| 82 | |
| 83 .. highlight:: text | |
| 84 | |
| 85 On Microsoft Windows, while cloning the repository, you might face an | |
| 86 error similar to:: | |
| 87 | |
| 88 abort: error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661) | |
| 89 | |
| 90 In such a case, you must explicitly add the cryptographic fingerprint | |
| 91 of our code server. To this end, edit the `configuration file | |
| 92 <https://www.mercurial-scm.org/doc/hgrc.5.html#files>`__ of Mercurial | |
| 93 (by default, ``%USERPROFILE%\Mercurial.ini``), and add the following | |
| 94 lines:: | |
| 95 | |
| 96 [hostsecurity] | |
| 97 hg.orthanc-server.com:fingerprints=sha256:A1:75:3A:3F:20:74:C1:A6:C3:16:DD:EC:4C:67:74:C4:70:BE:E8:35:0A:0A:C7:2E:36:1F:49:8B:E2:60:61:73 | |
| 98 | |
| 99 .. highlight:: bash | |
| 100 | |
| 101 For reference, here is the command that was used to generate this | |
| 102 fingerprint (`click here for more information | |
| 103 <https://stackoverflow.com/a/56579497/881731>`__):: | |
| 104 | |
| 105 $ openssl s_client -connect hg.orthanc-server.com:443 < /dev/null 2>/dev/null | openssl x509 -fingerprint -sha256 -noout -in /dev/stdin | |
| 106 | |
| 107 | |
| 80 Write access | 108 Write access |
| 81 ^^^^^^^^^^^^ | 109 ^^^^^^^^^^^^ |
| 82 | 110 |
| 83 Only the core developers of Orthanc have direct write access to the | 111 Only the core developers of Orthanc have direct write access to the |
| 84 Orthanc repositories (through SSH). Core developers can clone a | 112 Orthanc repositories (through SSH). Core developers can clone a |