pwman-tools

Check-in [1ead16f19c]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Store secure notes in the "launch" field as it's 256 vs 64 char

And secure notes are likely to be longer. Since whole file is encrypted
anyway, doesn't matter which field you use to store things in. Saves
patching PWman to make the password field accept more chars.

Add note to README regarding this known limitation.

Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | master | trunk
Files: files | file ages | folders
SHA3-256: 1ead16f19c3a9911b2140f890ce9f19bce49ee7b396e1ae50d83e8e643e98e45
User & Date: atomicules@lavabit.com 2013-02-03 21:42:51.000
Context
2013-07-16
11:44
Create LICENSE check-in: bbd0069fdd user: atomicules@lavabit.com tags: master, trunk
2013-02-03
21:42
Store secure notes in the "launch" field as it's 256 vs 64 char

And secure notes are likely to be longer. Since whole file is encrypted
anyway, doesn't matter which field you use to store things in. Saves
patching PWman to make the password field accept more chars.

Add note to README regarding this known limitation. check-in: 1ead16f19c user: atomicules@lavabit.com tags: master, trunk

21:35
Use Ascii armoured output

Note that this doesn't hugely matter. PWman has no trouble reading the
file under normal encryption and will convert it to Ascii when saving it
anyway, but using Ascii up front is more what you'd expect. check-in: d3432a1e16 user: atomicules@lavabit.com tags: master, trunk

Changes
Unified Diff Side-by-Side Diff Patch
Changes to README.markdown.
Changes to lastpass2pwman.lisp.