Re: V3 Format Comments

On Sat, 14 Jan 2006 17:26:23 -0500, <[email protected]> wrote:
>
> I haven't read the document you reference but one thing that I believed  
> was
> agreed with V3 was that all the old clutter relating to previous  
> versions was
> to be removed from the code e.g. no more Blowfish etc. etc.
>

The V3 format uses the same data structures for password records as  
previous
versions, i.e., one block containing the field type and length, followed by
the field's data. This is only reasonable. I don't know that you mean by
"clutter".

>
>                                                              It was also  
> agreed
> (again I believe) that V3, as it wouldn't "know" anything about prior  
> versions,
> would also not be able to read in previous versions and convert them to  
> V3.  In
> fact, in order to open a non-V3 database, it would call a standalone  
> program
> (that would also prompt for the passphrase) to try and convert it for it.
>

This is an implementation issue, and best left to the implementors.  
Personally, I
don't see any benefit to the design that you are suggesting over having a  
single
implementation that supported all prior versions of the database format.

>
> I had better look at this documentation, although I am not conversant  
> with CVS,
> it would be nice if they were available just to be downloaded from the  
> website
> (e.g. as current executable and source code).
>

Just go to "Browse CVS Repository" on SourceForge. The V3 document can be  
accessed at
http://cvs.sourceforge.net/viewcvs.py/passwordsafe/pwsafe/pwsafe/formatV3.txt?rev=1.4&view=auto

Frank


-- 
Frank Pilhofer, [email protected]


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click