|[tm-dev] TM considers retiring the RSE Telnet Subsystem|
As the TM committers reviewed the TM 3.4 Project Plan in today’s monthly meeting , we are considering to retire the Telnet RSE Subsystem.
The RSE Telnet Subsystem hasn’t seen any Community interaction or contribution in several years and quality is very low:
- login hangs infinitely when the remote doesn’t send the expected prompt characters, making the connect practically unusable (bug 194473 )
- Empty password is a problem (bug 251484 )
- Remote echo is typically not configured properly, leading to duplicate output/input (likely related to bug 259367 )
See also a query with Telnet List of Bugs .
Unless we get Community input that Telnet is needed, we’ll consider retiring Telnet in TM 3.4.
Please let us know whether the RSE Telnet subsystem is actively used anywhere, and consider contributing to the component in that case.
Note that even if we retire Telnet as an RSE Subsystem, the Terminal Telnet connector would remain (and adopters could use last year's Telnet subsystems on this year's TM since API for subsystems hasn't changed).
Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River
direct +43.662.457915.85 fax +43.662.457915.6