| Age | Commit message (Collapse) | Author |
|
|
|
|
|
New sentence, new line.
|
|
it's not really "cheap".
|
|
|
|
standard. This change inspired by Apple's "Secure Empty Trash" functionality
in MacOS 10.3. However, it is important to understand that this change
does not -- and can not -- actually achieve conformance to the current
revision of the standard. To quote the manual page:
The -P option attempts to conform to U.S. DoD 5220-22.M, "National Indus-
trial Security Program Operating Manual" ("NISPOM") as updated by Change
2 and the July 23, 2003 "Clearing & Sanitization Matrix". However,
unlike earlier revisions of NISPOM, the 2003 matrix imposes requirements
which make it clear that the standard does not and can not apply to the
erasure of individual files, in particular requirements relating to spare
sector management for an entire magnetic disk. Because these
requirements are not met, the -P option does not conform to the standard.
This also makes the -P option a *lot* more expensive than it used to be.
It used to overwrite with 0xff, overwrite with 0x00, overwrite with 0xff,
with an fsync after each write. Now it overwrites with a random character,
overwrites with 0xff, overwrites with 0x00, reads to validate the 0x00
overwrite, then overwrites with random data -- calling sync() after every
operation in an attempt to force seeks that will clear the data from the
cache of disks that lie about whether data has been committed to the
platters. Also, the file's opened with O_SYNC|O_RSYNC to cause metadata
updates on every read/write, which should cause still more seeks.
This is better than it used to be, but it's by no means adequate if you
have data you really don't want read by an adversary who can pull the
disk apart.
|
|
one from further down in the same page. Suggested by jmc@openbsd.
|
|
|
|
Calling stderror here is not safe, because we might have not setjmp()'ed
yet.
|
|
to be the most common practice in our tree.
|
|
|
|
(like executing "pax -Z" by itself), this caused a shr of 32 bits, which is
undefined behavior (C99) if the variable is 32 bits wide, too. Also solves
a problem where the flgch array could be indexed out of bounds.
Thanks to uwe@ and lha@ for their suggestions... I just found the bug :p
|
|
Ito in PR bin/23969 and PR bin/23970.
|
|
Noted by Jeff Ito in PR bin/23967.
|
|
Noted by Jeff Ito in PR bin/23966.
|
|
|
|
works.
XXX: ls -sh now always uses 4 chars for the size column width even if it
needs less than that.
|
|
|
|
from David P. Reese Jr. in PR bin/23870.
|
|
|
|
|
|
this adresses bin/23810 by VaX#n8
bump date and update copyright
|
|
nonintuitive evaluation in case there is both || and && specified
pointed out in bin/23814 by VaX#n8
|
|
change sent in bin/23813 by VaX#n8
|
|
|
|
seems to be an off-by-one error, since njobs is decremented before we use
it. I hope this does not break the vfork case!
|
|
Really: test commits on new cvs binary.
|
|
|
|
run out of inodes. df -i was saying, however, that such file systems
had 100% of their inodes in use, which would do things like trigger
alarms in scripts looking for file systems that have run out.
Instead, say 0% are in use, which although not strictly true is at
least less wrong, fixes scripts and is less worrying in nightly reports.
|
|
|
|
|
|
Sort options.
|
|
systrace UI to be attached and re-attached, it also multiplexes across
systrace process so that one UI can function as central notification
|
|
All the code has been present for a while, and the memory cost is (about)
180 bytes per process.
Fixes PR bin/23545
|
|
Compile problems noticed by Dan Carosone.
|
|
really tar format. valid CPIO files should not trigger a warning from tar.c
|
|
Small.
|
|
in September. Pointed out by Mike Small in a private email.
|
|
|
|
|
|
for us, rather than iterating until satisfied.
Suggested by David Laight.
|
|
outputting to the files being manipulated by opening a file in the standard IO
descriptor space. In particular, an output file unlucky enough to be sitting
on descriptor 2 (stderr) is certain to be corrupted.
Addresses PR bin/8521, and passes the recently committed regression test
"bin/dd".
|
|
subsequent 'pwd -L' will report the same value.
Update man page to be a closer match to reality.
|
|
|
|
|
|
when describing the file system.
|
|
- Make 'pwd -L' fall back to 'pwd -P' if PWD is incorrect.
- Ignore PWD if it contains "/./" or "/../".
- Garbage collect some redundant code.
It is still non-conformant because posix mandates that the default
be 'pwd -L' (aka ksh), not 'pwd -P' (historic practise everywhere else).
Changing the default will break too much...
|
|
Note that 'pwd -L' and 'pwd -P' almost always report the same answer as
the shell detects when 'cd' follows a symlink and discards its cached 'pwd'
|
|
|
|
Noted by Igor Sobrado in PR 23278, fixed following a suggestion by Greg A. Woods.
|