Atom Smasher wrote:
On Fri, 10 Sep 2010, Ivan Voras wrote:
1) power outage of the server
2) power outage on the client
3) network problems (ssh or TCP connection drop)
4) administrative command (e.g. root executes "killall $shell")
?
I don't think there is a way to protect from all of those, so any
effort in protecting from only part of the problem looks useless.
========================
you forgot cosmic rays, nuclear war and zombie apocalypse, among other
failure modes. *NOTHING* is capable of protecting against everything;
a good solution will most always have pitfalls; as a
sysadmin/engineer/manager one has to either accept the pitfalls or
find a more acceptable solution, which usually means different
pitfalls. that doesn't mean a given solution is useless.
Bah.
since you mentioned .logout, i'm assuming you are using tcsh.
what i would suggest is that you create an md and check out the files
into that. this solves the power fail issue completely, also, it solves
the main issue. have the logout script simply umount and mdconfig -d
the ramdisk. also, this way, security is enhanced because no fragments,
even of deleted files, are left on disk after logout. the only question
i have is if a bzero is done before returning the ram to the os, if not,
simply dd if=/dev/zero of=/dev/md0 bs=whatever to be sure that the ram
formeerly contained in the ramdisk isn't readable by later procs.
have you considered trustedbsd? it should perform the bzero by
default. TBSD MAC is in fbsd these days to control access to the
mountpoint, but that might not help if you are worried about a lifted
disk, MAC don't mean shit without physical security, the kind involved
in the environments for which it was commissioned.
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
