[LEDE-DEV] [PATCH] busybox: re-enable telnet applet

[Philip Prindeville]

> On Feb 18, 2018, at 11:25 AM, Philip Prindeville <philipp_subx at redfish-solutions.com> wrote:
> 
> 
> 
>> On Feb 18, 2018, at 2:27 AM, John Crispin <john at phrozen.org> wrote:
>> 
>> 
>> 
>>> On 20/06/17 19:13, Stefan Tomanek wrote:
>>> While sshd should be favoured over telnetd, having a telnet client on the
>>> router is useful for connecting to other devices in the same LAN.
>>> 
>>> Signed-off-by: Stefan Tomanek <stefan.tomanek at wertarbyte.de>
>> 
>> sorry for the late reply, it has been discussed over and over and the decision was made to not enable telnet by default. sorry ...
>> 
>>    John
> 
> Too bad.  While it’s a liability for logging in, it’s a great tool for testing remote services like HTTP, SMTP, IMAP, JetDirect printers, etc.


Although we should be honest about it: the problem isn’t the host with the telnet client; it’s the one with the telnet server.

-Philip


>>> ---
>>> package/utils/busybox/Config-defaults.in |    4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>> 
>>> diff --git a/package/utils/busybox/Config-defaults.in b/package/utils/busybox/Config-defaults.in
>>> index 1977e7f..9e0efcf 100644
>>> --- a/package/utils/busybox/Config-defaults.in
>>> +++ b/package/utils/busybox/Config-defaults.in
>>> @@ -2289,10 +2289,10 @@ config BUSYBOX_DEFAULT_TCPSVD
>>>     default n
>>> config BUSYBOX_DEFAULT_TELNET
>>>     bool
>>> -    default n
>>> +    default y
>>> config BUSYBOX_DEFAULT_FEATURE_TELNET_TTYPE
>>>     bool
>>> -    default n
>>> +    default y
>>> config BUSYBOX_DEFAULT_FEATURE_TELNET_AUTOLOGIN
>>>     bool
>>>     default n
>> 
>>