Re: Some Followup on that ypchfn mess of mine
From: Jon Loeliger (jdl@jdl.com)
Date: 07/27/01
- Next message: Kris Kennaway: "Re: Mistake in security advisory."
- Previous message: Kris Kennaway: "Re: some new exploit is out"
- In reply to: Anthony Schneider: "Re: Some Followup on that ypchfn mess of mine"
- Next in thread: Jon Loeliger: "Re: Some Followup on that ypchfn mess of mine"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: Anthony Schneider <aschneid@mail.slc.edu> Date: Thu, 26 Jul 2001 19:25:56 -0500 From: Jon Loeliger <jdl@jdl.com>
So, like Anthony Schneider was saying to me just the other day:
> Type ls -lo /path/to/ypchfn, and look for flags set on it
> (i.e. schg, uchg). If any of these are set, you will
> need to run
> chflags noschg ypchfn
> (or switch noschg with whatever flag is set).
> Not sure what else it might be.
> -Anthony.
>
So cleverly, I did this and it didn't work.
Then I got to thinking...
# sysctl kern.securelevel
kern.securelevel: 1
Uh oh. Hack rc.conf, back down to -1...
# chflags noschg ypchfn
And finally.
# chmod -x ypchfn
Woo hoo!
OK, so I feel a bit better now... :-)
Thanks!
jdl
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- Next message: Kris Kennaway: "Re: Mistake in security advisory."
- Previous message: Kris Kennaway: "Re: some new exploit is out"
- In reply to: Anthony Schneider: "Re: Some Followup on that ypchfn mess of mine"
- Next in thread: Jon Loeliger: "Re: Some Followup on that ypchfn mess of mine"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]