1 |
I submitted a patch to device-mapper-1.00.07 that makes dmsetup lock its |
2 |
pages. This should prevent swaps between 'hashalot | dmsetup', so with |
3 |
a few changes to the dm-crypt init script, people should be able to |
4 |
encrypt their block devices leaving swap unencrypted, and not have to |
5 |
worry about their key leaking to swap. checkout the following if |
6 |
interested. |
7 |
|
8 |
http://bugs.gentoo.org/show_bug.cgi?id=43162 |
9 |
|
10 |
Justin |
11 |
|
12 |
On Fri, 2004-02-27 at 19:27 -0500, Justin Whitney wrote: |
13 |
|
14 |
> http://bugs.gentoo.org/show_bug.cgi?id=43146 |
15 |
> |
16 |
> any help getting it load before localmount especially appreciated, as |
17 |
> it's much less useful till then. i've tried all sorts of things, on two |
18 |
> boxes neither crypto-loop or dm-crypt will load right. |
19 |
> |
20 |
> Justin |
21 |
> |
22 |
> On Fri, 2004-02-27 at 14:24 -0500, Mike Frysinger wrote: |
23 |
> |
24 |
> > On Friday 27 February 2004 03:55 am, Justin Whitney wrote: |
25 |
> > > I've written a dm-crypt ebuild and initscript that does the same thing |
26 |
> > > crypto-loop does, but using the device mapper. |
27 |
> > |
28 |
> > the sooner we get it into the portage the sooner we can test it and the sooner |
29 |
> > we can tramsition off of crypto-loop ;) |
30 |
> > hell, it'll be nice if only so we dont have to constantly worry about |
31 |
> > util-linux updates breaking everyone |
32 |
> > -mike |
33 |
> |
34 |
> |
35 |
> -- |
36 |
> gentoo-dev@g.o mailing list |
37 |
|
38 |
|
39 |
-- |
40 |
gentoo-dev@g.o mailing list |