選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。

instructions.tmpl 5.1KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123
  1. ********************************************************************************
  2. Gitblit SSL Client Certificate for $serverHostname
  3. ********************************************************************************
  4. Hello $userDisplayname,
  5. Your private key, public certificate, and the Gitblit Certificate Authority
  6. certificate for $serverHostname are stored in $username.p12, a PKCS#12 certificate
  7. store[1], and also in $username.pem, a PEM certificate store.
  8. Both of these certificate stores are password-protected.
  9. Password Hint: $storePasswordHint
  10. Git (All) Installation Instructions
  11. =============================================
  12. The provided PEM file can be directly used by your git client.
  13. git config [--global] http.sslCert path/to/$username.pem
  14. The supplied PEM file is password-protected and you may be prompted for your
  15. password multiple times during an exchange with Gitblit. If you desire a
  16. password-less git client workflow then you will need to decrypt and export your
  17. private key with OpenSSL[2] and then update your git config to use that key.
  18. openssl rsa -in path/to/$username.pem -out path/to/$username.key
  19. git config [--global] http.sslKey path/to/$username.key
  20. Obviously, you should protect access to any decrypted private key.
  21. NOTE:
  22. Some older git clients may have trouble using the PEM file without explicitly
  23. extracting the private key. This has been observed, for example, on Ubuntu 12.04
  24. with git 1.7.9.5.
  25. Firefox (All) Installation Instructions
  26. =============================================
  27. Firefox maintains it's own certificate store which is separate from the operating
  28. system.
  29. 1. Navigate to Options->Advanced->Encryption
  30. 2. Click "View Certificates"
  31. 3. Switch to the "Your Certificates" tab
  32. 4. Click "Import..."
  33. 5. Navigate your filesystem and select $username.p12
  34. 6. At the password prompt enter the certificate store password
  35. You have now imported your private key, public certificate, and the CA certificate
  36. but now we must manually set the trust settings of the CA certificate.
  37. 7. Switch to the "Authorities" tab
  38. 8. Scroll down and find "Gitblit-> Gitblit Certificate Authority"
  39. 9. Select it and click "Edit Trust..."
  40. 10. Check "This certificate can identify websites" and click OK.
  41. Chrome/IE (Windows) Installation Instructions
  42. =============================================
  43. On Windows, Chrome and IE share their certificate store so configuring one will
  44. automatically apply for both.
  45. IE
  46. ------------------------------------
  47. 1. Navigate to Internet Options->Content
  48. 2. Click the "Certificates" button
  49. Chrome
  50. ------------------------------------
  51. 1. Navigate to Settings->Show Advanced Settings->HTTP/SSL
  52. 2. Click the "Manage Certificates..." button
  53. Both (Windows)
  54. ------------------------------------
  55. 3. Switch to the "Personal" tab
  56. 4. Click the "Import..." button
  57. 5. Follow the Import Wizard instructions.
  58. You will need to change the selected file filter when navigating to $username.p12
  59. 6. At the password prompt enter the certificate store password
  60. 7. Because both your personal certificate and the CA certifcate are stored in
  61. $username.p12, you must choose "Automatically select the certificate store based on the type of certificate".
  62. If you choose the default you will not install the CA certificate.
  63. Chrome (Linux) Installation Instructions
  64. =============================================
  65. On Linux, Chrome maintains it's own certificate store.
  66. 1. Navigate to Settings->Show Advanced Settings->HTTP/SSL
  67. 2. Click the "Manage Certificates..." button
  68. 3. Navigate your filesystem and select $username.p12
  69. 4. At the password prompt enter the certificate store password
  70. You have now imported your private key, public certificate, and the CA certificate
  71. but now we must manually set the trust settings of the CA certificate.
  72. 5. Switch to the "Authorities" tab
  73. 6. Scroll down and find "Gitblit-> Gitblit Certificate Authority"
  74. 7. Select it and click "Edit Trust..."
  75. 8. Check "This certificate can identify websites" and click OK.
  76. Chrome/Safari (Mac OS X) Installation Instructions
  77. =============================================
  78. On Mac OS X, Chrome and Safari both use Keychain Access to store certificates
  79. so configuring one will automatically apply for both.
  80. 1. Double-click $username.pem
  81. 2. At the password prompt enter the certificate store password
  82. You have now imported your private key, public certificate, and the CA certificate
  83. but now we must manually set the trust settings of the CA certificate.
  84. 3. Find the Gitblit Certificate Authority certificate, it should have a red
  85. indicator meaning untrusted, and double-click it.
  86. 4. Open the "Trust" disclosure triangle and change "When using this certificate"
  87. to "Always Trust".
  88. 5. Close the certificate view and enter your system password to save the changes
  89. to your keychain.
  90. [1] PKCS#12 is one of the standard container formats for sharing private keys and
  91. public certificates.
  92. [2] http://www.openssl.org