| 1 |
Am 20.05.2010 12:25, schrieb Stefan G. Weichinger: |
| 2 |
> Am 19.05.2010 00:23, schrieb Jan Engelhardt: |
| 3 |
> |
| 4 |
>> OK, but don't stop there. pam_mount really just ultimatively runs |
| 5 |
>> mount.crypt; and it tells you that it does by means of syslog (with |
| 6 |
>> enabled debug=1 of course). |
| 7 |
>> |
| 8 |
>> command: 'mount.crypt' '-ofsk.... |
| 9 |
> |
| 10 |
> Sorry, I don't see that in my logs (yep, debug=1). |
| 11 |
|
| 12 |
debug=2 didn't show anything new, btw. |
| 13 |
|
| 14 |
-- |
| 15 |
|
| 16 |
Trying pmt-ehd for a change: |
| 17 |
|
| 18 |
# pmt-ehd -f /dev/VG01/sgwcrypt -p /etc/security/sgwcrypt.enc -h md5 -D |
| 19 |
-s 25000 |
| 20 |
|
| 21 |
Creating a new container at /dev/VG01/sgwcrypt |
| 22 |
/dev/VG01/sgwcrypt is a symlink and points to ../dm-2 |
| 23 |
Do you really want to overwrite /dev/VG01/sgwcrypt? (y/n) |
| 24 |
y |
| 25 |
Writing random data to container |
| 26 |
Password: |
| 27 |
Reenter password: |
| 28 |
Using openssl cipher "aes-256-cbc" and hash "md5" |
| 29 |
ehd(crypto-dmc.c:144): Using _dev_VG01_sgwcrypt as dmdevice name |
| 30 |
crypt_activate: No such file or directory |
| 31 |
|
| 32 |
Oh my ... |
Archives