| 1 |
Am 06.05.2010 18:24, schrieb Daniel Troeder: |
| 2 |
> On 05/05/2010 10:23 PM, Stefan G. Weichinger wrote: |
| 3 |
>> Am 05.05.2010 22:17, schrieb Stefan G. Weichinger: |
| 4 |
>> |
| 5 |
>>> Remember that I said: "I am not sure which HOWTO I followed" ? |
| 6 |
>>> |
| 7 |
>>> What if I didn't use aes-256-ecb? |
| 8 |
> You don't need to supplay that information to cryptsetup, it can |
| 9 |
> (should) autodetect it. To see that info for yourself run: |
| 10 |
> $ cryptsetup luksDump /dev/mapper/VG01-crypthome |
| 11 |
|
| 12 |
But I always did when I followed your example. |
| 13 |
Anyway, this part is solved now. |
| 14 |
|
| 15 |
>> Yep. See pam_mount.conf.xml: |
| 16 |
>> It's "aes-256-cbc" in my case. |
| 17 |
>> |
| 18 |
>> I was now able to luksOpen and I have the decrypted device mounted. |
| 19 |
> Hooray :) |
| 20 |
|
| 21 |
Yes :-) |
| 22 |
|
| 23 |
Currently I run an unencrypted home on another LV. |
| 24 |
|
| 25 |
>> Nice. |
| 26 |
>> |
| 27 |
>> So: |
| 28 |
>> |
| 29 |
>> the user-pw didn't change and the keyfile is OK. |
| 30 |
>> |
| 31 |
>> So why is pam_mount unable to mount it? |
| 32 |
>> |
| 33 |
>> I will now pull another backup and check/add fallback keys ;-) |
| 34 |
> There are interesting options in the cryptsetup-man page: |
| 35 |
> luksHeaderBackup and luksHeaderRestore... I think I'll add that to my |
| 36 |
> backup scripts :) |
| 37 |
|
| 38 |
Good idea. |
| 39 |
|
| 40 |
The main question is still unanswered: Why does pam_mount not work |
| 41 |
anymore with the given device/key ? |
| 42 |
|
| 43 |
Should I file a bug? |
| 44 |
|
| 45 |
S |
Archives