× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: misc security holes
  • From: "Leif Svalgaard" <leif@xxxxxxxx>
  • Date: Thu, 8 Jun 2000 15:34:13 -0500

> As we're finding and publishing these chasms....are there any known ways
> to block the problems on our machines now, short of waiting until 5.1, 6.1
> or X.1 to address the problems?
> 
> Basically, what I'm getting at is, folks are presenting problems...are
> there any solutions that can be found within the great minds that I know
> are on this list...?
> 

Steve Glanstein suggested to me that the password sniffer exposed
by Gene Gaunt be augmented with a little twist: if the user ID found
is that of the user running the sniffer, then blank out the user ID and
password in the buffer. Include this little program as one of your start-
up programs, and you have decreased the chance that someone
can sniff your password.

Both Steve and I have actually written such a program. It is possible
to run this at SECLVL 40 (it is in user state). A system-state version
would run under 50.







+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.