On Thu, Sep 28, 2000 at 06:52:47AM -0400, Ben Logan wrote:
| No matter how many times a change that file, it always ends up back
| like it was originally.
1: Stupid question: you _do_ have write permission when you edit it, yes?
2: More likely, it is being rewritten by some network start.
For example, some DHCP setups will rewrite resolv.conf.
Could this be the case?
Test: take careful not of size and modification time after edit,
startup ppp, check, etc.
Just guessing of course,
--
Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/
A workable solution might be to only trust hosts on the same physical
network, and modify gateways to reject packets that claim to, but do
not in fact, come from directly connected networks.
- from a 1985 paper by Robert Morris Snr entitled "A Weakness in the
4.2BSD Unix TCP/IP Software" in which he details TCP source spoofing,
10 years before IP spoofing became popular and 10 years before this
simple measure was widely implemented
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
