| At line 1 changed one line |
| Here is an example on how to make a certificate request for an authority. |
| !__Starting from the beginning :__ |
| \\ |
| \\ |
| ![Use Portecle's GUI to make a Keystore|Portecle] <---click here |
| \\ |
| \\ |
| \\ |
| \\ |
| \\ |
| ---- |
| !__Renewing a certificate :__ |
| \\ |
| \\ |
| ![Use Portecle's GUI to make a Keystore|Portecle] <---click here |
| \\ |
| \\ |
| \\ |
| \\ |
| \\ |
| ---- |
| Alternate methods for bringing in a cert from another server: |
| ---- |
| *Apache - If you already have a certificate for Apache, follow these [instructions|openssl_key_convert] for converting it. |
| ---- |
| *IIS - If you already have a certificate in IIS, you can export that certificate as a .PFX file and use that certificate directly in CrushFTP. [http://www.digicert.com/ssl-support/pfx-import-export-iis.htm] |
| ---- |
| *OS X Server - Export the private key using keychain. You will need to run keychain using root access to be able to export the certificate. |
| {{{ |
| sudo "/Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain Access" |
| }}} |
| Then use Portecle to add in the missing certificate that go along with the chain to trust the private key's signature. For GoDaddy, that means downloading the valicert, cross and intermediate cert. |
| ---- |
| At line 34 added 6 lines |
| These below instructions are complicated and shouldn't be used unless you just can't stand using Portecle for some strange reason. |
|
| *Java - When purchasing a certificate from a cert authority, be sure to choose 'Tomcat' for the format. |
|
|
| *PART 1 (Command Line) |
| At line 4 changed 4 lines |
| |
| I purchased a cheap chained certificate from godaddy. I chose the "Tomcat" type of certificate as CrushFTP works the same way as tomcat for certificates. I substituted "crushftp" instead of "tomcat" though. It really doesn't matter however. |
| |
| *PART 1 |
|
| At line 11 changed one line |
| keytool -genkey -keysize 2048 -alias crushftp -keyalg RSA -keystore crushftp.keystore |
| keytool -genkey -keysize 2048 -alias crushftp -keyalg RSA -keystore crushftp.jks |
| At line 43 changed one line |
|
| ---- |
| At line 49 changed one line |
| keytool -certreq -keyalg RSA -alias crushftp -file crushftp.csr -keystore crushftp.keystore |
| keytool -certreq -keyalg RSA -alias crushftp -file crushftp.csr -keystore crushftp.jks |
| At line 56 changed 3 lines |
|
| *WARNING! Keep your "crushftp.keystore" file! (Maybe even make a backup of it just in case you make a mistake in step 3.) You must have this original keystore file to apply the signed certificate GoDaddy gives back. |
|
| ---- |
| At line 93 added 2 lines |
| WARNING! Keep your "crushftp.jks" file! (Make a backup of it just in case you make a mistake in step 3.) You must have this original keystore file to apply the signed certificate GoDaddy gives back. |
|
| At line 71 removed one line |
|
| At line 73 changed one line |
| [https://certificates.starfieldtech.com/Repository.go] |
| [https://certs.godaddy.com/anonymous/repository.seam] |
| At line 83 changed one line |
| keytool -import -alias root -keystore crushftp.keystore -trustcacerts -file valicert_class2_root.crt |
| keytool -import -alias root -keystore crushftp.jks -trustcacerts -file valicert_class2_root.crt |
| At line 85 changed 3 lines |
| Certificate was added to keystore<br/> |
| keytool -import -alias cross -keystore crushftp.keystore -trustcacerts -file gd_cross_intermediate.crt |
| keytool -import -alias intermed -keystore crushftp.keystore -trustcacerts -file gd_intermediate.crt ] |
| Certificate was added to keystore |
| keytool -import -alias cross -keystore crushftp.jks -trustcacerts -file gd_cross_intermediate.crt |
| Trust this certificate? [no]: yes |
| Certificate was added to keystore |
| keytool -import -alias intermed -keystore crushftp.jks -trustcacerts -file gd_intermediate.crt ] |
| Trust this certificate? [no]: yes |
| Certificate was added to keystore |
| At line 91 changed one line |
| keytool -import -alias crushftp -keyalg RSA -keystore crushftp.keystore -trustcacerts -file www.crushftp.com.crt |
| keytool -import -alias crushftp -keyalg RSA -keystore crushftp.jks -trustcacerts -file www.crushftp.com.crt |
| At line 93 changed one line |
| (Substitute your certificates name instead of "www.crushftp.com.crt".) |
| (Substitute your certificate's name instead of "www.crushftp.com.crt".) |
| ---- |
| Now the resulting crushftp.keystore is a complete signed certificate chain. Place this file in the CrushFTP folder. Then go to the preferences of CrushFTP. Choose encryption on the left, then SSL. Browse and locate your crushftp.keystore file. |
| At line 95 removed 2 lines |
| Now the resulting crushftp.keystore is a complete signed certificate chain. Place this file where ever you like, but that might as well be in the CrushFTP folder. Then go to the preferences of CrushFTP. Choose encryption on the left, then SSL. Browse and locate your crushftp.keystore file. |
|
| At line 100 removed 5 lines |
|
| If you already have a certificate for Apache, you may be able to convert it to a Java keystore and use it with CrushFTP. I provide this information untested, but it in theory looks like it would work. |
|
| [http://www.ks.uiuc.edu/Research/biocore/localServer/install/installCert.shtml] |
|
#