Is there any chance the requirement that an entry must have a password could be removed?
I've started using PasswordSafe to bookmark some important web sites, and I dont always have (or want) to store the password, and end up just putting a dummy password in.
This is a precaution against forgetting to enter the password. I guess it could be changed into a "No password was entered - are you sure?" type of warning (and the the application will enter "n/a" for you, for backwards compatibility.
Last edit: Rony Shapiro 2013-10-26
+1
backwards compatibility... ? does the pw field need something populated?
Some websites use my windows domain password, which I'm not storing in pwsafe (as I need to enter it to get access to pwsafe anyway...) and I'm looking to ensure it cannot even try to send even a dummy password around for such an entry.
Both Title and Password are the only mandatory fields for a PWS entry. This is used in many places within PWS and not easy to change. Any change would require significant regression testing.
Fair enough, I'll work around this then.
I don't really develop PWS any more. If another developer can/wants to do this, you may be in luck.
No worries. I've downloaded the source and have started to take a look around to see if if this is something I could do myself, just trying to get Visual Studio (2005) re-installed so I can do a test compile.
You may have a major issue there. The default VS has been 2012 for quite a while. There is no guarantee that all project files have been updated for old versions of VS.
Good luck!
Thanks, will have to see if I can persuade someone to buy me an upgrade :-)
Hmmm, doesnt look like pwsafe8.sln for Visual Studio Pro 2005 works anymore, or I'm doing things wrong (I normally use make/gcc on unix command line).
Various missing source files to start with - UUIDGen.cpp and tinyxmlparser.cpp to name but two, so cant even compile the code to start with, fairly major hurdle... Would need advice from an existing developer on this. Other errors cover things not being a member of a namespace and various syntax errors. Anyone willing to discuss this offlist to work out what I've done wrong, or is the code no longer compilable under VS2005 ?
Code should be compilable under VS2005. The errors you've reported are just changes in the source files, e.g., tinyxml et. al. has been replaced with pugixml. You should be able to open *.vcxproj files with a text editor (they're XML) and get a good idea of the current file set.
Please contact me directly if you need more assistance. ronys at users dot sourceforge dot net.
In principle, VS2005 should still work, as we're (still) not using any of the new C++11 features (this will change in 4.x).
You should be able to open the VS11 project files with a text editor and see the files that are currently compiled. The difference from when VS2005 was used shouldn't be that great...
If I were to do this, I wouldn't change the code. I would export the entries with everything you want and then post-process the XML file with a simple VBScript procedure. I would replace every line that begins
"<password>"
with something like
"<password>.</password>"
I would probably add 2 more lines per entry to stop automatic copying of the password via double clicking an entry after import (the '1' means "View/Edit"):
<dca>1</dca>
<shiftdca>1</shiftdca>