work around for Windows TELNET?
To: None <email@example.com>
From: Christos Zoulas <firstname.lastname@example.org>
Date: 08/15/2006 20:11:28
In article <E7B0D968-1BAA-41DA-818D-EC51CADF4EEA@cirr.com>,
Stephen Jones <email@example.com> wrote:
>Hi, to everyone who has replied either privately or publicly to me
>me that TELNET is 1. not a security issue under certain circumstances
>to use putty, thank you, but you are totally missing the point of my
>Neither of those are the issue here. What I am trying to get at is that
>the w2k/xp TELNET client seems to react differently with the NetBSD
>than the say Leen0x telnetd. I also stated in the initial email that
>suggesting to w2k/xp users to use a different client or 'unset crlf'
>via their client.
>So for those of you who replied with that information, you're not
>As I said in my previous post I do not have access to Windows, so I
>off of what I can examine from logs and what others who use Windows
>can tell me.
>Forcing complete strangers to use putty (or any other telnet client)
>of the question. I've been suggesting it since I was first informed
>problem. It may be the case that these people do not have the
>install software on the computer they are using, but for what ever
>is, I want them be able to enjoy learning about NetBSD without having to
>deal with this petty issue.
>So far I've not really heard any information that would lead me to
>changes (either by configuration or source modification) or stty
>get around the issue of the w2k/xp telnet client sending, seemingly
>double carriage returns.
>I've tried using -l for 'kludge' mode, but that doesn't seem resolve
>according to w2k/xp users. I've also tried using various stty
>to the defaults with leen0x (according to users), but that seems to
>double return behaviour.
>Yes, this is Windows client issue, but how difficult would it be for
>us to accommodate
Try running telnetd -k [kludgelinemode]