{"node_id": "f3d21241-2f95-11f1-bafc-e86a64d24d78", "revisions": [{"id": "f3d318c1-2f95-11f1-939d-e86a64d24d78", "node_id": "f3d21241-2f95-11f1-bafc-e86a64d24d78", "user_id": "edc3f576-2f95-11f1-900f-e86a64d24d78", "author": "foxhop", "data": "Public and Private SSH Keys\r\n##############################\r\n\r\nI tend to think of:\r\n\r\n* a server host as a \"house\"\r\n* a public key as a \"lock\" on a door of a \"house\"\r\n* a private key as a \"key\" to the \"lock\" on a door of a \"house\"\r\n\r\nIn this way, anyone might have access to the outside of a \"house\".\r\nAnyone could have access to the \"lock\" on a house.\r\nOnly you should have access to the private \"key\".\r\n\r\nHow to create a new public and private ssh keypair\r\n======================================================\r\n\r\nCreate a ssh public/private keypair:\r\n\r\n.. code-block:: bash\r\n\r\n ssh-keygen -t rsa -b 4096   #enter a passphrase when asked\r\n\r\nDocument the passphrase in keypass\r\n\r\nHow to add the public key to a host\r\n====================================\r\n\r\nAppend the contents of .pub key to a remote host's ~/.ssh/authorized_keys.\r\nThe user's *authorized_keys* file may contain none or many keys.\r\n\r\n.. warning::\r\n\r\n The *authorized_keys* file must be mode 400\r\n \r\n The *.ssh* directory must be mode 700\r\n\r\n\r\nHow to add a private key to your workstation\r\n===============================================\r\n\r\nKeep all your private keys in the same directory with the .key extension. \r\nUse the following script to add all private .key files to ssh agent:\r\n\r\n.. code-block:: bash\r\n\r\n for f in *.key; do ssh-add $f; done\r\n\r\nThe SSH agent will prompt for each key's passphrase in turn. \r\nThis must be done after each reboot.\r\n\r\nCould not open a connection to your authentication agent\r\n---------------------------------------------------------------\r\n\r\nYou must have a running ssh-agent and your shell must have access to use it.\r\nIf you get this error message when you attempt to run ssh-add then\r\nfirst run the following command to spawn an ssh-agent for this shell:\r\n\r\n.. code-block:: bash\r\n\r\n eval \"$(ssh-agent)\"\r\n\r\nNow try to run ssh-add again.\r\n\r\nAnother command for debugging:\r\n\r\n.. code-block:: bash\r\n\r\n echo $SSH_AUTH_SOCK\r\n\r\nHow to create a putty ppk\r\n===============================\r\n\r\n#. Create a keypair: `How to create a new public and private ssh keypair`_\r\n#. SCP the keypair from unix host to windows host\r\n#. Download and open puttygen.exe\r\n\r\n   * Click the *Load* button\r\n   * Browse to the private key,\r\n     might need to choose 'All Files(\\*.\\*)' from dropdown\r\n   * enter passphrase, click *OK*\r\n   * Click the *Save private key* bytton\r\n   * Name the new key with .ppk extension, and hit *Save*\r\n\r\n#. Add the .ppk to putty.exe and test\r\n", "source_format": "rst", "revision_number": 5, "created": 1373565694000}, {"id": "f3d31434-2f95-11f1-8ea7-e86a64d24d78", "node_id": "f3d21241-2f95-11f1-bafc-e86a64d24d78", "user_id": "edc3f576-2f95-11f1-900f-e86a64d24d78", "author": "foxhop", "data": "Public and Private SSH Keys\r\n##############################\r\n\r\nI tend to think of:\r\n\r\n* a server host as a \"house\"\r\n* a public key as a \"lock\" on a door of a \"house\"\r\n* a private key as a \"key\" to the \"lock\" on a door of a \"house\"\r\n\r\nIn this way, anyone might have access to the outside of a \"house\".\r\nAnyone could have access to the \"lock\" on a house.\r\nOnly you should have access to the private \"key\".\r\n\r\nHow to create a new public and private ssh keypair\r\n======================================================\r\n\r\nCreate a ssh public/private keypair::\r\n\r\n ssh-keygen -t rsa -b 4096   #enter a passphrase when asked\r\n\r\nDocument the passphrase in keypass\r\n\r\nHow to add the public key to a host\r\n====================================\r\n\r\nAppend the contents of .pub key to a remote host's ~/.ssh/authorized_keys.\r\nThe user's *authorized_keys* file may contain none or many keys.\r\n\r\n.. warning::\r\n\r\n The *authorized_keys* file must be mode 400\r\n \r\n The *.ssh* directory must be mode 700\r\n\r\n\r\nHow to add a private key to your workstation\r\n===============================================\r\n\r\nKeep all your private keys in the same directory with the .key extension. \r\nUse the following script to add all private .key files to ssh agent::\r\n\r\n for f in *.key; do ssh-add $f; done\r\n\r\nThe SSH agent will prompt for each key's passphrase in turn. \r\nThis must be done after each reboot.\r\n\r\nCould not open a connection to your authentication agent\r\n---------------------------------------------------------------\r\n\r\nYou must have a running ssh-agent and your shell must have access to use it.\r\nIf you get this error message when you attempt to run ssh-add then\r\nfirst run the following command to spawn an ssh-agent for this shell:\r\n\r\n.. code-block:: bash\r\n\r\n eval \"$(ssh-agent)\"\r\n\r\nNow try to run ssh-add again.\r\n\r\nAnother command for debugging:\r\n\r\n.. code-block:: bash\r\n\r\n echo $SSH_AUTH_SOCK\r\n\r\nHow to create a putty ppk\r\n===============================\r\n\r\n#. Create a keypair: `How to create a new public and private ssh keypair`_\r\n#. SCP the keypair from unix host to windows host\r\n#. Download and open puttygen.exe\r\n\r\n   * Click the *Load* button\r\n   * Browse to the private key,\r\n     might need to choose 'All Files(\\*.\\*)' from dropdown\r\n   * enter passphrase, click *OK*\r\n   * Click the *Save private key* bytton\r\n   * Name the new key with .ppk extension, and hit *Save*\r\n\r\n#. Add the .ppk to putty.exe and test\r\n", "source_format": "rst", "revision_number": 4, "created": 1373565564000}, {"id": "f3d30f68-2f95-11f1-934d-e86a64d24d78", "node_id": "f3d21241-2f95-11f1-bafc-e86a64d24d78", "user_id": "edc3f576-2f95-11f1-900f-e86a64d24d78", "author": "foxhop", "data": "Public and Private SSH Keys\r\n##############################\r\n\r\nI tend to think of:\r\n\r\n* a server host as a \"house\"\r\n* a public key as a \"lock\" on a door of a \"house\"\r\n* a private key as a \"key\" to the \"lock\" on a door of a \"house\"\r\n\r\nIn this way, anyone might have access to the outside of a \"house\".\r\nAnyone could have access to the \"lock\" on a house.\r\nOnly you should have access to the private \"key\".\r\n\r\nHow to create a new public and private ssh keypair\r\n======================================================\r\n\r\nCreate a ssh public/private keypair::\r\n\r\n ssh-keygen -t rsa -b 4096   #enter a passphrase when asked\r\n\r\nDocument the passphrase in keypass\r\n\r\nHow to add the public key to a host\r\n====================================\r\n\r\nAppend the contents of .pub key to a remote host's ~/.ssh/authorized_keys.\r\nThe user's *authorized_keys* file may contain none or many keys.\r\n\r\nPermissions:\r\n *authorized_keys*: \r\n   file must be mode 400\r\n *.ssh*:\r\n  directory must be mode 700\r\n\r\n\r\nHow to add a private key to your workstation\r\n===============================================\r\n\r\nKeep all your private keys in the same directory with the .key extension. \r\nUse the following script to add all private .key files to ssh agent::\r\n\r\n for f in *.key; do ssh-add $f; done\r\n\r\nThe SSH agent will prompt for each key's passphrase in turn. \r\nThis must be done after each reboot.\r\n\r\nHow to create a putty ppk\r\n===============================\r\n\r\n#. Create a keypair: `How to create a new public and private ssh keypair`_\r\n#. SCP the keypair from unix host to windows host\r\n#. Download and open puttygen.exe\r\n\r\n   * Click the *Load* button\r\n   * Browse to the private key,\r\n     might need to choose 'All Files(\\*.\\*)' from dropdown\r\n   * enter passphrase, click *OK*\r\n   * Click the *Save private key* bytton\r\n   * Name the new key with .ppk extension, and hit *Save*\r\n\r\n#. Add the .ppk to putty.exe and test\r\n", "source_format": "rst", "revision_number": 3, "created": 1373472104000}, {"id": "f3d309f6-2f95-11f1-8c03-e86a64d24d78", "node_id": "f3d21241-2f95-11f1-bafc-e86a64d24d78", "user_id": "edc3f576-2f95-11f1-900f-e86a64d24d78", "author": "foxhop", "data": "Public and Private SSH Keys\r\n##############################\r\n\r\nI tend to think of:\r\n\r\n* a server host as a \"house\"\r\n* a public key as a \"lock\" on a door of a \"house\"\r\n* a private key as a \"key\" to the \"lock\" on a door of a \"house\"\r\n\r\nIn this way, anyone might have access to the outside of a \"house\".\r\nAnyone could have access to the \"lock\" on a house.\r\nOnly you should have access to the private \"key\".\r\n\r\nHow to create a new public and private ssh keypair\r\n======================================================\r\n\r\nCreate a ssh public/private keypair::\r\n\r\n ssh-keygen -t rsa -b 4096   #enter a passphrase when asked\r\n\r\nDocument the passphrase in keypass\r\n\r\nHow to add the public key to a host\r\n====================================\r\n\r\nAppend the contents of .pub key to a remote host's ~/.ssh/authorized_keys.\r\nThe user's *authorized_keys* file may contain none or many keys.\r\n\r\nPermissions:\r\n *authorized_keys*: \r\n   file must be mode 400\r\n *.ssh*:\r\n  directory must be mode 700\r\n\r\n\r\nHow to add a private key to your workstation\r\n===============================================\r\n\r\nKeep all your private keys in the same directory with the .key extension. \r\nUse the following script to add all private .key files to ssh agent::\r\n\r\n for f in *.key; do ssh-add $f; done\r\n\r\nThe SSH agent will prompt for each key's passphrase in turn. \r\nThis must be done after each reboot.\r\n\r\nHow to create a putty ppk\r\n===============================\r\n\r\n#. Create a keypair: `How to create a new public and private ssh keypair`_\r\n#. SCP the keypair from unix host to windows host\r\n#. Download and open puttygen.exe\r\n\r\n   * Click the *Load* button\r\n   * Browse to the private key,\r\n     might need to choose 'All Files(\\*.\\*)' from dropdown\r\n   * enter passphrase, click *OK*\r\n   * Click the *Save private key* bytton\r\n   * Name the new key with .ppk extension, and hit *Save*\r\n\r\n#. Add the .ppk to putty.exe and test\r\n", "source_format": "rst", "revision_number": 2, "created": 1373472103000}, {"id": "f3d30192-2f95-11f1-8303-e86a64d24d78", "node_id": "f3d21241-2f95-11f1-bafc-e86a64d24d78", "user_id": "edc3f576-2f95-11f1-900f-e86a64d24d78", "author": "foxhop", "data": "Public and Private SSH Keys\r\n##############################\r\n\r\nI tend to think of:\r\n\r\n* a server host as a \"house\"\r\n* a public key as a \"lock\" on a door of a \"house\"\r\n* a private key as a \"key\" to the \"lock\" on a door of a \"house\"\r\n\r\nIn this way, anyone might have access to the outside of a \"house\".\r\nAnyone could have access to the \"lock\" on a house.\r\nOnly you should have access to the private \"key\".\r\n\r\nHow to create a new public and private ssh keypair\r\n======================================================\r\n\r\nCreate a ssh public/private keypair::\r\n\r\n ssh-keygen -t rsa -b 4096   #enter a passphrase when asked\r\n\r\nDocument the passphrase in keypass\r\n\r\nHow to add the public key to a host\r\n====================================\r\n\r\nAppend the contents of .pub key to a remote host's ~/.ssh/authorized_keys.\r\nThe user's *authorized_keys* file may contain none or many keys.\r\n\r\n.. warning::\r\n\r\n The *authorized_keys* file must be mode 400\r\n \r\n The *.ssh* directory must be mode 700\r\n\r\n\r\nHow to add a private key to your workstation\r\n===============================================\r\n\r\nKeep all your private keys in the same directory with the .key extension. \r\nUse the following script to add all private .key files to ssh agent::\r\n\r\n for f in *.key; do ssh-add $f; done\r\n\r\nThe SSH agent will prompt for each key's passphrase in turn. \r\nThis must be done after each reboot.\r\n\r\nHow to create a putty ppk\r\n===============================\r\n\r\n#. Create a keypair: `How to create a new public and private ssh keypair`_\r\n#. SCP the keypair from unix host to windows host\r\n#. Download and open puttygen.exe\r\n\r\n   * Click the *Load* button\r\n   * Browse to the private key,\r\n     might need to choose 'All Files(\\*.\\*)' from dropdown\r\n   * enter passphrase, click *OK*\r\n   * Click the *Save private key* bytton\r\n   * Name the new key with .ppk extension, and hit *Save*\r\n\r\n#. Add the .ppk to putty.exe and test\r\n", "source_format": "rst", "revision_number": 1, "created": 1373471878000}], "count": 5}