Description of problem: jpilot cannot show private records


Version-Release number of selected component (if applicable):


How reproducible: every time


Steps to Reproduce:
1. Start jpilot with a database containing private records
2. Click on the "lock" button to view private records
3. jpilot asks for password, but never accepts the password
  
Actual results: jpilot never accepts the PalmOS password and so doesn't allow
the user to view private records.


Expected results: Should accept password and unlock private records


Additional info: The problem seems to be due to a 64-bit bug in pilot-link.  I
asked about this problem on the jpilot list and received a response from Ludovic
Rousseau, who pointed me to the following bug he had recently
filed at pilot-link.org: http://bugs.pilot-link.org/1858

He says that the problem is due to a 64-bit bug in pilot-link, where
pi-md5.h has 
  #define UINT32 unsigned long
which is incorrect on 64-bit systems, and that this prevents jpilot from
computing the right hash to view private records.  He recommends
changing this to 
  #define UINT32 unsigned int
though he notes that this will work on 32- and 64-bit systems but fail
on 16-bit ones. 

I rebuilt the pilot-link and jpilot srpms with this change in the pilot-link
source and jpilot can now view private records on my laptop.  So the fix seems
to work, but I have not tested it extensively.

(This is probably really a bug in pilot-link, but as far as I know it only
manifests itself in jpilot.  Rahul Sundaram on the Fedora list recommended
filing it against jpilot.)