Re: PLiSS cryptofilesystem with SuSE 9.1?

• Previous message: Security Alert: "SSRT4773 rev.0 HP-UX xfs and stmkfont remote unauthorized access"
• In reply to: Stefan Weinzierl: "PLiSS cryptofilesystem with SuSE 9.1?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Tue, 27 Jul 2004 08:43:29 +0200

Hi,

I forgot the second point.

Stefan Weinzierl schrieb:
>
> *OLD* *NEW*
>
> loop loop=/dev/loop0
>
>
> *REMARK:* Apparently SuSE is now binding the particular cryptofilesystems
> statically to a specific loop-device, instead of dynamicly like before. So
> I've got some problems. Because e.g. /dev/loop0 is in my case always
> already occupied by that encrypted partition, on which my file-container
> for the home-directory is stored. If I don't mount that partition, I can't
> reach my homecontainer anyway. I simply changed the device-assignment. Then
> it works. Was that statical binding of loop-devices already possible in
> former times, or is that a new feature?PLiSS Cryptofilesystem mit SuSE 9.1?
> PLiSS Cryptofilesystem mit SuSE 9.1?

Did you unbind the encrypted container from the initial loop device
after making the filesystem on it? ("losetup -d /dev/loop[yourloopdev]")
Maybe that's why SuSE is trying (or doing :-) to assign automatically an
other loop dev or even the same loop dev to both the partitition and the
container.

Chris

• Previous message: Security Alert: "SSRT4773 rev.0 HP-UX xfs and stmkfont remote unauthorized access"
• In reply to: Stefan Weinzierl: "PLiSS cryptofilesystem with SuSE 9.1?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]