i ran across this little project a few days ago, and must say it's impressive. kudos to everyone involved. experimenting with pwm has been both fun and frustrating. no worries though: i get three more chances to access my bank account tomorrow :)
i've spent quite a bit of time reading the manual, faq, and of course these forums, and would like to contribute $0.02.
there are several threads regarding sync'ing and/or ftp support. however, i didn't see any references to having the rdf file saved to a remote location _instead of_ a local hard drive. iow, have only one rdf file and have it located on a remote server.
picture this: i use pwm on my personal laptop (which dual boots win/linux), home desktop computer (also dual booting win/linux), family computer (which is setup for mom, dad, and 2.8 kids), work desktop, work laptop, blackberry, etc. wouldn't it be nice to have just one rdf file on a remote server instead of having 2, 3, 5, 10 or who knows how many different rdf files and trying to keep them sync'd?
regarding the online version, one or more people mentioned having control over what preferences are stored in the cookie. i agree this is important. a lot of the security comes from the different options selected when generating a password. having the leet level (if any), hash algorithm, password length, etc saved in a cookie would be _very_ bad if one is on a public computer. and the online version is probably being used _because_ one is using a public computer or at least a computer that isn't theirs.
it would also be nice to mask the generated password when using the online version. if you're using the online version there's a good chance someone will be looking over your shoulder. wouldn't want to give them a free peek at your online banking password (even if it's wrong and you're just trying to guess it :)
thanks for a great concept and its implementation.
....steve