Which KeePass? Ver 1.5+ or 2.+ ??

[Shepherd Jim]

Hello!
I've been using an old Palm password storage database called
"Cloak" (Chapura Software) for YEARS. I'm now in the process of moving
out of my end-of-the-line Palm device -- a Centro smartphone -- and
into a Motorola Droid.

I Have HUNDREDS of records/passwords in Cloak on the Centro and my PC
desktop.

I've been reading the KeePass website and feel pretty certain that
there's no DIRECT way to convert my Cloak files to KeePass so I'll be
exporting a .CSV from Cloak and then endeavoring to suck that up into
KeePass.

WHICH version of KeePass am I best off using? From the official
KeePass website it sounds like it's almost a coin-toss. But, I see
where KeePassDroid treats ver 2.+ as a beta. SO, I'm thinking I'll
start off with ver. 1+ on the desktop -- see how successful I am at
importing the .csv. And, then try to copy the resulting KeePass files
onto the Droid and see how KeePassDroid likes that.

PLEASE let me know if there's some reason that I'd be better off going
with ver. 2.+ -- I see where 2.+ has a more extensive of importing
software than does 1.5+, but I DO also want this all to work with
KeePassDroid.

If this all works I'll be making donations to both the KeePass and
KeePassDroid people. I'm a huge fan of open source software == s'truly
amazing what's out there!!

Wish me luck! Jim
PS - I'd love to hear any "tips or tricks" from anyone who's gone down
this road before. I can't think of anything stored on either the Palm
Centro or my laptop that's more important/critical than the data
that's presently in Cloak.

[Martin Sherburn]

I used to use v1.x when I first started using KeePass. When v2.x came out I switched to that and haven't looked back. I'm not sure why they bother keeping v1.x alive because it's basically just v2.x with less features. Looking at the website it seems like the only advantage of 1.x is that it doesn't rely on having .NET framework 2.0 installed (which you'll probably already have anyway).

You should know that you can still read/save v1.x database files with KeePass v2.x (i.e. it is backwards compatible). So that isn't a reason for using v1.x. Once you've got all your passwords into KeePass v2.x you can choose whether to save your database in v1.x or v2.x file format or any other format KeePass supports. KeePassDroid only supports reading of v2.x database, so if you want to add new passwords with your android phone I'd suggest using KeePass v2.x but saving as v1.x file format.

Hope that helps,

Martin.

[Jim Child]

Hey Martin -- much tnx for your reply.

Right along you seemed to be saying that there was no reason for me NOT to just start straightaway with Evernote. 2.+

And then, right at the end you're suggesting I use Evernote 2. but SAVE as Evernote 1.

Why wouldn't. I just go ALL ver 1 ??

Jim

[Shepherd Jim]

Meant to type " Why wouldn't. I just go ALL ver 2 (TWO) ??"

[Martin Sherburn]

Evernote? Huh? I guess you meant KeePass.

Personally I use KeePass 2.x and save as 2.x because I don't need to save passwords on my android phone, I only use it for accessing my passwords and never adding new ones. I do that with my PC.

My point was if you have KeePass 2.x you are more flexible because you can save as either 2.x or 1.x. If you use KeePass 1.x you can only save as 1.x.

Hope that makes sense,

Martin.

[Jim Child]

Hey John:

You should come up with two more "bullet points" and you'd have the necessary 10 for David Letterman to read on his show!  LOL

Seriously, I think you are right. Taking into account that I want to use KeePassDroid on my Droid it really makes sense to run totally in the 1.17 for the time  being.

I've finished (I think) downloading importer plugins and am going to start experimenting with trying to bring Cloak .csv records into KeePass 1.17.

Wish me luck!

Jim

On Thu, Aug 26, 2010 at 12:55 AM, JNavas <john....@gmail.com> wrote:

If it meets your needs, I suggest using KeePass 1.17, for the time
being at least:
1. KeePassAndroid is very handy for syncing your passwords to an
Android device....<snip>....

--
i wish i knew then what i know now