It's too bad this little "feature" will pop up on rootshell.com someday,
since they LOVE finding backdoors into ISP's anyway they can get them.
You can say to your employees, "reset console before you quit!" till
you're blue in the face, but there are times it just doesn't happen. what
about WHILE THEY'RE DEBUGGING ? It's vulnerable then.
sure... "run comos3.8 or greater and use the Java app" is the response
from livingston, so they don't have to add 2 lines of code that will
"bloat" the server, but what about when ComOS releases SUCK so bad we
refuse to use them at all ?
Just have to vent. Livingston/Lucent starts to aggravate me more and more
everyday with stupid little shit like this.
On Wed, 8 Jul 1998, Stephen Zedalis wrote:
> So what you are saying is that ALL your release (non-beta) versions of
> ComOS have this bug and there is no resolution. And from the suggestion
> to use the Java tools even though they only work on an as of yet
> unreleased version of ComOS, there isn't going to be one either. And
> given all the focus on the PM-3 and its V.90/V.34 problems, its gonna be
> awhile til you see a resolution for the lowly PM-2's, etc. since they will
> get ComOS 3.8 after you get the PM-3s squared away as you guys have stated
> before. Man this makes the red LED issue seem insignificant. This ought
> to have a big Warning label in your Command Line Administrator's Guide,
> Troubleshooting Guide, etc.
>
> On Wed, 8 Jul 1998, D. Scott Gardner wrote:
>
> >Versions of the ComOS earlier than 3.8 do not have the necessary hooks
> >for our Java applications to perform either monitoring or debugging.
>
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
> Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>