On Thu, 1 Jan 2004, Erik Andersen wrote: > Perhaps swapon should automagically do a chmod and chown on all > swapfiles, unless specifically asked to be wildly insecure (perhaps > with a -W option -- wildly insecure swapfile permissions are > considered acceptable).... There's no sane reason to have open swap files, so yes, above behaviour would be good. > -Erik regards, -- Paul Jakma paul _at_ clubi.ie paul _at_ jakma.org Key ID: 64A2FF6A warning: do not ever send email to spam _at_ dishone.st Fortune: A prisoner of war is a man who tries to kill you and fails, and then asks you not to kill him. -- Sir Winston Churchill, 1952 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- Re: chmod of active swap file blocksNeale Banks
- Re: chmod of active swap file blocksAndrew Morton
- Re: chmod of active swap file blocksAndries Brouwer
- Re: chmod of active swap file blocksErik Andersen
- Prev by Date: Re: udev and devfs - The final word
- Next by Date: Re: [CFT/PATCH] give sound/oss/trident a holiday cleanup for 2.6
- Previous by thread: Re: chmod of active swap file blocks
- Next by thread: Happy new year from texas
- Indexes:[Main][Thread]