Re: [gnukeyring-discuss] crypto.c, Line 67, DES3_Read: not block padded

[Jochen H. <jo...@gn...>]

On Friday, 28. June 2002 15:09, you wrote:
> Dear all,
>
> being a fascinated user of gnukeyring, I have been experiencing the
> problem mentioned in the subject field since I upgraded my Palm Vx
> to Palm OS 3.5.3.  I use a German version of PalmOS.
>
> There is one possible source for the error: I use the gnukeyring
> plugin of jpilot for data handling on the Linux PC.  Maybe this
> software there creates the mis-padded block.
>
> Has anyone had the same problem and could fix it?  Or does know
> where I could start looking for further information.

I haven't heard about the problem, yet.  You can inspect the key file 
with the pilot-* tools:  Fetch the database from the palm with

pilot-xfer -f Keys-Gtkr

And then dump it with "pilot-file -v Keys-Gtkr.pdb"

The records (except record 0) should look like this:

entries
index   size    attrs   cat     uid
[...]

10      40      0x40    5       0xd96014
0000: 4b 65 79 72 69 6e 67 00 68 de 34 7a 54 f8 9a 22 Keyring.h^4zTx."
0010: 3a ac da a5 19 ae 03 a7 16 55 cf 2c 26 9e a2 92 :,Z%...'.UO,&.".
0020: e3 6f 9c e8 d3 31 5b 80                         co.hS.[.
^^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^
Addr. Hex Dump                                        Ascii text

The Ascii text should start with the clear text name, followed by a 
single NUL byte (depicted as ".").  After that comes the encrypted 
password data, it should consist of a multiple of 8 characters.

In this case the name is "Keyring", followed by NUL byte, followed by 
32 bytes of crypted data (which is a multiple of 8).

The record you have problems with probably has some extra characters 
after the crypted data.

  Jochen

-- 
Jochen Hoenicke -- ICQ: 101057678