07.04.2011 13:06, Ed Schouten wrote: > Package: busybox > Version: 1:1.10.2-2 > Severity: normal > > > First of all, I'm running reportbug on a different box, but this bug is > related to the latest squeeze packages.
For that you can just modify version information in the bugreport to match reality. But ok. > The busybox-static package has a telnetd, but cannot work standalone. > This isn't a problem normally, since you can just use inetd for that. > Unfortunately, it doesn't come with inetd. So it's about busybox-static, not busybox. Ok. > Please enable the standalone telnetd by default. What are you using busybox-static for? I asked for a usage scenarious a while back in order to understand what exactly needs to be enabled (enabling "everything" is not an option), but got basically no replies. I was about to _drop_ busybox-static entirely, because I don't really see it's usage. So if you've a good usage case for it please speak up now :) And yes, what you observed makes sense, it's illogical at least. Maybe it's better to actually _drop_ telnetd instead of fixing it. We have netcat (nc) - you can run it something like this: nc -l -p 23 -e login which should be quite close to telnetd... :) Thanks! /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
