On Tue 18 Dec 2018 at 09:02:45 -0500, Thor Lancelot Simon wrote:
> Apple removed it from OS X and it's a big pain in the ass. I'd suggest
> fix it (going at it with a big torch if necessary to remove likely dead
> and likely dangerous code -- many/most of the options, even things like
> linemode)
Date:Wed, 19 Dec 2018 08:06:19 +1030
From:Brett Lymn
Message-ID: <20181218213619.gb1...@internode.on.net>
| I don't do this personally but I think there are people out there that
| have older, slower machines on their local network
Aside from that, telnet is quit
On Tue, Dec 18, 2018 at 09:02:45AM -0500, Thor Lancelot Simon wrote:
>
> I see far less reason to keep the daemon than the client.
I don't do this personally but I think there are people out there that
have older, slower machines on their local network that take an
inordinate amount of time to pe
On Sat, Dec 15, 2018 at 10:08:00PM +, Taylor R Campbell wrote:
>
> Given that a large fraction of respondents (though not all) indicated
> that their primary use of telnet is to test reachability of a server
> or manually enter SMTP or HTTP requests over the internet -- a use
> which is adequa
On Dec 17, 10:24am, Marc Balmer wrote:
} > Am 17.12.2018 um 08:57 schrieb Martin Husemann :
} > On Sat, Dec 15, 2018 at 10:43:14PM +0100, Marc Balmer wrote:
} >> To me it looks like one or two people don't like telnet and have become
} >> very vocal and loud about removing it and did not invest a l
> Am 17.12.2018 um 08:57 schrieb Martin Husemann :
>
> On Sat, Dec 15, 2018 at 10:43:14PM +0100, Marc Balmer wrote:
>> To me it looks like one or two people don't like telnet and have become
>> very vocal and loud about removing it and did not invest a lot of thought
>> in to the cause. Yes,
On Sat, Dec 15, 2018 at 10:43:14PM +0100, Marc Balmer wrote:
> To me it looks like one or two people don't like telnet and have become
> very vocal and loud about removing it and did not invest a lot of thought
> in to the cause. Yes, I call them ***
Name calling and other personal insul
On Dec 16, 4:16pm, m...@netbsd.org wrote:
}
} I asked to delete it but I was told it'd be socially inconvenient to do
} so right now. You're a difficult bunch.
No, actually we aren't.
}-- End of excerpt from m...@netbsd.org
On Sun, Dec 16, 2018 at 08:11:09PM +, David Holland wrote:
> I have found the 0.18pre1 tarballs if anyone wants them.
Please share :-)
On Sun, Dec 16, 2018 at 07:02:27PM +, m...@netbsd.org wrote:
> On Sun, Dec 16, 2018 at 01:54:24PM -0500, Christos Zoulas wrote:
> > On Dec 16, 6:05pm, dholland-t...@netbsd.org (David Holland) wrote:
> > -- Subject: Re: Moving telnet/telnetd from base to pkgsrc
> >
On Sun, Dec 16, 2018 at 01:54:24PM -0500, Christos Zoulas wrote:
> On Dec 16, 6:05pm, dholland-t...@netbsd.org (David Holland) wrote:
> -- Subject: Re: Moving telnet/telnetd from base to pkgsrc
>
> | On Sat, Dec 15, 2018 at 04:37:30PM +, Christos Zoulas wrote:
> | > I ha
On Dec 16, 6:05pm, dholland-t...@netbsd.org (David Holland) wrote:
-- Subject: Re: Moving telnet/telnetd from base to pkgsrc
| On Sat, Dec 15, 2018 at 04:37:30PM +, Christos Zoulas wrote:
| > I have already started fixing the telnet client code. There is not
| > so much of it...
|
On Sun, Dec 16, 2018 at 06:14:37PM +, m...@netbsd.org wrote:
> On Sun, Dec 16, 2018 at 06:05:55PM +, David Holland wrote:
> > On Sat, Dec 15, 2018 at 04:37:30PM +, Christos Zoulas wrote:
> > > I have already started fixing the telnet client code. There is not
> > > so much of it...
>
On Sun, Dec 16, 2018 at 06:05:55PM +, David Holland wrote:
> On Sat, Dec 15, 2018 at 04:37:30PM +, Christos Zoulas wrote:
> > I have already started fixing the telnet client code. There is not
> > so much of it...
>
> Good luck with that.
>
> You want the diffs from my attempts twenty y
On Sat, Dec 15, 2018 at 04:37:30PM +, Christos Zoulas wrote:
> I have already started fixing the telnet client code. There is not
> so much of it...
Good luck with that.
You want the diffs from my attempts twenty years ago or would you
rather repeat that work? :-/
--
David A. Holland
dhol
On Sun, Dec 16, 2018 at 04:24:54PM +, m...@netbsd.org wrote:
> > > Given that a large fraction of respondents (though not all) indicated
> > > that their primary use of telnet is to test reachability of a server
> > > or manually enter SMTP or HTTP requests over the internet -- a use
> > >
> Date: Sun, 16 Dec 2018 16:16:20 +
> From: m...@netbsd.org
>
> Kerberos is only in authentication. The encryption code in the program
> is DES.
> I asked to delete it but I was told it'd be socially inconvenient to do
> so right now. You're a difficult bunch.
That is not true, and you know i
On Sun, Dec 16, 2018 at 10:33:25AM -0500, Greg Troxel wrote:
> Taylor R Campbell writes:
>
> > Given that a large fraction of respondents (though not all) indicated
> > that their primary use of telnet is to test reachability of a server
> > or manually enter SMTP or HTTP requests over the intern
On Sun, Dec 16, 2018 at 10:30:22AM -0500, Greg Troxel wrote:
> > What's the deal wiht IPSEC?
>
> The protoocol is called IPsec (and often miscapitalized), and our kernel
> option is IPSEC.
>
> > I've never used it, but I was under the impression it gives encryption
> > for free for things that ot
Taylor R Campbell writes:
> Given that a large fraction of respondents (though not all) indicated
> that their primary use of telnet is to test reachability of a server
> or manually enter SMTP or HTTP requests over the internet -- a use
> which is adequately served by the much smaller and much m
> What's the deal wiht IPSEC?
The protoocol is called IPsec (and often miscapitalized), and our kernel
option is IPSEC.
> I've never used it, but I was under the impression it gives encryption
> for free for things that otherwise don't have it.
It provides confidentiality and data origin authent
On Sat, 15 Dec 2018, Taylor R Campbell wrote:
Date: Sat, 15 Dec 2018 22:38:10 +0100
From: Anders Magnusson
I'm pretty sure that all users of telnet know what the implications
are. If they don't then it doesn't matter whether it is in base or not.
One of the implications at the moment is tha
On Sat, 15 Dec 2018, Taylor R Campbell wrote:
Date: Sat, 15 Dec 2018 22:43:14 +0100
From: Marc Balmer
To me it looks like one or two people don't like telnet and
have become very vocal and loud about removing it and did not invest
a lot of thought in to the cause. Yes, I call them dummies
On Dec 15, 8:13pm, m...@netbsd.org wrote:
} On Sat, Dec 15, 2018 at 01:45:04PM +0700, Robert Elz wrote:
} > Date:Fri, 14 Dec 2018 21:28:34 -0800
} > From:John Nemeth
} > Message-ID: <201812150528.wbf5syhr025...@server.cornerstoneservice.ca>
} >
} > | As kre noted,
On Dec 15, 8:58pm, m...@netbsd.org wrote:
} A new version is easier to do without the promise of compatibility.
It's always easy to make a non-functional version of something.
} Anyway, I get it, another case of "please maintain legacy code forever
} and never make significant changes to it
On Dec 15, 7:46pm, m...@netbsd.org wrote:
} On Sat, Dec 15, 2018 at 01:45:04PM +0700, Robert Elz wrote:
} > Date:Fri, 14 Dec 2018 21:28:34 -0800
} > From:John Nemeth
} > Message-ID: <201812150528.wbf5syhr025...@server.cornerstoneservice.ca>
} >
} > | As kre noted,
> Am 15.12.2018 um 23:20 schrieb Alexander Nasonov :
>
> Taylor R Campbell wrote:
>> I know English may not be your first language, so here's a couple of
>> dictionary entries if you would like to read further:
>>
>> https://en.wiktionary.org/wiki/name-calling
>> https://www.merriam-webster.com
On Sat, 15 Dec 2018, Marc Balmer wrote:
a lot of thought in to the cause. Yes, I call them dummies
What, no, I _never_ call anyone names!
Lool
Just to make one thing clear. I will not apologize. I see no need for that.
Rude!
Taylor R Campbell wrote:
> I know English may not be your first language, so here's a couple of
> dictionary entries if you would like to read further:
>
> https://en.wiktionary.org/wiki/name-calling
> https://www.merriam-webster.com/dictionary/name-calling
Patronising?
--
Alex
> Am 15.12.2018 um 23:17 schrieb Alexander Nasonov :
>
> Taylor R Campbell wrote:
>> One of the implications at the moment is that anyone on the internet
>> between you and the remote host can crash your telnet client[*] with
>> no user interaction beyond making a connection.
>
> Index: ./usr.
Taylor R Campbell wrote:
> One of the implications at the moment is that anyone on the internet
> between you and the remote host can crash your telnet client[*] with
> no user interaction beyond making a connection.
Index: ./usr.bin/telnet/telnet.1
Am 15.12.2018 um 23:15 schrieb Taylor R Campbell
:
>> Date: Sat, 15 Dec 2018 22:54:05 +0100
>> From: Marc Balmer
>>
>> Am 15.12.2018 um 22:52 schrieb Taylor R Campbell
>> :
>>
Date: Sat, 15 Dec 2018 22:43:14 +0100
From: Marc Balmer
To me it looks like one or two peopl
> Date: Sat, 15 Dec 2018 22:54:05 +0100
> From: Marc Balmer
>
> Am 15.12.2018 um 22:52 schrieb Taylor R Campbell
> :
>
> >> Date: Sat, 15 Dec 2018 22:43:14 +0100
> >> From: Marc Balmer
> >>
> >> To me it looks like one or two people don't like telnet and
> >> have become very vocal and loud a
Am 15.12.2018 um 23:08 schrieb Taylor R Campbell
:
>> Date: Sat, 15 Dec 2018 22:38:10 +0100
>> From: Anders Magnusson
>>
>> I'm pretty sure that all users of telnet know what the implications
>> are. If they don't then it doesn't matter whether it is in base or not.
>
> One of the implica
> Date: Sat, 15 Dec 2018 22:38:10 +0100
> From: Anders Magnusson
>
> I'm pretty sure that all users of telnet know what the implications
> are. If they don't then it doesn't matter whether it is in base or not.
One of the implications at the moment is that anyone on the internet
between you an
> Am 15.12.2018 um 23:00 schrieb m...@netbsd.org:
>
>> On Sat, Dec 15, 2018 at 10:38:10PM +0100, Anders Magnusson wrote:
>>> Den 2018-12-15 kl. 22:11, skrev Marc Balmer:
>>> Whatever.
>>>
>>> Please keep telnet and telnetd in base. They have their valid use cases.
>>>
>> Yes please. I have
On Sat, Dec 15, 2018 at 10:38:10PM +0100, Anders Magnusson wrote:
> Den 2018-12-15 kl. 22:11, skrev Marc Balmer:
> > Whatever.
> >
> > Please keep telnet and telnetd in base. They have their valid use cases.
> >
> Yes please. I have used both kerberized telnet and plain telnet last 12
> months
Am 15.12.2018 um 22:52 schrieb Taylor R Campbell
:
>> Date: Sat, 15 Dec 2018 22:43:14 +0100
>> From: Marc Balmer
>>
>> To me it looks like one or two people don't like telnet and
>> have become very vocal and loud about removing it and did not invest
>> a lot of thought in to the cause. Yes
> Date: Sat, 15 Dec 2018 22:43:14 +0100
> From: Marc Balmer
>
> To me it looks like one or two people don't like telnet and
> have become very vocal and loud about removing it and did not invest
> a lot of thought in to the cause. Yes, I call them dummies
This is not helpful whether you thi
> Am 15.12.2018 um 22:38 schrieb Anders Magnusson :
>
>> Den 2018-12-15 kl. 22:11, skrev Marc Balmer:
>> Whatever.
>>
>> Please keep telnet and telnetd in base. They have their valid use cases.
>>
> Yes please. I have used both kerberized telnet and plain telnet last 12
> months frequently
Den 2018-12-15 kl. 22:11, skrev Marc Balmer:
Whatever.
Please keep telnet and telnetd in base. They have their valid use cases.
Yes please. I have used both kerberized telnet and plain telnet last 12
months frequently.
I don't think it's up to us try to tell people that "this SW may be
inse
Whatever.
Please keep telnet and telnetd in base. They have their valid use cases.
Thanks,
-mb
> Am 15.12.2018 um 22:06 schrieb m...@netbsd.org:
>
>> On Sat, Dec 15, 2018 at 09:55:34PM +0100, Marc Balmer wrote:
>> Is telnet / telnetd less of a risk to our users if it is in pkgsrc rather
>> t
>
> Anyway, I get it, another case of "please maintain legacy code forever
> and never make significant changes to it".
Don‘t be stupid. I did not say that.
On Sat, Dec 15, 2018 at 09:55:34PM +0100, Marc Balmer wrote:
> Is telnet / telnetd less of a risk to our users if it is in pkgsrc rather
> than in base?
>
> Is pkgsrc the toilet for software you don‘t want to see in base?
>
> Is pkgsrc your personal toilet?
>
> I have good use for telnet and te
A new version is easier to do without the promise of compatibility.
Anyway, I get it, another case of "please maintain legacy code forever
and never make significant changes to it".
Is telnet / telnetd less of a risk to our users if it is in pkgsrc rather than
in base?
Is pkgsrc the toilet for software you don‘t want to see in base?
Is pkgsrc your personal toilet?
I have good use for telnet and telnetd. I don‘t want it to be removed from
base.
-mb
On Sat, Dec 15, 2018 at 01:45:04PM +0700, Robert Elz wrote:
> Date:Fri, 14 Dec 2018 21:28:34 -0800
> From:John Nemeth
> Message-ID: <201812150528.wbf5syhr025...@server.cornerstoneservice.ca>
>
> | As kre noted, it is probably the oldest network application
> | aro
On Sat, Dec 15, 2018 at 01:45:04PM +0700, Robert Elz wrote:
> Date:Fri, 14 Dec 2018 21:28:34 -0800
> From:John Nemeth
> Message-ID: <201812150528.wbf5syhr025...@server.cornerstoneservice.ca>
>
> | As kre noted, it is probably the oldest network application
> | aro
It won't be hard to write a telnet client that does all of that, but
it's not going to have 100% compatibility with the existing client in
netbsd and it will never be tested against ancient telnet servers, so it
won't be accepted as a replacement.
In article <20181215090320.gb17...@mail.duskware.de>,
Martin Husemann wrote:
>On Sat, Dec 15, 2018 at 09:49:06AM +0100, Micha? Górny wrote:
>> To be honest, I don't think you can pull this. Not because telnet is
>> necessary but because Windows-origin users are used to think of telnet
>> as netc
On Sat, Dec 15, 2018 at 09:49:06AM +0100, Micha? Górny wrote:
> To be honest, I don't think you can pull this. Not because telnet is
> necessary but because Windows-origin users are used to think of telnet
> as netcat, and rarely realizing all the dragons hidden there. Changing
> your habits is h
On Thu, 2018-12-13 at 22:50 +, co...@sdf.org wrote:
> Hi,
>
> telnet:
> 1. terrible code, with many abstraction violations
> 2. something people expect to talk to their legacy machines, which
> nobody but them has access to.
> 3. common use case is served by netcat, already in base.
> 4. too m
Date:Fri, 14 Dec 2018 21:28:34 -0800
From:John Nemeth
Message-ID: <201812150528.wbf5syhr025...@server.cornerstoneservice.ca>
| As kre noted, it is probably the oldest network application
| around. According to Wikipedia, the protocol was developed in
| 1969, pr
On Dec 14, 4:22pm, co...@sdf.org wrote:
}
} You know I'm writing this as telnet on netbsd is vulnerable to remote
} exploits, and everyone that can MITM you can do that to you whenever you
} 'telnet to see if ports are open'?
Name the remote exploit! And, don't tell me about MITM.
}-- End
On Dec 14, 1:21pm, Taylor R Campbell wrote:
} > Date: Fri, 14 Dec 2018 09:46:08 +0100
} > From: Edgar Fuß
} >
} > > Y'all seem to think it's totally reasonable to telnet in the open internet
} > What's the problem with "telnet www.uni-bonn.de http"?
}
} If the telnet client is remotely exploita
On Fri, Dec 14, 2018 at 04:53:06PM +, Taylor R Campbell wrote:
> There is an exploit being privately circulated, which is what prompted
> this discussion in the first place, and an advisory is presumably
> forthcoming.
Two local 'exploits', one that had been fixed more than 13 years ago
(with
> Date: Fri, 14 Dec 2018 16:34:47 - (UTC)
> From: mlel...@serpens.de (Michael van Elst)
>
> co...@sdf.org writes:
>
> >You know I'm writing this as telnet on netbsd is vulnerable to remote
> >exploits, and everyone that can MITM you can do that to you whenever you
> >'telnet to see if ports a
co...@sdf.org writes:
>You know I'm writing this as telnet on netbsd is vulnerable to remote
>exploits, and everyone that can MITM you can do that to you whenever you
>'telnet to see if ports are open'?
Obviously wrong.
--
--
Michael van Elst
Internet: mlel...@s
Greg Troxel wrote in :
|Robert Elz writes:
|
|> It does no harm as it is, if you don't use the client, all it does is
|> occupy a couple of hundred blocks (nothing), the server is not
|> enabled by default, and it is even smaller.
|
|I agree. I use it often, to see if TCP ports are open an
You know I'm writing this as telnet on netbsd is vulnerable to remote
exploits, and everyone that can MITM you can do that to you whenever you
'telnet to see if ports are open'?
On 12/14/18 2:21 PM, Taylor R Campbell wrote:
We should at least have warnings on it until someone takes up
maintenance not to use it on the open internet.
This comes around to me similar to having a notice in the cup of coffee
just bought "Caution: content may be hot", or instructions for
campbell+netbsd-tech-userle...@mumble.net (Taylor R Campbell) writes:
>If the telnet client is remotely exploitable
Is it?
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
> Date: Fri, 14 Dec 2018 09:46:08 +0100
> From: Edgar Fuß
>
> > Y'all seem to think it's totally reasonable to telnet in the open internet
> What's the problem with "telnet www.uni-bonn.de http"?
If the telnet client is remotely exploitable then that exposes you to
exploitation by www.uni-bonn.d
Robert Elz writes:
> It does no harm as it is, if you don't use the client, all it does is
> occupy a couple of hundred blocks (nothing), the server is not
> enabled by default, and it is even smaller.
I agree. I use it often, to see if TCP ports are open and hand-type
smtp or http.
Another
> Date: Fri, 14 Dec 2018 09:41:20 +0100
> From: Edgar Fuß
>
> > send hate mail my way.
> I guess you are over-looking my (and probably a lot of other network
> administrator's) primary use case for /usr/bin/telnet: connect to a
> HTTP/SMTP/IMAP/whatever port and speak the protocol.
That's what
On Dec 14, 4:56am, co...@sdf.org wrote:
}
} The maintenance burden is as follows:
}
} - Y'all seem to think it's totally reasonable to telnet in the open
} internet
Nobody thinks it should be used in the open internet in any
situation where security is required, at least not without using
On Fri, 14 Dec 2018, Edgar Fu? wrote:
send hate mail my way.
I guess you are over-looking my (and probably a lot of other network
administrator's) primary use case for /usr/bin/telnet: connect to a
HTTP/SMTP/IMAP/whatever port and speak the protocol.
Yep, there's still a lot of network gear o
> Y'all seem to think it's totally reasonable to telnet in the open internet
What's the problem with "telnet www.uni-bonn.de http"?
> send hate mail my way.
I guess you are over-looking my (and probably a lot of other network
administrator's) primary use case for /usr/bin/telnet: connect to a
HTTP/SMTP/IMAP/whatever port and speak the protocol.
Date:Fri, 14 Dec 2018 04:56:02 +
From:co...@sdf.org
Message-ID: <20181214045601.ga12...@sdf.org>
| The maintenance burden is as follows:
|
| - Y'all seem to think it's totally reasonable to telnet in the open
| internet
|
| This means it begs for a re
On 14.12.2018 06:40, Kamil Rytarowski wrote:
> On 13.12.2018 23:50, co...@sdf.org wrote:
>> Hi,
>>
>> telnet:
>> 1. terrible code, with many abstraction violations
>> 2. something people expect to talk to their legacy machines, which
>> nobody but them has access to.
Actually telnet is used active
On 13.12.2018 23:50, co...@sdf.org wrote:
> Hi,
>
> telnet:
> 1. terrible code, with many abstraction violations
> 2. something people expect to talk to their legacy machines, which
> nobody but them has access to.
> 3. common use case is served by netcat, already in base.
> 4. too much superfluou
On Fri, 14 Dec 2018, Sevan Janiyan wrote:
On 13/12/2018 22:50, co...@sdf.org wrote:
telnet:
1. terrible code, with many abstraction violations
2. something people expect to talk to their legacy machines, which
nobody but them has access to.
3. common use case is served by netcat, already in bas
The maintenance burden is as follows:
- Y'all seem to think it's totally reasonable to telnet in the open
internet
This means it begs for a rewrite
- You'd want some esoteric functionality preserved
This means rewriting it isn't going to happen
On Dec 13, 10:50pm, co...@sdf.org wrote:
}
} telnet:
} 1. terrible code, with many abstraction violations
} 2. something people expect to talk to their legacy machines, which
} nobody but them has access to.
} 3. common use case is served by netcat, already in base.
} 4. too much superfluous funct
On 13/12/2018 22:50, co...@sdf.org wrote:
> telnet:
> 1. terrible code, with many abstraction violations
> 2. something people expect to talk to their legacy machines, which
> nobody but them has access to.
> 3. common use case is served by netcat, already in base.
> 4. too much superfluous functio
On Fri, 14 Dec 2018 00:06:18 +0100
Manuel Bouyer wrote:
> On Thu, Dec 13, 2018 at 10:50:30PM +, co...@sdf.org wrote:
> > Hi,
> >
> > telnet:
> > 1. terrible code, with many abstraction violations
> > 2. something people expect to talk to their legacy machines, which
> > nobody but them has a
Manuel Bouyer wrote:
> On Thu, Dec 13, 2018 at 10:50:30PM +, co...@sdf.org wrote:
> > Hi,
> >
> > telnet:
> > [ ... ]
> > Let's pull it out as a package, the alternative being breaking
> > functionality for the four remaining users.
>
> Actually, lots of mananged network equipements (or remot
On Thu, Dec 13, 2018 at 10:50:30PM +, co...@sdf.org wrote:
> Hi,
>
> telnet:
> 1. terrible code, with many abstraction violations
> 2. something people expect to talk to their legacy machines, which
> nobody but them has access to.
> 3. common use case is served by netcat, already in base.
> 4
79 matches
Mail list logo
