Downloads

Read the Legal notice: use of fpwdman is entirely at your own risk.

Executable Binaries

Right click on these links ("Save Link As ...") to get the latest versions. Note well: they are tgz archives, so check to make sure your browser has not changed the extension to tar, zip, gz, or something else. If so, change the extension back to tgz
- Debian binary, tarred and zipped. Uncompress it with tar -zxf fpwdman.linux.tgz
- Windows binary, tarred and zipped for NT/XP. Uncompress it with tar -zxf fpwdman.wndws.tgz at the command line, or via the graphical user interface of a tool such as QuickZip or WinZip.
The single graphical sbctool is included in the 2.x distributions. The two command line tools are also included in 2.x source and 1.x binary distributions.
The executables are statically linked, so you can run them "as-is" without having to install supporting libraries, like fltk

Source Code

The best way to get the most recent source is to download it via CVS. The project page has instructions on how to anonymously get the source from CVS. The top-level module is fpwdman.
Download tarred and zip source from the fpwdman release page on SourceForge. The source includes linux Makefiles, Dev-C++ dev files, and compilation notes. It also include this documentation, under fpwdman/doc/html.
- fpwdman-2.0.1 This is the first in the 2.x series. It includes not only fpwdman but also sbctool. The graphical sbctool replaces the two command line tools, but is completely compatible with them. You can upgrade by using fpwdman-1.0.6 to export to plaintext XML, using sbctool to encrypt the XML file, then open the encrypted XML with fpwdman-2.0.1.
- fpwdman-1.0.6 This is the last in the 1.x series before the 2.x series starts. fpwdman-1.0.6 can use the tinyXML library to export the password file to plaintext XML. This is so that it can be immediately imported by FPwdMan2
  
  FPwdMan 2 will be internally reorganized; it will also use XML. An example of its XML is now in the CVS tree, as is the (very simple!) DTD for it. The command line tools, ensbc and desbc, will be supplemented by a single GUI based tool for en/de-cryption. FPwdMan 2.0.1 should be available by November, 2006.
- fpwdman-1.0.5 now can use the zlib library to compress the password file before encryption. This feature is ON by default; it can be controlled via the Tools menu.
- fpwdman-1.0.4 now accepts the name of a password file as an argument. Thus, under Windows, you can open a file by double-clicking upon it. As usual, you must first tell Windows to "Open with ..." and check the "always" box. The ensbc command line encryption tool now accepts arbitrary length and format strings as the seed, not just a single integer.
- fpwdman-1.0.3 For some sites, a fairly big chunk of information might be recorded (user id, password, mother's maiden name, name of first pet, city of birth, SSN of first born child, ...). Therefore, the popup windows to create, edit, and view entries have been made resizable, so you can see long entries at a glance. A timeout then autoclosure feature has been added for security.
- fpwdman-1.0.2 You can now view an item just by double-clicking upon it. Therefore, the "View" button became redundant and was removed. A status line now shows the file being used, and whether or not there are unsaved changes.
- fpwdman-1.0.1 Added the ensbc and desbc command line utilities.
- fpwdman-1.0.0 Initial release of fpwdman.
You browse fpwdman's CVS tree via sourceforge.

Compilation and Installation Notes

The most important notes are in the top-level README file. It explains how to compile under both Linux and Windows. Note that you need the FLTK toolkit in either case. Although you could compile from the command line, or a different IDE, it has been tested with the Dev-C++. IDE under Windows.
fpwdman uses the cross-platform GUI toolkit fltk. Excellent documentation and instructions may be found on the fltk website. You will definitely need it if you intend to build from source code (which is recommended). You may need to get and install a runtime version for your machine. Try the binary first, and only install fltk if you get error messages indicating that it is needed.
Binary distributions are signed with this key. The top-level archive contains two files: the executable binary, and a signature for it. Both tar and winzip will uncompress the top-level archive to get the two files. You should then use PGP or GnuPG to verify the signature, before running the executable.
Source code distributions are signed with the same key. The top-level archive contains two files: the actual source code archive, and a signature for it. Both tar and winzip will uncompress the top-level archive to get the two files. You should then use PGP or GnuPG to verify the signature, before uncompressing and building the source code.