Date: Thu, 18 Mar 1999 11:53:54 -0600 (CST) From: James Wyatt <jwyatt@RWSystems.net> To: Robert Watson <robert+freebsd@cyrus.watson.org> Cc: Andrew McNaughton <andrew@squiz.co.nz>, "Daniel C. Sobral" <dcs@newsguy.com>, Dmitry Valdov <dv@dv.ru>, freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding Message-ID: <Pine.BSF.4.05.9903181005370.29893-100000@kasie.rwsystems.net> In-Reply-To: <Pine.BSF.3.96.990318092103.298B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 18 Mar 1999, Robert Watson wrote: > The linking behavior in conjunction with quotas makes a lot of sense: if a > user wants to consume someone else's quota, she just hard links to their > files so they cannot delete them. And if she are mean, she links to them > in private directories so the victim cannot find the links. Even if the > user truncates the file, the inode is still consumed in their name. User's manager: Why can't you read your mail or write code? Now, *why* was your unix account blocked? Why did you do *that*? After I make systems fairly secure, I do not hesistate to warn users if they interfere with others. I raraly hesistate in cutting accounts off after warnings. I warn for things like filling /tmp when you vi a 100M application dumo file. I block for things like demonstrably(sp?) injuring others. As I usually log info (ls of dir, clip log msgs, etc...), I usually get cooperation from management. It has also assisted them in gathering enough records to remove such folks from the payroll - they are usually problem folks in other areas as well. Fix social problems with social tools - Jy@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9903181005370.29893-100000>