Re: serious telnet bug; is it just me? (fwd)

Robert Hanson (roberth@cet.cet.com)
Sat, 9 Sep 1995 09:54:00 -0700 (PDT)

id still like to see a posted "working" packet filter fix... i tried the
posted one and it didn't "appear" to work like i expected... i could
still telnet there from the other side of the cloud etc etc... anyone?

-rh

On Fri, 8 Sep 1995, Brian 'MegaZone' Bikowicz wrote:

> Once upon a time Chris B. Wilson, VectorNet shaped the electrons to say...
> >So livingston's technical support department is telling us "not to worry
> >about it"?.. What if this gets farther than this list, and I have the
> >tight competiton in town rebooting my terminal server.. don't worry about
>
> No, that is not what I said. I said I wouldn't/don't personally think of
> it as a bug, it is a console feature. But I also understand the worry, and
> I've already (as in the moment I reporodced it) sent the info up the tree to
> be worked on.
>
> 1. There is a workaround (which I would think anyone worried about security
> would have done already) - packet filtering.
> 2. In *very* brief testing it didn't reboot a unit running a new beta.
> 3. This 'bug' has been around nigh unto forever - how many reports have there
> been of PMs being reset willy-nilly with it?
>
> I'm a bit amused by the mad panic, like it needs to be fixed yesterday or
> the world will end. Calm down, breathe deep, relax - the odds are extremely
> low that someone will decide to exploit this out of the blue. We know about
> it, and it will be addressed.
>
> Life is to short to get too worried about something like this. It can be
> prevented already.
>
> -MZ
> --
> Livingston Enterprises Technical Support
> Phone: 800-458-9966 FAX: 510-426-8951
> support@livingston.com <http://www.livingston.com/>
> 6920 Koll Center Parkway #220, Pleasanton, CA 94566
>