Mike Williams <[EMAIL PROTECTED]> writes: > On Sunday 28 December 2003 03:34, Jason Wever wrote: >> I don't believe our intention or goal is to proactively protect the user >> from their own possible stupidity. Telnet is still rather viable for >> things (think terminal servers) and has many applications where security >> may not be a concern.
> Mostly, as an administrator/power user, telnet is an absolute must for testing > services. Although people often tend to use and think of telnet as being plain-text, bare TCP, it really is a protocol, and so it would probably be best to use the far-more-useful-for-that-purpose netcat program (net-analyzer/netcat). > The block-telnet with a virtual/telnet is a good idea. A simple 1 line reason > for the block printed when portage shows the block would make things even > better. > Yes, it's work for a dev, but if it saves a multitude of questions later isn't > it worth the effort now? Adding a block-telnet package to the system class seems like an excessive amount of trouble to inconvenience users excessively. -- Jeremy Maitin-Shepard -- [EMAIL PROTECTED] mailing list
