Open Stock Firmware - Revision history

X53sv: /* Create a startup script & config for sshd. */

X53sv — Fri, 06 Apr 2012 15:18:27 GMT

Create a startup script & config for sshd.

← Older revision		Revision as of 15:18, 6 April 2012
Line 87:		Line 87:

	* We will use vi to create & edit the '/etc/init.d/sshd.sh' startup script. (This script does not exist in stock, no backup needed)		* We will use vi to create & edit the '/etc/init.d/sshd.sh' startup script. (This script does not exist in stock, no backup needed)
		+
		+	* If you have firmware 1.56 or 1.57, the /etc/init.d/sshd.sh already exists and does not need to be modified. Update /etc/nas_feature and set SUPPORT_SFTP=1 instead of SUPPORT_SFTP=0.

	Type in the following:		Type in the following:

Okisan: /* Config */

Okisan — Tue, 12 Jul 2011 16:57:22 GMT

Config

← Older revision		Revision as of 16:57, 12 July 2011
Line 167:		Line 167:
	UsePAM no		UsePAM no
	This worked for me on a LinkStation Quad v1.11		This worked for me on a LinkStation Quad v1.11
		+
		+	HostKey file can be generated by
		+	ssh-keygen -t dsa -f /etc/ssh_host_key

	=== Adding Telnet/SSHD to your start up script (rcS). ===		=== Adding Telnet/SSHD to your start up script (rcS). ===

Kage: /* Have a plan */

Kage — Wed, 17 Nov 2010 16:01:32 GMT

Have a plan

← Older revision		Revision as of 16:01, 17 November 2010
Line 18:		Line 18:
	* Probably the most important part... BACKUP, you don't want to lose your important data/system files.		* Probably the most important part... BACKUP, you don't want to lose your important data/system files.
	* If unsure read again, check the wiki, search the forum.... then post.		* If unsure read again, check the wiki, search the forum.... then post.
		+	* Firmware version 1.3.5 appears to break acpcommander, do not upgrade to 1.35 till the issue is resolved.

	== <font color=blue>Getting Console (Telnet) Access with acp_commander</font> ==		== <font color=blue>Getting Console (Telnet) Access with acp_commander</font> ==

Sandius: added how to change root pw with acp_commander without using telnet

Sandius — Thu, 29 Apr 2010 10:34:22 GMT

added how to change root pw with acp_commander without using telnet

← Older revision		Revision as of 10:34, 29 April 2010
Line 57:		Line 57:
	java -jar acp_commander.jar -pw <admin password> -t <quad's IP address> -ip <quad's IP address> -o		java -jar acp_commander.jar -pw <admin password> -t <quad's IP address> -ip <quad's IP address> -o
	Use the admin password which is valid for the web interface. After logging in, you will need to go into the Linkstation's web page, onto the network page, and re-enable DHCP to be able access the net from your linkstation. This will restart the network service (which will pause your telnet session for 10-20 seconds, dont panic, it will come back). Source: http://forum.buffalo.nas-central.org/viewtopic.php?f=66&t=14651		Use the admin password which is valid for the web interface. After logging in, you will need to go into the Linkstation's web page, onto the network page, and re-enable DHCP to be able access the net from your linkstation. This will restart the network service (which will pause your telnet session for 10-20 seconds, dont panic, it will come back). Source: http://forum.buffalo.nas-central.org/viewtopic.php?f=66&t=14651
		+
		+	=== Bypassing Telnet altogether ===
		+	If you fail to get access via telnet you can use the -c option to set root password with acp_commander:
		+	java -jar acp_commander.jar -t <IP Address> -c "(echo <pass>;echo <pass>)\|passwd"
		+	Replace <IP Address> with the IP address of your TS and <pass> with password you want. You can now login via ssh as root using your new password.

	== <font color=blue>Securing</font> ==		== <font color=blue>Securing</font> ==

Maddes: /* SSHD */ add sshd.sh before daemonwatch.sh in /etc/init.de/rcS to avoid errors during boot sequence

Maddes — Wed, 21 Apr 2010 01:24:48 GMT

SSHD: add sshd.sh before daemonwatch.sh in /etc/init.de/rcS to avoid errors during boot sequence

← Older revision		Revision as of 01:24, 21 April 2010
Line 188:		Line 188:
	* If you have taken the option to enable sshd you can add the sshd.sh to this file also.		* If you have taken the option to enable sshd you can add the sshd.sh to this file also.

-	I prefer to keep the file as close to default as possible I will add it to the same section as stock.	+	I prefer to keep the file as close to default as possible I will add it to the same section (step 3) as stock.
-	Add sshd.sh to the line containing (This is for LS-Live, Pro has less scripts to start)	+	Add sshd.sh before daemonwatch.sh, that's the line containing (This is for LS-Live, Pro has less scripts to start)
-	echo " step3 "	+	<pre>echo " step3 "
-	for cmd in micon_setup.sh ~~atalk~~.~~sh ftpd~~.~~sh httpd~~.~~sh lprng.sh smb.sh pcastd.sh epg.sh directcopy.sh~~ clientUtil_servd.sh lsprcvd.sh daemonwatch.sh cron.sh ltbootd.sh logchkd.sh	+	for cmd in micon_setup.sh ... clientUtil_servd.sh lsprcvd.sh daemonwatch.sh cron.sh ltbootd.sh logchkd.sh
-	do	+	do
-	exec_sh $cmd	+	exec_sh $cmd
-	done	+	done</pre>
	Like So:		Like So:
-	echo " step3 "	+	<pre>echo " step3 "
-	for cmd in micon_setup.sh ~~atalk~~.~~sh ftpd~~.~~sh httpd~~.~~sh lprng~~.sh ~~smb~~.sh ~~pcastd.sh epg.sh directcopy.sh clientUtil_servd.sh lsprcvd~~.sh daemonwatch.sh cron.sh ltbootd.sh logchkd~~.sh sshd~~.sh	+	for cmd in micon_setup.sh ... clientUtil_servd.sh lsprcvd.sh sshd.sh daemonwatch.sh cron.sh ltbootd.sh logchkd.sh
-	do	+	do
-	exec_sh $cmd	+	exec_sh $cmd
-	done	+	done</pre>

	Exit vi		Exit vi

Maddes: /* Create a startup script & config for sshd. */ remove -n from echo for cleaner output

Maddes — Tue, 20 Apr 2010 22:27:59 GMT

Create a startup script & config for sshd.: remove -n from echo for cleaner output

← Older revision		Revision as of 22:27, 20 April 2010
Line 101:		Line 101:
	case "$1" in		case "$1" in
	start)		start)
-	echo -n "Start ~~services~~: sshd"	+	echo "Start service: sshd"
	/usr/local/sbin/sshd -f /etc/sshd_config		/usr/local/sbin/sshd -f /etc/sshd_config
	touch ${ACTIVE_FILE}		touch ${ACTIVE_FILE}
	;;		;;
	stop)		stop)
-	echo -n "Stop ~~services~~: sshd"	+	echo "Stop service: sshd"
	killall sshd		killall sshd
	rm -f ${ACTIVE_FILE}		rm -f ${ACTIVE_FILE}

Maddes: /* Create a startup script & config for sshd. */ 2> /dev/null prevented to see errors; only one script variant needed

Maddes — Tue, 20 Apr 2010 22:26:07 GMT

Create a startup script & config for sshd.: 2> /dev/null prevented to see errors; only one script variant needed

← Older revision		Revision as of 22:26, 20 April 2010
Line 86:		Line 86:
	You will then be taken into the text editor.		You will then be taken into the text editor.
	Press i, to get into Insert mode.		Press i, to get into Insert mode.
-	Enter the following code:	+	Enter the following code (valid for all versions, Verified with version 1.06 and 1.33):

-	~~=== Pre 1.11-1a Firmware: ===~~	+	<pre>#! /bin/sh
-	#! /bin/sh	+
-	~~# Start/stop the SSH daemon.~~	+
-	#	+
-	#	+
-		+
-	~~test -f /usr/local/sbin/sshd \|\| exit 0~~	+
-		+
-	~~case "$1" in~~	+
-	~~start) echo -n "Start services: sshd"~~	+
-	~~/usr/local/sbin/sshd -f /etc/sshd_config 2> /dev/null &~~	+
-	;;	+
-	~~stop) echo -n "Stop services: sshd"~~	+
-	~~killall sshd~~	+
-	;;	+
-	~~restart)~~	+
-	~~$0 stop~~	+
-	~~$0 start~~	+
-	;;	+
-	*) echo "Usage: $0 start\|stop\|restart"	+
-	~~exit 1~~	+
-	;;	+
-	~~esac~~	+
-	~~exit 0~~	+

-	~~=== 1.11-1a Firmware: ===~~	+	#
-	~~Verified with version 1.33~~	+	# Start/stop the SSH daemon.
-	#~~! /bin/sh~~	+	#
-	# Start/stop the SSH daemon	+
-	#	+	test -f /usr/local/sbin/sshd \|\| exit 0
-	#	+
-		+	# this is used by daemonwatch (since fw 1.11-1a)
-	test -f /usr/local/sbin/sshd \|\| exit 0	+	ACTIVE_FILE=/var/run/active_sshd
-		+
-	# this is used by daemonwatch	+	case "$1" in
-	ACTIVE_FILE=/var/run/active_sshd	+	start)
-		+	echo -n "Start services: sshd"
-	case "$1" in	+	/usr/local/sbin/sshd -f /etc/sshd_config
-	start) echo -n "Start services: sshd"	+	touch ${ACTIVE_FILE}
-	/usr/local/sbin/sshd -f /etc/sshd_config ~~2> /dev/null &~~	+	;;
-	touch $ACTIVE_FILE	+	stop)
-	;;	+	echo -n "Stop services: sshd"
-	stop) echo -n "Stop services: sshd"	+	killall sshd
-	killall sshd	+	rm -f ${ACTIVE_FILE}
-	rm -f $ACTIVE_FILE	+	;;
-	;;	+	restart)
-	restart)	+	$0 stop
-	$0 stop	+	$0 start
-	$0 start	+	;;
-	;;	+	*)
-	*) echo "Usage: $0 start\|stop\|restart"	+	echo "Usage: $0 start\|stop\|restart"
-	exit 1	+	exit 1
-	;;	+	;;
-	esac	+	esac
-	exit 0	+	exit 0</pre>

	Press Esc to exit Insert mode.		Press Esc to exit Insert mode.

Timtim at 01:45, 19 December 2009

Timtim — Sat, 19 Dec 2009 01:45:14 GMT

← Older revision		Revision as of 01:45, 19 December 2009
Line 437:		Line 437:
	[[Category:Software]]		[[Category:Software]]
	[[Category:LSLive]]		[[Category:LSLive]]
		+	[[Category:LSQuad]]

Arnolde: /* Config */

Arnolde — Thu, 17 Dec 2009 18:50:37 GMT

Config

← Older revision		Revision as of 18:50, 17 December 2009
Line 174:		Line 174:

	Assuming that you have no errors all is fine. You can now login to your Linkstation with your ssh client.		Assuming that you have no errors all is fine. You can now login to your Linkstation with your ssh client.
		+
		+	If the sshd does not start and reports something like this:
		+	Could not load host key: /etc/apache/server.key
		+	Disabling protocol version 1. Could not load host key
		+	Disabling protocol version 2. Could not load host key
		+	sshd: no hostkeys available -- exiting.
		+	try changing the following lines in /etc/sshd_config:
		+	HostKey /etc/ssh_host_key
		+	UsePAM no
		+	This worked for me on a LinkStation Quad v1.11

	=== Adding Telnet/SSHD to your start up script (rcS). ===		=== Adding Telnet/SSHD to your start up script (rcS). ===

Arnolde: /* Getting Console (Telnet) Access with acp_commander */

Arnolde — Thu, 17 Dec 2009 18:34:25 GMT

Getting Console (Telnet) Access with acp_commander

← Older revision		Revision as of 18:34, 17 December 2009
Line 52:		Line 52:
	telnet <IP ADDRESS>		telnet <IP ADDRESS>
	and login with "root" No password should be asked.		and login with "root" No password should be asked.
		+
		+	=== Linkstation Quad with Firmware >= 1.10 ===
		+	If the telnet attempt results in "connection refused", try this:
		+	java -jar acp_commander.jar -pw <admin password> -t <quad's IP address> -ip <quad's IP address> -o
		+	Use the admin password which is valid for the web interface. After logging in, you will need to go into the Linkstation's web page, onto the network page, and re-enable DHCP to be able access the net from your linkstation. This will restart the network service (which will pause your telnet session for 10-20 seconds, dont panic, it will come back). Source: http://forum.buffalo.nas-central.org/viewtopic.php?f=66&t=14651

	== <font color=blue>Securing</font> ==		== <font color=blue>Securing</font> ==