On Sat 07 Dec 2024 at 08:39:54 (-0700), pe...@easthope.ca wrote:
> > Unencrypted login sessions, with passwords being
> > sent in the clear over a network, are inherently insecure.
>
> You give a password every time a xterm or similar is opened? To my
> understanding, most users just open the ter
Hi,
On Sat, Dec 07, 2024 at 08:39:54AM -0700, pe...@easthope.ca wrote:
> > Unencrypted login sessions, with passwords being > sent in the clear
> > over a network, are inherently insecure.
>
> You give a password every time a xterm or similar is opened?
As has been noted multiple times in this t
rom 11 to 12.
Booted Debian 12, made utelnetd and tested. Works as indicated in
various Web pages.
> I won't try to guess how important the warnings are.
I'd expect a compiler guru to say they're critically important and
revealing and valuable!
> There is no need to co
peter wrote:
> Retrieved utelnetd 0.1.11 from here.
> https://public.pengutronix.de/software/utelnetd/
OK, let's look at this thing. The tarball from the above web site
contains:
hobbit:~/tmp$ tar tzvf ~/Downloads/utelnetd-0.1.11.tar.gz
drwxr-xr-x frogger/frogger 0 2008-08-11 05:
On 24/11/2024 23:11, pe...@easthope.ca wrote:
An embedded system may have one terminal connected. A connection to
an external network is not necessary for communication between
utelnetd and telnet client.
If the connected system is also connected to an external network, a
firewall can prevent
From: Greg Wooledge
Date: Sun, 10 Nov 2024 15:23:38 -0500
> ... inetutils-telnetd which should work out of the box.
Of course. Used for years and working now.
From: Greg Wooledge
Date: Sun, 10 Nov 2024 13:41:11 -0500
> Now, I have absolutely no idea what this "ute
>> SSHD is packaged and available on Debian.
> Timothy, for a console on localhost do you use ssh exclusively? Never
> xterm or similar? You authenticate every connection to localhost?
Hmm...`xterm` is unrelated: you'd run `telnet` or `ssh` *inside*
`xterm`, no *instead of* `xterm`.
> Naively,
Hi,
On Fri, Nov 15, 2024 at 11:11:49AM -0700, pe...@easthope.ca wrote:
> Exactly what I meant with "Naively, I wouldn't expect TLS to be
> necessary for localhost.
This utelnetd is also not necessary for localhost. And if telnet was
actually a requirement, I'm fairly confi
On Fri, Nov 15, 2024 at 2:27 PM wrote:
> From: Stefan Monnier
> Date: Fri, 15 Nov 2024 12:45:14 -0500
> > Hmm...`xterm` is unrelated: you'd run `telnet` or `ssh` *inside*
> > `xterm`, no *instead of* `xterm`.
>
> OK, I understand that. If X11 is running you use xterm or similar. If
> X1
From: Stefan Monnier
Date: Fri, 15 Nov 2024 12:45:14 -0500
> Hmm...`xterm` is unrelated: you'd run `telnet` or `ssh` *inside*
> `xterm`, no *instead of* `xterm`.
OK, I understand that. If X11 is running you use xterm or similar. If
X11 is not running you can do "ssh localhost" on the c
pe...@easthope.ca wrote:
> Extremely long References header shortened. =8~/
>
> From: Timothy M Butterworth
> Date: Thu, 14 Nov 2024 14:21:20 -0500
> > SSHD is packaged and available on Debian.
>
> Timothy, for a console on localhost do you use ssh exclusively?
> Never xterm or simila
Extremely long References header shortened. =8~/
From: Timothy M Butterworth
Date: Thu, 14 Nov 2024 14:21:20 -0500
> SSHD is packaged and available on Debian.
Timothy, for a console on localhost do you use ssh exclusively? Never
xterm or similar? You authenticate every connection to
of install
> but
> TLDP helps.
> https://tldp.org/HOWTO/Software-Building-HOWTO-3.html
> https://tldp.org/LDP/LG/current/smith.html
> etc.
>
> > Now, I have absolutely no idea what this "utelnetd" does, ...
>
> Found it about a week ago.
> https://wiki.g
tldp.org/LDP/LG/current/smith.html
etc.
> Now, I have absolutely no idea what this "utelnetd" does, ...
Found it about a week ago.
https://wiki.gentoo.org/wiki/Utelnetd
https://boxmatrix.info/wiki/Property:utelnetd
https://public.pengutronix.de/software/utelnetd/
https://sourceforge.net/
On Sun, 10 Nov 2024 20:31:53 +
Andy Smith wrote:
Hello Andy,
>Just struggling to find the point of utelnetd existing I suppose.
The included readme says it's a minimalist telnetd to be run, mostly,
on embedded systems.
As has been pointed out, it's quite old (2008). Further
On Sun, Nov 10, 2024 at 03:23:38PM -0500, Greg Wooledge wrote:
> On Sun, Nov 10, 2024 at 20:15:44 +, Andy Smith wrote:
> > There is also a telnetd packaged in Debian but I think that one needs to
> > be run under an inetd so you'd have to install one of those as well.
>
> Fortunately, the inet
mean running an inetd as well.
Just struggling to find the point of utelnetd existing I suppose.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
On Sun, Nov 10, 2024 at 20:15:44 +, Andy Smith wrote:
> There is also a telnetd packaged in Debian but I think that one needs to
> be run under an inetd so you'd have to install one of those as well.
Fortunately, the inetutils-telnetd package in Debian depends on
inetutils-inetd | inet-superse
On Sat, Nov 09, 2024 at 07:02:12PM -0700, pe...@easthope.ca wrote:
Hi,
> Retrieved utelnetd 0.1.11 from here.
> https://public.pengutronix.de/software/utelnetd/
This is really old software that you're trying to build from source and
while that should still be possible, it see
On Sun, Nov 10, 2024 at 10:08:47 -0700, pe...@easthope.ca wrote:
> From:
> Date: Sun, 10 Nov 2024 17:30:42 +0100
> > But perhaps Make is right and utelnetd is built and ready to go?
> >
> > What evidence would you have that it is not so?
>
> # ls -ld
From:
Date: Sun, 10 Nov 2024 17:30:42 +0100
> But perhaps Make is right and utelnetd is built and ready to go?
>
> What evidence would you have that it is not so?
# ls -ld /usr/local/bin/u*
ls: cannot access '/usr/local/bin/u*': No such file or directory
# cd /u
On Sun, Nov 10, 2024 at 10:08:47AM -0700, pe...@easthope.ca wrote:
> From:
> Date: Sun, 10 Nov 2024 17:30:42 +0100
> > But perhaps Make is right and utelnetd is built and ready to go?
> >
> > What evidence would you have that it is not so?
>
> # ls -ld
PROGS))" ahead of "all: $(PROGS)". That's
> what you intended, correct?
>
> Got this.
> # make DEBUG=1 -f ./Makefile
> PROGS: utelnetd
> make: Nothing to be done for 'all'.
That would mean that some "utelnetd" is there and is as young or
y
a $(info $(PROGS)) before the 'all' recipe to see:
>
> $(info PROGS: $(PROGS))
> all: $(PROGS)
Inserted line "$(info PROGS: $(PROGS))" ahead of "all: $(PROGS)". That's
what you intended, correct?
Got this.
# make DEBUG=1 -f ./Makefile
PROG
On Sat, Nov 09, 2024 at 10:39:32PM -0500, Jeffrey Walton wrote:
> On Sat, Nov 9, 2024 at 10:18 PM wrote:
> >
> > Retrieved utelnetd 0.1.11 from here.
> > https://public.pengutronix.de/software/utelnetd/
> >
> > Installed gcc and tried make.
> > # make DEBUG=
On Sat, Nov 9, 2024 at 10:18 PM wrote:
>
> Retrieved utelnetd 0.1.11 from here.
> https://public.pengutronix.de/software/utelnetd/
>
> Installed gcc and tried make.
> # make DEBUG=1 -f ./Makefile
> make: Nothing to be done for 'all'.
> #
>
> This is the &q
Retrieved utelnetd 0.1.11 from here.
https://public.pengutronix.de/software/utelnetd/
Installed gcc and tried make.
# make DEBUG=1 -f ./Makefile
make: Nothing to be done for 'all'.
#
This is the "all" stanza in Makefile.
all: $(PROGS)
$(PROGS): $(OBJS)
$(CC)
27 matches
Mail list logo
