Re: utelnetd

[peter@easthope.ca]

    From: Greg Wooledge <greg@wooledge.org>
    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 <greg@wooledge.org>
    Date: Sun, 10 Nov 2024 13:41:11 -0500
> Now, I have absolutely no idea what this "utelnetd" does, ...

Google utelnetd.
https://boxmatrix.info/wiki/Property:utelnetd
https://wiki.gentoo.org/wiki/Utelnetd
https://public.pengutronix.de/software/utelnetd/

A glance at boxmatrix reveals  "... ideal for use on embedded systems ... " 
and "AN INTERNET SUPERSERVER DAEMON IS NOT REQUIRED."

telnetd developed when multiple terminals connected to a time shared 
mainframe.  https://en.wikipedia.org/wiki/Telnet#Historical_uses

Yes in the present world a security hazard is possible.
https://en.wikipedia.org/wiki/Telnet#Security_vulnerabilities
 
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 illicit access.
https://en.wikipedia.org/wiki/Firewall

So server terminal access and embedded cases distinct.

My original question is restated here.
https://lists.debian.org/debian-gcc/2024/11/msg00059.html 
If I'm lucky, clarification will surface among the compiler people.

Regards,                    ... P.



-- 
VoIP:   +1 604 670 0140
work: https://en.wikibooks.org/wiki/User:PeterEasthope