| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
that have changed since the last security check.
Make the spacing between sections more consistent.
|
|
|
|
|
|
|
| |
the /etc/security setuid checks. This is useful for things like large
news spool partitions that dont have executables.
Reviewed by: pst
|
|
|
|
| |
guessing involves too much AI.
|
|
|
|
|
|
| |
Check devices too, follow original BSD intention
Find only executable files with s-bits, close PR bin/1022
Reset locale to C to have equal results in any case
|
|
|
|
| |
warning and make it, all following commands fails in old case
|
| |
|
|
|
|
| |
found SUID files, only SGID files. The find has missed some parantheses.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Subject: Re: daily insecurity output (fwd)
|From: rgrimes@agora.rain.com (Rodney Grimes)
|
|This is from the new /etc/security script. I no longer get the segmentation
|violation, but now the arg list is too long, some /bin/sh program want to
|fix the current /etc/security ls command so that it is a pipe insteal of
|a back quoted arg?
|
|> checking setuid files and devices:
|> /etc/security: ls: argument list too long
This uses xargs instead. My slip line's down so I can't check it in
at the moment. Rich
|
|
|
|
| |
directorty contents.
|
|
|
|
|
| |
only to run find on local file systems. It now works and no longer gets
the error from sort
|
|
|
|
| |
plus some tid bits from me.
|
|
|
|
|
| |
yet have the accounting stuff in it. Disabled ncheck search in security
due to missing ncheck.
|
|
|