| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* All variables are now embraced: ${foo}
* All comparisons against some value now take the form:
[ "${foo}" ? "value" ]
where ? is a comparison operator
* All empty string tests now take the form:
[ -z "${foo}" ]
* All non-empty string tests now take the form:
[ -n "${foo}" ]
Submitted by: jkh
|
|
|
|
|
|
| |
PR: 9639
Reported by: Bob Willcox <bob@pmr.com>
Submitted by: des
|
|
|
|
|
| |
PR: 9424
Submitted by: Lars K*ller <root@cc.fh-lippe.de>
|
|
|
|
|
|
|
|
|
| |
to a hostname. This will help those who keep a cluster of machines all with
the same hostname but different domain names.
PR: bin/9091
Submitted By: Heikki Suonsivu <hsu@clinet.fi>
No Response From: -current mailing list
|
|
|
|
|
| |
PR: 7621
Submitted by: Mark Huizer
|
|
|
|
| |
Use awk -F: rather than 'BEGIN {FS=":"}'
|
|
|
|
|
|
|
|
| |
fail to detect 00.
PR: 7218
Submitted by: Michal Listos <mcl@Amnesiac.123.org>
Niall Smart <rotel@indigo.ie>
|
|
|
|
|
| |
- login failures
- tcp_wrapper messages about refused connections
|
| |
|
|
|
|
| |
or unreach.
|
|
|
|
| |
dmesg changes.
|
|
|
|
| |
The -g option to ls has been depreciated.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows find to pass files with "illegal" characters to xargs in a
safe manner.
Note: due to the manner in which the file names are now passed between
find and xargs, the files are now sorted differently than before.
The first /etc/security run after installing this change may result
in a lot of output when nothing did in fact change.
Closes PR# 1910.
2.2 candidate.
|
| |
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
|
|
|
| |
to freefall!)
|
|
|
|
| |
messages using the output of dmesg.
|
| |
|
|
|
|
|
|
| |
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.
|
|
|