Re: Enabling telnet access
Paal Marker wrote: > debian 3.0r2 kernel 2.2.20 You probably really want to consider upgrading to a 2.4 kernel. Debian 3.0r2 supports linux-2.4.18 with security patches. > I have installed telnetd, and it is running. You probably also want to install telnetd-ssl instead. It does not really change anything. But at least then 'ssh' don't send you hate mail about having telnetd installed. I think that is an annoyance of the ssh package. But easy enough to work around, I guess. Bob pgpVvirUPJNxn.pgp Description: PGP signature
Re: Enabling telnet access
Paal Marker <[EMAIL PROTECTED]> writes: > > When telneting the box I get into the login, asked for username. When > entering a valid username I get this message: > "System bootup in progress -please wait" You probably have an "/etc/nologin" file (containing this text you see) that wasn't deleted by the bootscripts. The presence of this file is supposed to prevent *any* non-root logins. (See the nologin(5) manpage.) Any chance you're running this machine in single-user mode or in some other nonstandard configuration? Assuming the standard runlevel (number 2) and standard Debian startup scripts, the "/etc/nologin" file should have been removed by "/etc/rc2.d/S99rmnologin" link to "/etc/init.d/rmnologin". -- Kevin <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Enabling telnet access
On Fri, 18 Jun 2004 08:46:41 +0200, Paal Marker wrote > debian 3.0r2 kernel 2.2.20 > I have got some workstations inside a network, and I will need > telnet access to them. > > I have installed telnetd, and it is running. > > When telneting the box I get into the login, asked for username. > When entering a valid username I get this message: "System bootup in > progress -please wait" > > And then login incorrect. > > If I try a in.telnetd restart I get the message: "telnetd: > getpeername: socket operation on non-socket. " > > Can anyone tell me what needs to be configured? You may want to try re-installing telnetd on your system. I also remembering seeing a similar message like that when trying to login into the terminal when I had a custom runlevel with most daemons turned off. Perhaps check to see that all your daemons are running properly. And as others have mentioned prior, ssh is better. Sounds like you'll use it instead. Cheers, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Enabling telnet access
On Fri, 18 Jun 2004 05:12:00 -0400, Carl Fink <[EMAIL PROTECTED]> wrote: > Anyone eavesdropping on your network can read your telnet account name and > password from the traffic, since they're sent in clear. Now, if the network > is entirely switched that becomes harder But not too much harder: http://www.securesphere.net/download/papers/SwitchSniff.htm (and also look at 'dsniff'). Sid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Enabling telnet access
On Fri, Jun 18, 2004 at 10:53:21AM +0200, Paal Marker wrote: > Well, telnet is the default inside our network, so I wanted to stick to > it. As the debian-box is inside the local nets firewall and each box has > a strict local firewall, security is not a real issue. Yes it is. Anyone eavesdropping on your network can read your telnet account name and password from the traffic, since they're sent in clear. Now, if the network is entirely switched that becomes harder -- Carl Fink [EMAIL PROTECTED] Jabootu's Minister of Proofreading http://www.jabootu.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Enabling telnet access
Paal Marker <[EMAIL PROTECTED]> writes: > Paul Johnson wrote: > >>Paal Marker <[EMAIL PROTECTED]> writes: >> >>>I have installed telnetd, and it is running. >> >>Why not just use ssh? It just drops in and works, and is a lot more >>flexable and secure than telnet. >> > Well, telnet is the default inside our network, so I wanted to stick > to it. As the debian-box is inside the local nets firewall and each > box has a strict local firewall, security is not a real issue. I tend towards not wanting to give an attacker an easy reward once they're inside, but hey, if you want just one wall to fall... > As I am new to debian, switching from rh, I have to adapt some > knowledge. But ok, I have found how to configure ssh and use it > now. But it did absolutely not just drop in and work straight out of > the box, I had to do some conf to get it up. Care to go into detail for the sake of the archives? If someone else is having the same problem, they'll benefit from your experience if you post it. -- Paul Johnson <[EMAIL PROTECTED]> Linux. You can find a worse OS, but it costs more. pgpkxfHzgaxuI.pgp Description: PGP signature
Re: Enabling telnet access
Paul Johnson wrote: Paal Marker <[EMAIL PROTECTED]> writes: I have installed telnetd, and it is running. Why not just use ssh? It just drops in and works, and is a lot more flexable and secure than telnet. Well, telnet is the default inside our network, so I wanted to stick to it. As the debian-box is inside the local nets firewall and each box has a strict local firewall, security is not a real issue. As I am new to debian, switching from rh, I have to adapt some knowledge. But ok, I have found how to configure ssh and use it now. But it did absolutely not just drop in and work straight out of the box, I had to do some conf to get it up. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Enabling telnet access
Paal Marker <[EMAIL PROTECTED]> writes: > I have installed telnetd, and it is running. Why not just use ssh? It just drops in and works, and is a lot more flexable and secure than telnet. -- Paul Johnson <[EMAIL PROTECTED]> Linux. You can find a worse OS, but it costs more. pgp6yJGxoXvgP.pgp Description: PGP signature
Re: Enabling telnet access
On Fri, 2004-06-18 at 08:46, Paal Marker wrote: > debian 3.0r2 kernel 2.2.20 > I have got some workstations inside a network, and I will need telnet > access to them. > > I have installed telnetd, and it is running. why ohh why are you using telnet when you can use ssh ? i know it was not a answer, but i had to ask -- Ronny Aasen <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Enabling telnet access
debian 3.0r2 kernel 2.2.20 I have got some workstations inside a network, and I will need telnet access to them. I have installed telnetd, and it is running. When telneting the box I get into the login, asked for username. When entering a valid username I get this message: "System bootup in progress -please wait" And then login incorrect. If I try a in.telnetd restart I get the message: "telnetd: getpeername: socket operation on non-socket. " Can anyone tell me what needs to be configured? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
