Re: default file perms
b4f978d71d6dd8d4558632b5a185f28d 37760 root root 755 r/bin/ls (with type being 'r' for regular files, 'b', 'c', 'p', 'l' for (respectively) block and character devices, pipes, links). It might be worth adding a type for control files, to make it easier to spot the difference between a corrupt binary, and a file that has been edited by the sysadmin. Cheers, Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: default file perms
In message [EMAIL PROTECTED] you write: |--==_Exmh_263623679P |Content-Type: text/plain; charset=us-ascii | | |dpkg-cert already does something like this. Klee is going to fold the |capabilities of dpkg-cert into dpkg, so I think a solution is on |the horizon. :-) PLEASE PLEASE PLEASE! If you are allready at it - it would be nice to be able to find files which do NOT come from any package. This will make it much easier for the person in charge to find sniffer log files and binaries, and make it harder on the cracker to conceal them. Thanks, --Amos --Amos Shapira| Of course Australia was marked for 133 Shlomo Ben-Yosef st. | glory, for its people had been chosen Jerusalem 93 805 | by the finest judges in England. ISRAEL [EMAIL PROTECTED] | -- Anonymous -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: default file perms
In article [EMAIL PROTECTED], Amos Shapira [EMAIL PROTECTED] writes: PLEASE PLEASE PLEASE! If you are allready at it - it would be nice to be able to find files which do NOT come from any package. This will make it much easier for the person in charge to find sniffer log files and binaries, and make it harder on the cracker to conceal them. Less paranoid-ly, it will also be useful for people upgrading to debian from another distribution.
Re: default file perms
On Wed, 28 May 1997, Tim Sailer wrote: I have a client that just got carried away (as root of course) with a chmod -R in the wrong dir. I really miss the chkperms stuff deom $CO at times like this... so, I'm going to write one in perl. Since each package has a .list file already, would it be a big deal to have each developer to add a default file perm, and owner/group to each line, and have dpkg not have a problem with this? I rather think this is dpkg's job. _(; We could (easily?) convert the .list files to a format looking like this (for each file): md5sum size owner group mode type filename b4f978d71d6dd8d4558632b5a185f28d 37760 root root 755 r/bin/ls (with type being 'r' for regular files, 'b', 'c', 'p', 'l' for (respectively) block and character devices, pipes, links). This is just an example, but I think this is all the info we need, and it could easily be done by dpkg-deb while making the package. Klee? Ian? Cordialement, -- - ** Linux ** +---+ ** WAW ** - - [EMAIL PROTECTED] | RENARDIAS Vincent | [EMAIL PROTECTED] - - Debian/GNU Linux +---+ http://www.waw.com/ - - http://www.debian.org/ |WAW (33) 4 91 81 21 45 - --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: default file perms
In your email to me, Vincent Renardias, you wrote: On Wed, 28 May 1997, Tim Sailer wrote: I have a client that just got carried away (as root of course) with a chmod -R in the wrong dir. I really miss the chkperms stuff deom $CO at times like this... so, I'm going to write one in perl. Since each package has a .list file already, would it be a big deal to have each developer to add a default file perm, and owner/group to each line, and have dpkg not have a problem with this? I rather think this is dpkg's job. _(; We could (easily?) convert the True, but what about a utility that would be able to fix mistakes, or just to check to make sure all the perms were correct and to report the wrong ones. Again, this is like tripwire, but tripwire doesn't fix anything (and currently doesn't work). .list files to a format looking like this (for each file): md5sum size owner group mode type filename b4f978d71d6dd8d4558632b5a185f28d 37760 root root 755 r/bin/ls (with type being 'r' for regular files, 'b', 'c', 'p', 'l' for (respectively) block and character devices, pipes, links). This is just an example, but I think this is all the info we need, and it could easily be done by dpkg-deb while making the package. This is almost what SCO has, without the file type and md5 (If I remember right.. it's been a few years) Tim -- (work) [EMAIL PROTECTED] / (home) [EMAIL PROTECTED] - http://www.buoy.com/~tps The quality of accurate observation is commonly called cynicism by those who have not got it. G.B. Shaw ** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: default file perms
dpkg-cert already does something like this. Klee is going to fold the capabilities of dpkg-cert into dpkg, so I think a solution is on the horizon. :-) We just have to wait patiently for Klee and his upcoming proposal to overhaul dpkg. Cheers, - Jim pgpD2sxtAmlaW.pgp Description: PGP signature
