[TUHS] History of chown semantics
cowan at mercury.ccil.org
Tue Jan 14 02:15:06 AEST 2014
Tim Bradshaw scripsit:
> For instance imagine I want to pass some customer data to which I have
> access to you, who con't have access, for purposes of malice.
Download the file and mail it to me via anonymous remailer. Failing
that, use your cell and take snapshots of the screen. Failing that,
write down the data with pen and ink and send it by snail mail.
If I own a file, I can always get the contents to you one way or another.
Blocking chown doesn't help.
Let's face it: software is crap. Feature-laden and bloated, written under
tremendous time-pressure, often by incapable coders, using dangerous
languages and inadequate tools, trying to connect to heaps of broken or
obsolete protocols, implemented equally insufficiently, running on
unpredictable hardware -- we are all more than used to brokenness.
More information about the TUHS