| 1 |
On Tuesday 2010-05-18 21:33, Stefan G. Weichinger wrote: |
| 2 |
>Am 18.05.2010 20:57, schrieb Stefan G. Weichinger: |
| 3 |
> |
| 4 |
>> On the other hand I would like to get that done right, sure. |
| 5 |
>> |
| 6 |
>> Any howto without pmt-ehd that would keep me safe from newlines etc |
| 7 |
>> (btw. there were NO newlines in that hexdump-output)? |
| 8 |
> |
| 9 |
>Created a new encrypted LV and used "--key-file=-" as mentioned in: |
| 10 |
> |
| 11 |
>http://pam-mount.git.sourceforge.net/git/gitweb.cgi?p=pam-mount/pam-mount;a=blob;hb=master;f=doc/bugs.txt |
| 12 |
> |
| 13 |
>Still no success with 2.x ... |
| 14 |
|
| 15 |
Debugging preexisting containers is hard (because people usually don't |
| 16 |
share that.) |
| 17 |
|
| 18 |
Since you are starting with a blank one, I would love to see your |
| 19 |
failing testcase -- i.e. sequence of shell commands to trigger the |
| 20 |
unanticipated behavior, such as the existing testcases in |
| 21 |
src/t-crypt: |
| 22 |
|
| 23 |
echo that | openssl whatever |
| 24 |
cryptsetup luksFoo,Format,Open that. |
| 25 |
mkfs |
| 26 |
cryptsetup luksClose |
| 27 |
mount.crypt -o [...] |
| 28 |
|
| 29 |
It does not need to follow t-crypt's style, just the sequence alone |
| 30 |
is good. |
Archives