On 2009-08-10 18:49, line...@ruiner.halo.nu wrote:
[snip]
The root filesystem is encrypted to make it more difficult for a
local attacker to replace system binaries with backdoored
versions.
I don't think this is a valid reason for encrypting root.
--
Scooty Puff, Sr
The Doom-Bringer
--
To
On Tuesday 11 August 2009 17:41:48 line...@ruiner.halo.nu wrote:
> Ok I guess the system is just hosed. If no one has any more suggestions in
> the next couple days I will reinstall.
>
>
> I will never trust Debian upgrades again, at least not when encrypted
> filesystems are in use.
Well, all
Ok I guess the system is just hosed. If no one has any more suggestions in the
next couple days I will reinstall.
I will never trust Debian upgrades again, at least not when encrypted
filesystems are in use.
On Mon, Aug 10, 2009 at 06:49:51PM -0500, line...@ruiner.halo.nu wrote:
> > hmm
> hmmm not sure, you could try
> turning of quiet mode remove the quiet from the kernel option on boot
> and maybe try turning on debug (add debug to the kernal options)
There is no quiet mode in my kernel line. Adding the debug option didn't seem
to add any additional relevant information;
>
On Wednesday 05 August 2009 19:54:50 line...@ruiner.halo.nu wrote:
> I tried configuring fstab to use the UUID from blkid, but I had the same
> problem. Could the problem be that the SCSI drives are not coming up until
> cryptsetup has loaded?
Hi again lineman (and list).
Just for another da
On Thu, Aug 06, 2009 at 19:21 -0500, Manoj Srivastava wrote:
> On Thu, Aug 06 2009, Siggy Brentrup wrote:
>
> > On Tue, Aug 04, 2009 at 18:50 -0500, line...@halo.nu wrote:
> >> Hi -
> >
> >> I have a Debian Etch system which I recently upgraded to v5.0.2.
> >> The file system was encrypted with LU
On Thu, Aug 06, 2009 at 18:29 -0400, Andrew Reid wrote:
> On Thursday 06 August 2009 04:16:42 Siggy Brentrup wrote:
> > Please bear with me, I'm asking this out of curiousity. Why did you
> > encrypt the full root FS? I can understand that you want your $HOME
> > encrypted, to a lesser degree I c
On Thu, Aug 06 2009, Siggy Brentrup wrote:
> On Tue, Aug 04, 2009 at 18:50 -0500, line...@halo.nu wrote:
>> Hi -
>
>> I have a Debian Etch system which I recently upgraded to v5.0.2.
>> The file system was encrypted with LUKS at install time.
>
> Please bear with me, I'm asking this out of curious
On Thursday 06 August 2009 04:16:42 Siggy Brentrup wrote:
> On Tue, Aug 04, 2009 at 18:50 -0500, line...@halo.nu wrote:
> > Hi -
> >
> > I have a Debian Etch system which I recently upgraded to v5.0.2.
> > The file system was encrypted with LUKS at install time.
>
> Please bear with me, I'm asking
On Tue, Aug 04, 2009 at 18:50 -0500, line...@halo.nu wrote:
> Hi -
> I have a Debian Etch system which I recently upgraded to v5.0.2.
> The file system was encrypted with LUKS at install time.
Please bear with me, I'm asking this out of curiousity. Why did you
encrypt the full root FS? I can un
On Wednesday 05 August 2009 19:54:50 line...@ruiner.halo.nu wrote:
> I tried configuring fstab to use the UUID from blkid, but I had the same
> problem. Could the problem be that the SCSI drives are not coming up until
> cryptsetup has loaded?
This could happen if the new kernel's initramfs doe
On Wed, Aug 05, 2009 at 06:54:50PM -0500, line...@ruiner.halo.nu wrote:
> I tried configuring fstab to use the UUID from blkid, but I had the same
> problem. Could the problem be that the SCSI drives are not coming up until
> cryptsetup has loaded?
hmmm not sure, you could try
turning of quiet
I tried configuring fstab to use the UUID from blkid, but I had the same
problem. Could the problem be that the SCSI drives are not coming up until
cryptsetup has loaded?
Here is some info on my configuration:
t...@magnesium:/etc/initramfs-tools/conf.d$ cat resume
RESUME=/dev/mapper/magnesium
On Tue, Aug 04, 2009 at 06:50:56PM -0500, line...@halo.nu wrote:
> Hi -
>
> I have a Debian Etch system which I recently upgraded to v5.0.2. The file
> system was encrypted with LUKS at install time.
>
> The upgrade appeared to go well, however when I boot into the new system, it
> gives the f
Hi -
I have a Debian Etch system which I recently upgraded to v5.0.2. The file
system was encrypted with LUKS at install time.
The upgrade appeared to go well, however when I boot into the new system, it
gives the following error:
Volume group "hostname" not found
cryptsetup: Source device /d
15 matches
Mail list logo
