From: Thomas Fischbacher <Thomas.Fischbacher@Physik.Uni-Muenchen.DE>
To: Yamagata Yoriyuki <yoriyuki@mbg.ocn.ne.jp>
Cc: oiwa@yl.is.s.u-tokyo.ac.jp, caml-list@inria.fr
Subject: Re: [Caml-list] How to secure an OCaml server
Date: Sun, 29 Feb 2004 00:49:40 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0402290044320.7058@seekar.cip.physik.uni-muenchen.de> (raw)
In-Reply-To: <20040229.081651.39150923.yoriyuki@mbg.ocn.ne.jp>
On Sun, 29 Feb 2004, Yamagata Yoriyuki wrote:
> From: Yutaka OIWA <oiwa@yl.is.s.u-tokyo.ac.jp>
> Subject: Re: [Caml-list] How to secure an OCaml server
> Date: Sun, 29 Feb 2004 01:44:10 +0900
>
> > The garbage collection helps this style of programming, since with
> > GC you can use those high-level data structures without fearing
> > about memory leakage or dangling pointers.
>
> On the other hand, relaying GC means data reside in the memory for
> unpredictable amount of time, and may swap out to the disk.
In case we are talking about linux, may I recommend using cryptoapi to
encrypt the swapspace (you can do a losetup -e blowfish /dev/loop7
swapfile; mkswap /dev/loop7; swapon /dev/loop7 at every boot - getting
losetup to use a random string may perhaps need a bit of patching...)?
What is swap good for nowadays that machines have RAM close to the 4 GB
boundary anyway? I suppose it is mostly used just to slow the machine down
enough so that root can react and kill processes by hand if some task
goes haywire. Hence, encrypting swap will even help to slightly improve
this. ;->
--
regards, tf@cip.physik.uni-muenchen.de (o_
Thomas Fischbacher - http://www.cip.physik.uni-muenchen.de/~tf //\
(lambda (n) ((lambda (p q r) (p p q r)) (lambda (g x y) V_/_
(if (= x 0) y (g g (- x 1) (* x y)))) n 1)) (Debian GNU)
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2004-02-28 23:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 15:10 David MENTRE
2004-02-28 16:37 ` David MENTRE
2004-02-28 16:44 ` Yutaka OIWA
2004-02-28 16:54 ` Richard Jones
2004-02-28 17:06 ` Thomas Fischbacher
2004-02-28 19:29 ` Richard Jones
2004-02-28 19:41 ` David MENTRE
2004-02-28 20:20 ` Richard Jones
2004-02-28 20:28 ` Thomas Fischbacher
2004-02-28 20:29 ` Richard Jones
2004-02-28 20:38 ` Thomas Fischbacher
2004-02-28 20:24 ` Thomas Fischbacher
2004-02-28 21:04 ` David MENTRE
2004-02-28 23:16 ` Yamagata Yoriyuki
2004-02-28 23:49 ` Thomas Fischbacher [this message]
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=Pine.LNX.4.58.0402290044320.7058@seekar.cip.physik.uni-muenchen.de \
--to=thomas.fischbacher@physik.uni-muenchen.de \
--cc=caml-list@inria.fr \
--cc=oiwa@yl.is.s.u-tokyo.ac.jp \
--cc=yoriyuki@mbg.ocn.ne.jp \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).