Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: =?iso-8859-1?q?G=FCnther?= Schwarz <strap@gmx.de>
Newsgroups: comp.os.linux.security
Subject: Re: tmps and swap
Date: 9 Feb 2012 21:51:14 GMT
Lines: 15
Message-ID: <9piteiF61gU2@mid.individual.net>
References: <9pdh5dF5ksU1@mid.individual.net> <jgscf0$22d2$1@saria.nerim.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net fUs4jk4jg3VzYpgSAsDBWQsAcGoewllhRTqcFItHNi25xzfMNMPppWvtcH
Cancel-Lock: sha1:fuVwQnze4LBXqylxx3eFJadMppw=
User-Agent: Pan/0.132 (Waxed in Black)
Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.security:100

Pascal Hambourg wrote:

> Günther Schwarz a écrit :
>> Any hints on how to prevent a tmpfs file system to be written to the
>> swap partition? Other than omitting a swap partition completely, of
>> course. I do not want some files to end up on the hard disk.
> 
> You can use ramfs instead of tmpfs. But the drawback is that you cannot
> limit the size. See Documentation/filesystems/ramfs-rootfs-initramfs.txt

An interesting option also. But it might be too easy for an user to fill 
the memory completely. I will first try with an encrypted swap with a key 
form /dev/urandom as suggested by Stachu.

Günther