SSH - Revision history

Brodriguez: Update to elaborate on the IdentitiesOnly value in the ssh config

2024-01-31T07:28:21Z

Update to elaborate on the IdentitiesOnly value in the ssh config

@@ Line 81: / Line 81: @@
 Possible options are as follows:
 * '''Host''' - Required. Can be any arbitrary value. This is what is typed locally to call this specific SSH configuration.
-** Generally, this is either the same as '''HostName''' or an abbreviation of such.
+** Generally, this is either the same as '''HostName''' or an abbreviation of such. But in reality, you can think of it as an alias.
 * '''HostName''' - Required. This is the actual address to connect to.
 ** Ex: An IP address if connecting to a production server. Or "github.com" if connecting to GitHub. Etc.
@@ Line 88: / Line 88: @@
 ** If not provided, then attempts to use the name of the local user invoking the ssh call.
 * '''PreferredAuthentications''' - Specifies the order which the client should attempt to authenticate with. Most common options are '''publickey''' or '''password'''.
 * '''IdentityFile''' - If applicable, the file to attempt to authenticate through.
 ** Ex: In the below examples, we use a {{ ic |github_rsa}} key and a {{ ic |bitbucket_ed2}} key, respectively.
@@ Line 113: / Line 114: @@
       IdentitiesOnly yes
       IdentityFile /home/my_user/.ssh/bitbucket_ed2

Brodriguez: Add new config line to example

2023-03-31T05:59:10Z

Add new config line to example

← Older revision		Revision as of 05:59, 31 March 2023
Line 101:		Line 101:
	Port 22		Port 22
	PreferredAuthentications publickey		PreferredAuthentications publickey
			IdentitiesOnly yes
	IdentityFile /home/my_user/.ssh/github_rsa		IdentityFile /home/my_user/.ssh/github_rsa

Line 110:		Line 111:
	Port 22		Port 22
	PreferredAuthentications publickey		PreferredAuthentications publickey
			IdentitiesOnly yes
	IdentityFile /home/my_user/.ssh/bitbucket_ed2		IdentityFile /home/my_user/.ssh/bitbucket_ed2

Brodriguez: Add note

2023-03-31T05:07:46Z

Add note

← Older revision		Revision as of 05:07, 31 March 2023
Line 138:		Line 138:

	First, you'll need to be able to make SSH connections using passwords. If not already enabled on the server, then enable it with the following:		First, you'll need to be able to make SSH connections using passwords. If not already enabled on the server, then enable it with the following:
			* Note that this requires enabling at least one user that can log in with a standard password. AWS EC2, for example, does not create such a user by default.
	* Edit the file {{ ic \|/etc/ssh/sshd_config}}.		* Edit the file {{ ic \|/etc/ssh/sshd_config}}.
	* Update the line {{ ic \|PasswordAuthentication}} to '''yes'''.		* Update the line {{ ic \|PasswordAuthentication}} to '''yes'''.

Brodriguez: Clarify wording

2022-05-21T22:57:40Z

Clarify wording

← Older revision		Revision as of 22:57, 21 May 2022
Line 89:		Line 89:
	* '''PreferredAuthentications''' - Specifies the order which the client should attempt to authenticate with. Most common options are '''publickey''' or '''password'''.		* '''PreferredAuthentications''' - Specifies the order which the client should attempt to authenticate with. Most common options are '''publickey''' or '''password'''.
	* '''IdentityFile''' - If applicable, the file to attempt to authenticate through.		* '''IdentityFile''' - If applicable, the file to attempt to authenticate through.
	** Ex: ~~If connecting to Hybels production servers, then~~ the ~~AWS .pub key. Or if connecting to BitBucket~~, ~~then the rsa/ed2~~ key ~~(generated via steps at [[SSH#Generating SSH Keys~~ \| ~~Generating SSH Keys]])~~.		** Ex: In the below examples, we use a {{ ic \|github_rsa}} key and a {{ ic \|bitbucket_ed2}} key, respectively.

Brodriguez: Add config file section

2021-12-19T23:51:14Z

Add config file section

@@ Line 3: / Line 3: @@
 Most common uses are to securely access repositories in sites like Github, GitLab, or Bitbucket. Or to gain access to a remote machine's terminal (such as if you're the admin of said machine).
-Generally speaking, SSH is considered similar to authenticating with a Username + Password, but considered generally a bit more secure, and thus preferred.
+SSH authentication can be done through either a standard "username + password" combination, or through SSH Keys. Note that SSH Keys are generally considered more secure, as it's a physical code that the user needs access to.
 == SSH Keys ==
@@ Line 51: / Line 52: @@
 ** For example, if making a RSA key for GitHub, it might be good to change the name to something like {{ ic |github_rsa}}.
 ** This allows you to have multiple keys, where each key corresponds to a different service or use case.

Brodriguez: Add sections about SSH Keys themselves

2020-10-05T06:46:20Z

Add sections about SSH Keys themselves

@@ Line 1: / Line 1: @@
-== Setting up Password-less Server Credentials ==
+SSH stands for "Secure Shell". It's used to securely connect to remote machines.
-First, you'll need to be able to make ssh connections with passwords. If not already enabled on the server, then enable it with the following:
+Most common uses are to securely access repositories in sites like Github, GitLab, or Bitbucket. Or to gain access to a remote machine's terminal (such as if you're the admin of said machine).
-Next, pass your public key to the server with the command:<br>
+Generally speaking, SSH is considered similar to authenticating with a Username + Password, but considered generally a bit more secure, and thus preferred.
-<code>ssh-copy-id -i <public_key_to_pass> <server_address></code>
 Test that it works by connecting to the server with ssh. It should connect without asking for a password.
 Finally, disable ssh connections with passwords to make the server more secure:
-* Edit the file <code>/etc/ssh/sshd_config</code>
+* Edit the file {{ ic |/etc/ssh/sshd_config}}.
-* Update the line <code>PasswordAuthentication</code> to <code>no</code>
+* Update the line {{ ic |PasswordAuthentication}} to '''no'''.
-* Restart the service with <code>sudo service ssh restart</code>
+* Restart the service with {{ ic |sudo service ssh restart}}
 == SSH not Prompting for Password ==
 https://askubuntu.com/a/419562

Brodriguez: Add temporary reference link

2020-10-04T08:07:20Z

Add temporary reference link

← Older revision		Revision as of 08:07, 4 October 2020
Line 16:		Line 16:
	* Update the line <code>PasswordAuthentication</code> to <code>no</code>		* Update the line <code>PasswordAuthentication</code> to <code>no</code>
	* Restart the service with <code>sudo service ssh restart</code>		* Restart the service with <code>sudo service ssh restart</code>


			== SSH not Prompting for Password ==
			https://askubuntu.com/a/419562

Brodriguez: Create page

2020-03-14T07:02:29Z

Create page

New page

== Setting up Password-less Server Credentials ==
This is done by passing a ssh public key to the server you wish to connect to.

First, you'll need to be able to make ssh connections with passwords. If not already enabled on the server, then enable it with the following:
* Edit the file <code>/etc/ssh/sshd_config</code>
* Update the line <code>PasswordAuthentication</code> to <code>yes</code>
* Restart the service with <code>sudo service ssh restart</code>

Next, pass your public key to the server with the command:<br>
<code>ssh-copy-id -i <public_key_to_pass> <server_address></code>

Test that it works by connecting to the server with ssh. It should connect without asking for a password.

Finally, disable ssh connections with passwords to make the server more secure:
* Edit the file <code>/etc/ssh/sshd_config</code>
* Update the line <code>PasswordAuthentication</code> to <code>no</code>
* Restart the service with <code>sudo service ssh restart</code>