Changes between Version 7 and Version 8 of howto/ShareArchives2

Timestamp:

Aug 4, 2011, 6:47:06 PM (13 years ago)

Author:

fracai

Comment:

Minor cleanup and phrasing

howto/ShareArchives2

@@ -26 +26 @@
 }}}
 
-You will be prompted to enter a passphrase to protect the private key. It is up to you to decide how complex this protection should be. Note that it is possible to store this key in your Keychain.app (using /usr/bin/ssh-add). This has the advantage of passing the key security on to the OS, though it may not be an acceptable option for automating package signing.
+You will be prompted to enter a passphrase to protect the private key. It is up to you to decide how complex this protection should be. Note that it is possible to store this key and passphrase in your Keychain.app (using '''/usr/bin/ssh-add'''). This has the advantage of passing the key security on to the OS, though it may not be an acceptable option for automating package signing.
 
 It is also possible to create a key without a passphrase. If you are not distributing packages outside of a home network, this is likely not a problem. An unprotected private key is generated as below; the command to generate the public key is unchanged.
@@ -143 +143 @@
 [http://localhost:6267]
 
-There is also a simple tutorial for enabling [http://redmine.lighttpd.net/wiki/1/HowToSimpleSSL SSL] support for additional security if it is desired. Be sure to install '''lighttpd''' with the '''+ssl'''.
+There is also a simple tutorial for enabling [http://redmine.lighttpd.net/wiki/1/HowToSimpleSSL SSL] support for additional security if it is desired. Be sure to install '''lighttpd''' with the '''+ssl''' variant.
 
 You'll also want the lighttpd service to run at all times so your client machines are not deprived of access to the port archives. A simple LaunchD task will handle this: