John Nemeth wrote:
> Numerous people have stated that they use telnet on a local
> network on older systems where ssh is too slow. For this purpose,
> it is pretty obvious that a telnetd would be needed.
I use rlogin/rlogind on my pc532. Never thought to use telnetd! I do
use the telnet c
On Dec 20, 3:56pm, haad wrote:
}
} Maybe we can use [1] to write new client. As we probably don't need a telnetd.
Numerous people have stated that they use telnet on a local
network on older systems where ssh is too slow. For this purpose,
it is pretty obvious that a telnetd would be neede
Hi Rhialto,
PuTTY is also in pkgsrc :-) from patches/
$NetBSD: patch-unix_uxpgnt.c,v 1.2 2017/03/17 11:55:53 maya Exp $
BSD setpgrp has parameters. POSIX says it is undefined whether
setpgrp(0,0) == setpgrp() and it should use setpgid.
Use setpgid without parameters on non-BSD
--- unix/uxpgn
On 20.12.2018 15:56, haad wrote:
> Maybe we can use [1] to write new client. As we probably don't need a telnetd.
>
> [1] https://github.com/seanmiddleditch/libtelnet
Actually I find native daemon useful too.
signature.asc
Description: OpenPGP digital signature
On Thu, Dec 20, 2018 at 3:52 PM Rhialto wrote:
>
> On Wed 19 Dec 2018 at 22:10:22 -0800, John Nemeth wrote:
> > PuTTY comes with a built-in terminal emulator and GUI based
> > menus. As far as I know, there is no way use it via a CLI. If
> > somebody does know of one, please tell us.
>
> I
On Wed 19 Dec 2018 at 22:10:22 -0800, John Nemeth wrote:
> PuTTY comes with a built-in terminal emulator and GUI based
> menus. As far as I know, there is no way use it via a CLI. If
> somebody does know of one, please tell us.
I suppose that the telnet protocol part can be used separetely.
On Wed, Dec 19, 2018 at 10:00:06PM -0800, John Nemeth wrote:
> } The previous telnet thread, contentious as it has been, has completely
> } missed the critical context, which is that telnet is 14,700 lines
> } cutpasted from the Necronomicon and telnetd is only slightly better.
>
> Yeah,
On Wed, Dec 19, 2018 at 11:48:49PM +, David Holland wrote:
> If you value your sanity, don't. But, also, you might want to rethink
> how much you trust it.
As much as the network I run it on. If someone can do a MITM on this
network I have a much bigger problem than a telnet exploit.
--
Manu
On Dec 19, 4:14pm, "J. Lewis Muir" wrote:
} Subject: Re: deleting telnet/telnetd
} On Wed, Dec 19, 2018 at 1:11 PM David Holland
wrote:
} > If the conclusion is that we really need a telnet client (I myself
} > really don't care if it's in base or not) then we
On Wed, Dec 19, 2018 at 10:04:19PM -0800, John Nemeth wrote:
> } The reason it came up this week is that someone found and posted a
> } couple noncritical problems in one of the other forks of it.
>
> And, how many years has it been since the last significant bug?
How many years has it b
John, you get everything you could possibly get: we're definitely not
deleting telnet. Please stop poking people in this thread which has gone
on for too long.
On Wed, Dec 19, 2018 at 10:17:28PM -0800, John Nemeth wrote:
> } - PuTTY is nice
>
> PuTTY is a graphical app, and therefore not a replacement for
> telnet(1). If there is a way to use it from a command line, please
> let us know.
As you would know if you'd bothered to look, PuTTY cont
On Wed, 19 Dec 2018, John Nemeth wrote:
One that still hasn't been released publically, so there is
no point in talking about it.
https://hacker.house/releasez/expl0itz/telnet_term_0day.py was released
last week... it's a proof of concept that doesn't do anything except make
telnet crash,
On Dec 20, 1:25am, m...@netbsd.org wrote:
} On Thu, Dec 20, 2018 at 09:24:35AM +0900, Rin Okuyama wrote:
} > On 2018/12/20 7:08, Hisashi T Fujinaka wrote:
} > > On Wed, 19 Dec 2018, David Holland wrote:
} > >
} > > > On Wed, Dec 19, 2018 at 01:36:48PM -0800, Hisashi T Fujinaka wrote:
} > > > > Te
On Dec 19, 11:48pm, David Holland wrote:
} On Wed, Dec 19, 2018 at 11:06:58PM +0100, Manuel Bouyer wrote:
} > On Wed, Dec 19, 2018 at 10:03:19PM +, David Holland wrote:
} > > On Wed, Dec 19, 2018 at 10:58:14PM +0100, Manuel Bouyer wrote:
} > > > On Wed, Dec 19, 2018 at 09:03:27PM +, Dav
On Dec 19, 10:55pm, m...@netbsd.org wrote:
} On Wed, Dec 19, 2018 at 10:14:47PM +, m...@netbsd.org wrote:
} > Relax, the end conclusion was not to delete it. To maintain it until a
} > replacement comes in. Please help test the replacement if it is written,
} > to ensure it works for your case.
On Dec 19, 9:03pm, David Holland wrote:
} On Wed, Dec 19, 2018 at 12:32:08PM -0800, Hisashi T Fujinaka wrote:
} > I don't understand your position. Let me explain why.
} >
} > You're saying, "Write a new one, and it's going to be close to
} > impossible," at the same time you're saying, "Dele
On Dec 19, 12:32pm, Hisashi T Fujinaka wrote:
}
} I don't understand your position. Let me explain why.
}
} You're saying, "Write a new one, and it's going to be close to
} impossible," at the same time you're saying, "Delete this one."
}
} If it's impossible, and we need one, we'll need to keep
On Dec 19, 7:11pm, David Holland wrote:
}
} The previous telnet thread, contentious as it has been, has completely
} missed the critical context, which is that telnet is 14,700 lines
} cutpasted from the Necronomicon and telnetd is only slightly better.
Yeah, so?
} If the conclusion is that
On 19.12.2018 21:32, Hisashi T Fujinaka wrote:
> I don't understand your position. Let me explain why.
>
> You're saying, "Write a new one, and it's going to be close to
> impossible," at the same time you're saying, "Delete this one."
>
> If it's impossible, and we need one, we'll need to keep t
On Thu, Dec 20, 2018 at 09:24:35AM +0900, Rin Okuyama wrote:
> On 2018/12/20 7:08, Hisashi T Fujinaka wrote:
> > On Wed, 19 Dec 2018, David Holland wrote:
> >
> > > On Wed, Dec 19, 2018 at 01:36:48PM -0800, Hisashi T Fujinaka wrote:
> > > > Telnet is used every day and most of the use cases can us
On 2018/12/20 7:08, Hisashi T Fujinaka wrote:
On Wed, 19 Dec 2018, David Holland wrote:
On Wed, Dec 19, 2018 at 01:36:48PM -0800, Hisashi T Fujinaka wrote:
> Telnet is used every day and most of the use cases can use nc.
>
> I wish you'd get rid of it because that would mean I can resign and
>
Date:Wed, 19 Dec 2018 21:03:27 +
From:David Holland
Message-ID: <20181219210327.ga5...@netbsd.org>
| But it can't be fixed and sooner or later someone's going to
| find a critical problem with it.
Nothing can't be fixed. It all depends what the objective is
On Wed, Dec 19, 2018 at 11:06:58PM +0100, Manuel Bouyer wrote:
> On Wed, Dec 19, 2018 at 10:03:19PM +, David Holland wrote:
> > On Wed, Dec 19, 2018 at 10:58:14PM +0100, Manuel Bouyer wrote:
> > > On Wed, Dec 19, 2018 at 09:03:27PM +, David Holland wrote:
> > > > [...]
> > > > The h
On Wed, Dec 19, 2018 at 10:03:19PM +, David Holland wrote:
> On Wed, Dec 19, 2018 at 10:58:14PM +0100, Manuel Bouyer wrote:
> > On Wed, Dec 19, 2018 at 09:03:27PM +, David Holland wrote:
> > > [...]
> > > The hope, I think, was that the conclusion would be that we don't
> > > really nee
On Wed, Dec 19, 2018 at 10:14:47PM +, m...@netbsd.org wrote:
> Relax, the end conclusion was not to delete it. To maintain it until a
> replacement comes in. Please help test the replacement if it is written,
> to ensure it works for your case.
- Given an exploit, it's still going to be an uni
On Wed, Dec 19, 2018 at 10:14:47PM +, m...@netbsd.org wrote:
> Relax, the end conclusion was not to delete it. To maintain it until a
> replacement comes in. Please help test the replacement if it is written,
> to ensure it works for your case.
Obviously since we've concluded we need a teln
On Wed, Dec 19, 2018 at 02:08:46PM -0800, Hisashi T Fujinaka wrote:
> On Wed, 19 Dec 2018, David Holland wrote:
>
> > On Wed, Dec 19, 2018 at 01:36:48PM -0800, Hisashi T Fujinaka wrote:
> > > Telnet is used every day and most of the use cases can use nc.
> > >
> > > I wish you'd get rid of i
Relax, the end conclusion was not to delete it. To maintain it until a
replacement comes in. Please help test the replacement if it is written,
to ensure it works for your case.
On Wed, Dec 19, 2018 at 1:11 PM David Holland wrote:
> If the conclusion is that we really need a telnet client (I myself
> really don't care if it's in base or not) then we should write a new
> one.
Or use an existing one?
PuTTY
https://www.chiark.greenend.org.uk/~sgtatham/putty/
claims to
On Wed, 19 Dec 2018, David Holland wrote:
On Wed, Dec 19, 2018 at 01:36:48PM -0800, Hisashi T Fujinaka wrote:
> Telnet is used every day and most of the use cases can use nc.
>
> I wish you'd get rid of it because that would mean I can resign and
> delete NetBSD and get rid of a lot of old hardw
On Wed, Dec 19, 2018 at 10:58:14PM +0100, Manuel Bouyer wrote:
> On Wed, Dec 19, 2018 at 09:03:27PM +, David Holland wrote:
> > [...]
> > The hope, I think, was that the conclusion would be that we don't
> > really need one.
>
> We really need one, and the one we have does the job. I rea
On Wed, Dec 19, 2018 at 01:36:48PM -0800, Hisashi T Fujinaka wrote:
> Telnet is used every day and most of the use cases can use nc.
>
> I wish you'd get rid of it because that would mean I can resign and
> delete NetBSD and get rid of a lot of old hardware.
You realize I'm not one of the del
On Wed, Dec 19, 2018 at 09:03:27PM +, David Holland wrote:
> [...]
> The hope, I think, was that the conclusion would be that we don't
> really need one.
We really need one, and the one we have does the job. I really don't see
why we shoud rewrite something that works.
--
Manuel Bouyer
On 12/19/18 10:36 PM, Hisashi T Fujinaka wrote:
I wish you'd get rid of it because that would mean I can resign and
delete NetBSD and get rid of a lot of old hardware.
I'm having the same feeling... :-(
regards,
chris
On Wed, 19 Dec 2018, David Holland wrote:
On Wed, Dec 19, 2018 at 12:32:08PM -0800, Hisashi T Fujinaka wrote:
> I don't understand your position. Let me explain why.
>
> You're saying, "Write a new one, and it's going to be close to
> impossible," at the same time you're saying, "Delete this one
On Wed, Dec 19, 2018 at 12:32:08PM -0800, Hisashi T Fujinaka wrote:
> I don't understand your position. Let me explain why.
>
> You're saying, "Write a new one, and it's going to be close to
> impossible," at the same time you're saying, "Delete this one."
>
> If it's impossible, and we nee
I don't understand your position. Let me explain why.
You're saying, "Write a new one, and it's going to be close to
impossible," at the same time you're saying, "Delete this one."
If it's impossible, and we need one, we'll need to keep the old one no
matter how bad it is, right? And if you can'
38 matches
Mail list logo
