Pi and pine - Revision history

Tim: /* pi2 pi3 pine64 */

2017-01-28T04:42:37Z

pi2 pi3 pine64

← Older revision		Revision as of 00:42, 28 January 2017
Line 8:		Line 8:

	sudo nano /etc/hostname		sudo nano /etc/hostname

			then reboot

	windowsstartmenu->search->hosts opens the notepad to edit the /Windows/System32/drivers/etc/hosts file		windowsstartmenu->search->hosts opens the notepad to edit the /Windows/System32/drivers/etc/hosts file

2017-01-28T04:31:37Z

← Older revision		Revision as of 00:31, 28 January 2017
Line 5:		Line 5:

	====hosts====		====hosts====
			To change the host from ubuntu to pi3

			sudo nano /etc/hostname

	windowsstartmenu->search->hosts opens the notepad to edit the /Windows/System32/drivers/etc/hosts file		windowsstartmenu->search->hosts opens the notepad to edit the /Windows/System32/drivers/etc/hosts file

2017-01-25T00:26:07Z

device ip addresses and hosts

← Older revision		Revision as of 20:26, 24 January 2017
Line 1:		Line 1:
	=pi2 pi3 pine64=		=pi2 pi3 pine64=
	====device ip addresses ~~and hosts~~====		====device ip addresses====
	To find out the ip adresses assigned to a device use the zenmap windows program and put in the command		To find out the ip adresses assigned to a device use the zenmap windows program and put in the command
	nmap -sP 10.0.1.0/24		nmap -sP 10.0.1.0/24

2017-01-24T22:55:45Z

hosts

← Older revision		Revision as of 18:55, 24 January 2017
Line 5:		Line 5:

	====hosts====		====hosts====
	windowsstartmenu/hosts~~(search)~~ opens the notepad to edit the ~~windows~~/System32/drivers/etc/hosts file		windowsstartmenu->search->hosts opens the notepad to edit the /Windows/System32/drivers/etc/hosts file

	Now you and update the ip for pi2 pine64 and whatever else there and refer to the devices as root@pi2 and ssh root@pine64 in ssh and winSCP		Now you and update the ip for pi2 pine64 and whatever else there and refer to the devices as root@pi2 and ssh root@pine64 in ssh and winSCP

			(found the start menu windowsstartmenu->allprograms->rightclick->open and rightclick->new->shortcut and put in "notepad.exe /Windows/System32/drivers/etc/hosts", named it hosts and the rightclicked on hosts ->advanced->runasAdminiistrator)

	====id.rsa certs for winSCP and ssh====		====id.rsa certs for winSCP and ssh====

2017-01-24T22:50:29Z

device ip addresses

← Older revision		Revision as of 18:50, 24 January 2017
Line 1:		Line 1:
	=pi2 pi3 pine64=		=pi2 pi3 pine64=
	====device ip addresses====		====device ip addresses and hosts====
	To find out the ip adresses assigned to a device use the zenmap windows program and put in the command		To find out the ip adresses assigned to a device use the zenmap windows program and put in the command
	nmap -sP 10.0.1.0/24		nmap -sP 10.0.1.0/24

			====hosts====
			windowsstartmenu/hosts(search) opens the notepad to edit the windows/System32/drivers/etc/hosts file

			Now you and update the ip for pi2 pine64 and whatever else there and refer to the devices as root@pi2 and ssh root@pine64 in ssh and winSCP

	====id.rsa certs for winSCP and ssh====		====id.rsa certs for winSCP and ssh====
	<s>In general you can't edit root owned files with WinSCP unless you are root. The only way to be root is to be able to login as root from		<s>In general you can't edit root owned files with WinSCP unless you are root. The only way to be root is to be able to login as root from

2017-01-24T22:01:56Z

← Older revision		Revision as of 18:01, 24 January 2017
Line 1:		Line 1:
	=pi2 pi3 pine64=		=pi2 pi3 pine64=
	===device ip addresses===		====device ip addresses====
	To find out the ip adresses assigned to a device use the zenmap windows program and put in the command		To find out the ip adresses assigned to a device use the zenmap windows program and put in the command
	nmap -sP 10.0.1.0/24		nmap -sP 10.0.1.0/24
	===id.rsa certs for winSCP and ssh===		====id.rsa certs for winSCP and ssh====
	<s>In general you can't edit root owned files with WinSCP unless you are root. The only way to be root is to be able to login as root from		<s>In general you can't edit root owned files with WinSCP unless you are root. The only way to be root is to be able to login as root from
	sudo nano /etc/ssh/sshd_config		sudo nano /etc/ssh/sshd_config

2017-01-24T22:00:55Z

← Older revision		Revision as of 18:00, 24 January 2017
Line 3:		Line 3:
	To find out the ip adresses assigned to a device use the zenmap windows program and put in the command		To find out the ip adresses assigned to a device use the zenmap windows program and put in the command
	nmap -sP 10.0.1.0/24		nmap -sP 10.0.1.0/24
			===id.rsa certs for winSCP and ssh===
	<s>In general you can't edit root owned files with WinSCP unless you are root. The only way to be root is to be able to login as root from		<s>In general you can't edit root owned files with WinSCP unless you are root. The only way to be root is to be able to login as root from
	sudo nano /etc/ssh/sshd_config		sudo nano /etc/ssh/sshd_config

2017-01-24T21:59:36Z

pi2 pi3 pine64

← Older revision		Revision as of 17:59, 24 January 2017
Line 1:		Line 1:
	=pi2 pi3 pine64=		=pi2 pi3 pine64=
			===device ip addresses===
	To find out the ip adresses assigned to a device use the zenmap windows program and put in the command		To find out the ip adresses assigned to a device use the zenmap windows program and put in the command
	nmap -sP 10.0.1.0/24		nmap -sP 10.0.1.0/24

2017-01-24T21:58:41Z

pi2 pi3 pine64

← Older revision		Revision as of 17:58, 24 January 2017
Line 1:		Line 1:
	=pi2 pi3 pine64=		=pi2 pi3 pine64=
	In general you can't edit root owned files with WinSCP unless you are root. The only way to be root is to be able to login as root from		To find out the ip adresses assigned to a device use the zenmap windows program and put in the command
			nmap -sP 10.0.1.0/24

			<s>In general you can't edit root owned files with WinSCP unless you are root. The only way to be root is to be able to login as root from
	sudo nano /etc/ssh/sshd_config		sudo nano /etc/ssh/sshd_config
	by changing		by changing
Line 8:		Line 11:
	restart sshd service using:		restart sshd service using:
	/etc/init.d/ssh restart		/etc/init.d/ssh restart
	:ref: http://raspberrypi.stackexchange.com/questions/48056/login-as-root-not-possible		:ref: http://raspberrypi.stackexchange.com/questions/48056/login-as-root-not-possible</s>

	But that is not really smart, you should keep your id_rsa.pub certificate from your laptop in the server users ./ssh/authorized_keys file		But that is not really smart, you should keep your id_rsa.pub certificate from your laptop in the server users ./ssh/authorized_keys file

2017-01-24T19:38:34Z

pi2 pi3 pine64

← Older revision		Revision as of 15:38, 24 January 2017
Line 6:		Line 6:
	to		to
	PermitRootLogin yes		PermitRootLogin yes
			restart sshd service using:
			/etc/init.d/ssh restart
	:ref: http://raspberrypi.stackexchange.com/questions/48056/login-as-root-not-possible		:ref: http://raspberrypi.stackexchange.com/questions/48056/login-as-root-not-possible

Line 12:		Line 14:
	and then switch back to		and then switch back to
	PermitRootLogin without-password		PermitRootLogin without-password
			restart sshd service using:
			/etc/init.d/ssh restart
	{{:ubuntu 16.04}}		{{:ubuntu 16.04}}
	{{:pine64}}		{{:pine64}}
	{{:pi}}		{{:pi}}