Classification: UNCLASSIFIED
Seems to hang when it can't find the kernel headers.
If you forget that they can come with the package for a moment and just install
them directly. If you've been away for some time you probably did not get the
memo that systems don't come with the headers or
Just thought it might be useful for someone else
in the future if I feed back the results of some
of my tests.
The first test is the set up of a dm-crypt based
loop back partition:
# Create a file for our little 30GB test disk
dd if=/dev/zero of=other.ext4 count=60M
#
Hey there Dale List,
I believe Ryan and Bill (CC'd) are using AES full disk crypto on their
systems. It seems complicated to me, but they can probably give you
tips. I think Bill is using Debian and Ryan is using Arch. Bill's
(DISA's) policies are pretty strict and probably require that his
On Wed, Mar 28, 2012 at 09:37:16AM -0700, C.J. Adams-Collier KF7BMP wrote:
| card be inserted at boot time. Ryan's history administering the
| intranet for a company in the medical field have set his bar probably
| higher than DISA's in many ways, but may not require that the physical
| token be
On Wed, Mar 28, 2012 at 12:03:22PM -0700, Ryan Corder wrote:
Full disk encryption with LUKS is actually pretty easy, and I do have the full
process written down. I've been looking for a reason to actually type it out
for later use...I'll do that later today and then send it on for reference.
On 03/28/2012 10:42 PM, Dale Amon wrote:
So does anyone have a suggestion as to where I have
gone wrong? It's been over half a decade since I've
gone through this and even longer since I was doing
the magic dance with patching and building my own
losetup, mount, etc...
If you want something
On Wed, Mar 28, 2012 at 11:14:41PM +0200, Milan Broz wrote:
If you want something simple, use LUKS. cryptsetup
and dmcrypt is in all distributions by default.
Truecrypt uses dmcrypt by default as backend as well.
Looking around a bit, it appears that cryptsetup is in
the ubuntu server set up
