<p>given that many attacks are launched from inside the network, it would be just blurring. all of this tries to patch a hole which will remain a hole, whatever plaster you use.</p>
<p>Given that the network we're talking about here is either a set of RIOT devices or the link between a RIOT device and the host computer it means that there is already vulnerability in RIOT to abuse or the (more capable) host computer is compromised. Either way, if the "inside network" is compromised you have worse things to worry about than a development telnet server.</p>
<p>I'm not claiming that this secures the telnet server, but it does prevent a large set of attacks against the telnet server and reduces the scope to local attackers only. It makes it easier to reason for a user whether the telnet server can be used for a simple test setup without issues.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/pull/16723#issuecomment-928999158">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABE7WYH33VXYS6YRFQ73ADTUEGALJANCNFSM5B44LPJQ">unsubscribe</a>.<br />Triage notifications on the go with GitHub Mobile for <a href="https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub">Android</a>.
<img src="https://github.com/notifications/beacon/ABE7WYAOELN3V366BIY4XVTUEGALJA5CNFSM5B44LPJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOG5PWN5Q.gif" height="1" width="1" alt="" /></p>
"name": "View Pull Request"
"description": "View this Pull Request on GitHub",