|Vincent Poy||Jul 30, 1997 7:07 am|
|Shashi Joshi||Jul 30, 1997 7:50 am|
|Satya Palani||Jul 30, 1997 9:44 am|
|Adam Shostack||Jul 30, 1997 11:59 am|
|Guy Helmer||Jul 30, 1997 2:22 pm|
|Frank Seltzer||Jul 30, 1997 3:11 pm|
|Pedro A M Vazquez||Jul 30, 1997 3:54 pm|
|Jordan K. Hubbard||Jul 30, 1997 4:06 pm|
|Guy Helmer||Jul 30, 1997 6:54 pm|
|Marc Slemko||Jul 31, 1997 10:59 am|
|Philippe Regnauld||Jul 31, 1997 1:14 pm|
|Dave Hummel||Aug 1, 1997 9:46 am|
|Subject:||Re: So, lets have a checklist compiled (was Re: Security hole)|
|From:||Vincent Poy (vin...@mail.MCESTATE.COM)|
|Date:||Jul 30, 1997 7:07:43 am|
On Wed, 30 Jul 1997, Shashi Joshi wrote:
=)As Marco Molteni said -> =) =)> Do you think one can be a newcomer as an administrator, but _has_ to know =)> everything about security before he starts to work? Come on! =) =) =)Exactly my thoughts. So, do we get a checklist or reference list from the =)gurus? =) =)I am also a bit new to the sys admin duties. I have =)taken the time to read the FreeBSD book that came with the CD (which =)doesn't help much in the security area), read a UNIX sysadmin book (Nemeth, =)Snyder etc the Red Book) but it too has its limitations.
I wish I had access to the FreeBSD book since I've been looking for one at different places in the Bay Area and they didn't have anything but the CD itself.
=)We don't have external user logins, so the risks are much less, but I would =)always like to learn because soon we will be "out there".
I'm sure that in the future, people will find all sorts of ways to break in to systems not via user logins but via ports or daemons.
=)Another netter mentioned about FreeBSD should ship with some documentation, =)scripts that tell us (about the system files and directories) what are the =)files associated with "feature" A or "service" B (e.g. uucp), which files =)need to be setuid for what functionality. =) =)Here is an example. (I know you gurus will laugh, but it was my 3rd day =)only). =) =)Realizing that sbin dirs are for sysadmin related files, I made the */sbin =)as -r-xr-x--- and group being wheel or bin as appropriate. =)Now, after a few weeks!! I realised that I am not able to send out any =)mail. I had been receiving mail like anything, my elm session also didn't =)complain when I sent out email. Finally I checked the logs and found =)nothing, not a trace of a mail sent out. So I checked to see `which =)sendmail` and it was /usr/sbin/sendmail =)So I had to give r-x permissions to it to the world. =) =)Now why would sendmail be in sbin when it is not purely a sysadmin tool =)only?
Good question but sendmail is a daemon that only root or the system should run I guess.
=)My point? Having a document or a checklist would be real helpful to newbies =)and can serve as a quick reference for the gurus.
Good point indeed.
I had been thinking about this hack, would it have been possible for the hacker to have ran perl.003 and then snatched the master.passwd file and then cracked it? Also, about the crc check, isn't the /etc/daily script supposed to compare files and do a security check already? Another point I want to make is that for one reason or another, 18.104.22.168R and previous versions were more strict on the password than 2.1R and 2.2.2R is. I have verified this with freshly installed boxes.
On a 22.214.171.124R and older box, if you tried to su and the root password was 1234567890, you had to enter it as 1234567890 or else it won't work and say Sorry!
On 2.1R, 2.2.2R and -CURRENT, I can enter 1234567890, 1234567891, 1234567892, etc. and it will still give me root access.
Cheers, Vince - vin...@MCESTATE.COM - vin...@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____]