All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: james@spunkysoftware.com
Cc: selinux@tycho.nsa.gov
Subject: Re: No RAM swapout to disk for "sandbox" run programs
Date: Tue, 28 Aug 2001 09:25:32 +0200	[thread overview]
Message-ID: <20010828092532.A10338@lemuria.org> (raw)
In-Reply-To: <005201c12f50$c8891240$b9fe3c3f@spunky>; from james@spunkysoftware.com on Tue, Aug 28, 2001 at 09:34:10AM +1000

On Tue, Aug 28, 2001 at 09:34:10AM +1000, james@spunkysoftware.com wrote:
> I have written Linus Torvalds talking about a range of PIDs, or a new field
> in the task_struct, which would indicate to the mm in the kernel that
> swapping this process' address space out to disk was forbidden.

this strikes me as redundant because such a mechanism already exists.

> programs, since PGP on WinNT at least was already doing it. I'm not sure how
> GnuPG handles this at the moment.

GPG will use existing system calls to achieve exactly this effect. I
don't know the details by heart, but I did once. grab the gpg source
and take a look around.


> Also, I am wondering where I can get software that will allow me to look at
> arbitrary memory ranges, the purpose being to look at "deleted" files on
> Windows and Linux. Anybody know of any such software? Is there a kernel
> module that allows this?

/proc/mem is your friend. :)



--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2001-08-28  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 23:34 No RAM swapout to disk for "sandbox" run programs james
2001-08-28  7:25 ` Tom [this message]
2001-08-28 11:40 ` Stephen Smalley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010828092532.A10338@lemuria.org \
    --to=tom@lemuria.org \
    --cc=james@spunkysoftware.com \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.