Re: Re: Re: Security Uploading Files

In regards to checking the amount of disk space left, you may want to partition your hard drive so that files are uploaded on a separate partition. Then, even if someone manages to try to upload a terabyte of data from /dev/urandom, all that gets filled will be your partition, and your computer should still be able to operate.

Want to support the EFF and FSF by buying cool stuff? Click here.

Comment on Re: Re: Re: Security Uploading Files

Replies are listed 'Best First'.
Re: Re: Re: Re: Security Uploading Files by beth (Scribe) on May 26, 2004 at 18:04 UTC
While you're doing that, mount the partition with noexec: noexec Do not allow execution of any binaries on the mounted file system. This option might be useful for a server that has file systems containing binaries for architectures other than its own. Also good for parititions that are writable by untrusted users. It was suggested to me recently that the whole web root should be on a noexec partition, with cgi's symlinked from /usr/lib (or, presumably, other trusted partitions). -- eval pack("H*", "7072696e74207061636b2822482a222c202236613631373036382229"); # japh or forkbomb? You decide!	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Security Uploading Files
by beth (Scribe) on May 26, 2004 at 18:04 UTC

              noexec Do not allow execution of  any  binaries  on
                     the  mounted file system.  This option might
                     be useful for a server that has file systems
                     containing  binaries for architectures other
                     than its own.

--
eval pack("H*", "7072696e74207061636b2822482a222c202236613631373036382229");
# japh or forkbomb? You decide!

[reply]