Re: How to allow root telnet to a NetBSD 6.1.5 box

* jmitchel (jmitc...@mail.bigjar.com) wrote: > Hello, > > I have an appliance that I'm upgrading from 1.6.2 (I know, I know) to 6.1.5. > The appliance currently only has the root account. I want users to be able > to set up the box without having to use a serial cable, so I'm configuring > it

Re: How to allow root telnet to a NetBSD 6.1.5 box

On Sun, Nov 8, 2015 at 2:23 PM, Thor Lancelot Simon wrote: > > That's irresponsible. I for one won't help you do it. Use SSH. Agreed. It's amazing how telnet still exists and even proliferates when it doesn't have to. Probably it should be requisite to explain why telnet is

Re: How to allow root telnet to a NetBSD 6.1.5 box

Andy Ruhl wrote: A guy I worked with a while back insisted on using it because Windows doesn't have a built in SSH client. Even after someone sniffed his password and showed him. Unbelievable. Wow is he living in the past. Windows doesn't have a telnet client either in recent versions and

RE: How to allow root telnet to a NetBSD 6.1.5 box

Mike Pumford (mpumf...@mudcovered.org.uk) writes... >Wow is he living in the past. Windows doesn't have a telnet client >either in recent versions and quite frankly I'd rather download PuTTY >anyway. ;) > > >Mike Actually, a telnet client is available in newer versions of Windows as a feature

Chatty drivers

Is there a sysctl or some such thing to make a particular driver less "chatty"? I have a twa card with a battery that needs replacing and it won't shut up about it. I'd like to turn off the messages for this driver until I can do maintenance and get the replacement in place. These are the

Re: How to allow root telnet to a NetBSD 6.1.5 box

Davis, Michael T. wrote: Actually, a telnet client is available in newer versions of Windows as a feature that can be enabled via the "Programs and Features" control panel. It is not enabled, by default. But I prefer PuTTY, as well. Well I've learnt something today :). Didn't realise that