Providing geek access to our servers - Revision history

Jacky at 08:55, 7 December 2019

2019-12-07T08:55:21Z

← Older revision		Revision as of 08:55, 7 December 2019
Line 49:		Line 49:
	<br> Back to [[Geeks Team Remit]]		<br> Back to [[Geeks Team Remit]]

	[[Category:~~Tech_Group_Stuff~~]]		[[Category:Geeks Team]]

Jacky at 18:05, 27 March 2017

2017-03-27T18:05:09Z

← Older revision		Revision as of 18:05, 27 March 2017
Line 1:		Line 1:
	These are instructions for providing a new geek with full access to the [[Freegle servers]].		These are instructions for providing a new geek with full access to the Freegle servers.

	== Software ==		== Software ==

Jacky: /* Set SSH Key */

2015-07-11T19:46:51Z

Set SSH Key

← Older revision		Revision as of 19:46, 11 July 2015
Line 47:		Line 47:
	You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.		You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.

	<br> Back to [[~~Freegle~~ Geeks]]		<br> Back to [[Geeks Team Remit]]

	[[Category:Tech_Group_Stuff]]		[[Category:Tech_Group_Stuff]]

Chriscant: Add link to Freegle servers

2012-06-27T12:56:36Z

Add link to Freegle servers

← Older revision		Revision as of 12:56, 27 June 2012
Line 1:		Line 1:
	These are instructions for providing a new geek with full access to ~~our server(s)~~.		These are instructions for providing a new geek with full access to the [[Freegle servers]].

	== Software ==		== Software ==
Line 8:		Line 8:
	*WinSCP: [http://winscp.net/eng/index.php http://winscp.net/eng/index.php] - provides file access		*WinSCP: [http://winscp.net/eng/index.php http://winscp.net/eng/index.php] - provides file access

	SmartFTP (paid) or FileZilla (free) are good FTP clients.		SmartFTP (paid) or FileZilla (free) are good FTP clients.

	== Create access key ==		== Create access key ==
Line 45:		Line 45:
	*Note that in WinSCP you cannot "sudo su" to root so some files will not be accessible.		*Note that in WinSCP you cannot "sudo su" to root so some files will not be accessible.

	You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.		You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.

	<br> Back to [[Freegle Geeks]]		<br> Back to [[Freegle Geeks]]

	[[Category:Tech_Group_Stuff]]		[[Category:Tech_Group_Stuff]]

Edwh: /* Software */

2012-06-05T21:05:51Z

Software

← Older revision		Revision as of 21:05, 5 June 2012
Line 7:		Line 7:
	*Putty: [http://www.chiark.greenend.org.uk/~sgtatham/putty/ http://www.chiark.greenend.org.uk/~sgtatham/putty/] - provides shell prompt		*Putty: [http://www.chiark.greenend.org.uk/~sgtatham/putty/ http://www.chiark.greenend.org.uk/~sgtatham/putty/] - provides shell prompt
	*WinSCP: [http://winscp.net/eng/index.php http://winscp.net/eng/index.php] - provides file access		*WinSCP: [http://winscp.net/eng/index.php http://winscp.net/eng/index.php] - provides file access

			SmartFTP (paid) or FileZilla (free) are good FTP clients.

	== Create access key ==		== Create access key ==

Chriscant at 12:32, 30 October 2011

2011-10-30T12:32:53Z

← Older revision		Revision as of 12:32, 30 October 2011
Line 38:		Line 38:
	*In that directory create file authorized_keys		*In that directory create file authorized_keys
	**in that file you put the public half of any SSH keys you want to use for password-less logging in, ie usually starting with ssh-rsa and ending with rsa-key-20100411		**in that file you put the public half of any SSH keys you want to use for password-less logging in, ie usually starting with ssh-rsa and ending with rsa-key-20100411
	*You'll want to "chmod 700 .ssh" and "chmod 600 authorized_keys" (read/write only by user) to keep SSH happier.		*You'll want to "chmod 700 .ssh" and "chmod 600 authorized_keys" (read/write only by user) to keep SSH happier.
	*Set up putty and WinSCP to use SSH to login.  In both cases refer to your local private key file.		*Set up putty and WinSCP to use SSH to login.  In both cases refer to your local private key file.
	*You should now normally access the server using the SSH methods.		*You should now normally access the server using the SSH methods.
	*Note that in WinSCP you cannot "sudo su" to root so some files will not be accessible.		*Note that in WinSCP you cannot "sudo su" to root so some files will not be accessible.

	You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.		You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.

			<br> Back to [[Freegle Geeks]]

			[[Category:Tech_Group_Stuff]]

Chriscant: Add these instructions - these are standard instructions and are not a security breach

2011-10-30T12:29:06Z

Add these instructions - these are standard instructions and are not a security breach

← Older revision		Revision as of 12:29, 30 October 2011
Line 1:		Line 1:
	These are instructions for providing a new geek with full access to our server(s).		These are instructions for providing a new geek with full access to our server(s).

	== Software ==		== Software ==

	On access from Windows, try these:		On access from Windows, try these:

	*Putty: [http://www.chiark.greenend.org.uk/~sgtatham/putty/ http://www.chiark.greenend.org.uk/~sgtatham/putty/] - provides shell prompt		*Putty: [http://www.chiark.greenend.org.uk/~sgtatham/putty/ http://www.chiark.greenend.org.uk/~sgtatham/putty/] - provides shell prompt
	*WinSCP: [http://winscp.net/eng/index.php http://winscp.net/eng/index.php] - provides file access		*WinSCP: [http://winscp.net/eng/index.php http://winscp.net/eng/index.php] - provides file access

	== Create access key ==		== Create access key ==

	Use puttygen to create public and private keys:		Use puttygen to create public and private SSH keys:

	SSH-2 RSA, 2048 bits		*SSH-2 RSA, 2048 bits
			*save the public and private keys -  ?no need for a passphrase on the private key

	~~save the public and private keys - ?no need for a passphrase on the private key~~		== Add user ==

	~~== Add user ==~~		An existing geek needs to login and "sudu su" to root:

	~~An existing geek needs~~ to ~~login and sudu su~~ to ~~root:~~		*Add a user:
			**adduser <user>
			*giving an initial password
			*Give them su permissions
			**usermod -G sudo -a <user>
			*-G says add to your list of supplemental groups (as opposed to your primary group)
			*-a says append, not replace the list of supplemental groups

	~~Add a user:~~		==  Login ==

	~~adduser <user>~~		The new geek will need to log in using putty (with username and password) then change their password so it's secret.

	~~giving an initial password~~		== Set SSH Key ==

	~~Give them su permissions~~		The new geek should set up logging in using SSH as it is more secure:

	~~usermod -G sudo -a~~ <user>		*mkdir /home/<user>/.ssh
			*In that directory create file authorized_keys
			**in that file you put the public half of any SSH keys you want to use for password-less logging in, ie usually starting with ssh-rsa and ending with rsa-key-20100411
			*You'll want to "chmod 700 .ssh" and "chmod 600 authorized_keys" (read/write only by user) to keep SSH happier.
			*Set up putty and WinSCP to use SSH to login.  In both cases refer to your local private key file.
			*You should now normally access the server using the SSH methods.
			*Note that in WinSCP you cannot "sudo su" to root so some files will not be accessible.

	~~-G says add to your list of supplemental groups (as opposed to your primary group)~~		You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.

	~~-a says append, not replace the list of supplemental groups~~

	~~== Login ==~~

	~~The new geek will need to log in using putty and the password then change their password so it's secret.~~

	~~== Set SSH Key ==~~

	Set SSH keys<br> cd /home/<user>/.ssh (mkdir if need be, making user correct if uploaded)<br>create authorized_keys<br>in that file you put the public half of any SSH keys you want to use for password-less logging in<br>you'll want to "chmod 700 .ssh"<br>and "chmod 600 authorized_keys" (read/write only by user) that keeps SSH happier.<br>You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.~~<br>~~

Chriscant: Created page with 'These are instructions for providing a new geek with full access to our server(s). == Software == On access from Windows, try these: *Putty: [http://www.chiark.greenend.org.uk…'

2011-10-30T12:18:04Z

Created page with 'These are instructions for providing a new geek with full access to our server(s). == Software == On access from Windows, try these: *Putty: [http://www.chiark.greenend.org.uk…'

New page

These are instructions for providing a new geek with full access to our server(s).

== Software ==

On access from Windows, try these:

*Putty: [http://www.chiark.greenend.org.uk/~sgtatham/putty/ http://www.chiark.greenend.org.uk/~sgtatham/putty/] - provides shell prompt
*WinSCP: [http://winscp.net/eng/index.php http://winscp.net/eng/index.php] - provides file access

== Create access key ==

Use puttygen to create public and private keys:

SSH-2 RSA, 2048 bits

save the public and private keys - ?no need for a passphrase on the private key

== Add user ==

An existing geek needs to login and sudu su to root:

Add a user:

adduser <user>

giving an initial password

Give them su permissions

usermod -G sudo -a <user>

-G says add to your list of supplemental groups (as opposed to your primary group)

-a says append, not replace the list of supplemental groups

== Login ==

The new geek will need to log in using putty and the password then change their password so it's secret.

== Set SSH Key ==

Set SSH keys cd /home/<user>/.ssh (mkdir if need be, making user correct if uploaded) create authorized_keys in that file you put the public half of any SSH keys you want to use for password-less logging in you'll want to "chmod 700 .ssh" and "chmod 600 authorized_keys" (read/write only by user) that keeps SSH happier. You only put the public half on servers you are logging into. The private file always stays with you, so you can use the key pair (pvt/pub) to login to as many servers as you care to setup.