NSLU2-Linux
view · edit · print · history

HowTo.BootTelnetEnabled History

Hide minor edits - Show changes to markup

April 16, 2008, at 01:58 PM by LJR --
Changed lines 17-19 from:

Normally inetd.conf does not contain an entry for telnet and what the web interface does is add that line, kill inetd and then restart it. The above simply does the same thing at boot time.

to:

Normally inetd.conf does not contain an entry for telnet and what the web interface does is add that line, kill inetd and then restart it. The above simply does the same thing at boot time.

CAUTION! Even though the web page still appears to activate and kill telnet, telnet will ALWAYS remain enabled - even when the web screen says it is disabled. Make sure you understand the security risks involved. For hardware bitbangers such as me the risk is tolerable. For those with any kind of sensitive information it would not be.

April 15, 2008, at 01:37 AM by LJR -- How to boot unslung with Telnet enabled
April 15, 2008, at 01:37 AM by LJR --
April 15, 2008, at 01:36 AM by LJR --
Added lines 7-8:

Then:

April 15, 2008, at 01:36 AM by LJR --
Added line 8:
April 15, 2008, at 01:35 AM by LJR --
Changed lines 8-10 from:

Compose /unslung/rc.xinetd with the following content:

to:

Create /unslung/rc.xinetd with the following content:

April 15, 2008, at 01:35 AM by LJR --
Changed lines 1-2 from:

I realize that there are good reasons for UnSlung? to default to a disabled Telnet but there are other good reasons for it to come up enabled. I am running a sprinkler system inside an effective firewall and I don't really consider someone hacking a sprinkler system as a threat. Therefore I have created the following recipe that will cause the unit to boot with Telnet active.

to:

I realize that there are good reasons for Unslung to default to a disabled Telnet but there are other good reasons for it to come up enabled. I am running a sprinkler system inside an effective firewall and I don't really consider someone hacking a sprinkler system as a threat. Therefore I have created the following recipe that will cause the unit to boot with Telnet active.

April 15, 2008, at 01:35 AM by LJR --
Changed lines 7-8 from:

Then cp /etc/inetd.conf <to> /unslung

to:
 cp /etc/inetd.conf /unslung
April 15, 2008, at 01:34 AM by LJR --
Changed lines 11-14 from:
  1. !/bin/sh

cp /unslung/inetd.conf /etc return 1

to:
 #!/bin/sh
 cp /unslung/inetd.conf /etc
 return 1
April 15, 2008, at 01:33 AM by LJR --
April 15, 2008, at 01:32 AM by LJR -- How to boot unslung with Telnet enabled
Added lines 1-15:

I realize that there are good reasons for UnSlung? to default to a disabled Telnet but there are other good reasons for it to come up enabled. I am running a sprinkler system inside an effective firewall and I don't really consider someone hacking a sprinkler system as a threat. Therefore I have created the following recipe that will cause the unit to boot with Telnet active.

The recipe is very simple.

First enable telnet via the web interface.

Then cp /etc/inetd.conf <to> /unslung

Compose /unslung/rc.xinetd with the following content:

  1. !/bin/sh

cp /unslung/inetd.conf /etc return 1

Normally inetd.conf does not contain an entry for telnet and what the web interface does is add that line, kill inetd and then restart it. The above simply does the same thing at boot time.

view · edit · print · history · Last edited by LJR.
Originally by LJR.
Page last modified on April 16, 2008, at 01:58 PM