If you use the Internet much, you have a hundred different passwords for things like email accounts, subscriptions, banking, social media, and the like. The best passwords are long and complex (combining letters, numbers, symbols, and punctuation) and never reused across different accounts. With so many to remember, some people use a password manager to securely store everything behind a single, memorable master password of suitable complexity. Password managers make it easy to use strong passwords for every account - but they also introduce a single point of failure. Much has been said on both sides of the argument and the decision to use a password manager should be made carefully.
If you decide a password manager is right for you, there are different kinds and many options to choose from. For my purposes, a cloud-based password manager seemed best. Thinking about what's important to me, I wanted something:
- Open source
I couldn't find a perfect match, so I wrote my own cloud-based password manager: PassWeb. From time to time, someone asks to try it out, so I've open-sourced the implementation for anyone to evaluate, use, and improve.
I've tried to ensure PassWeb is safe and secure for normal use in low-risk environments, but do not trust me. Before using PassWeb, you should evaluate it against your unique needs, priorities, threats, and comfort level. If you find a problem or a weakness, please let me know so I can address it - but ultimately you use PassWeb as-is and at your own risk.
What is PassWeb? PassWeb is a simple online/offline web application to securely manage passwords. Data is encrypted locally and stored in the cloud so it's available from anywhere. Unencrypted data never leaves the machine, so YOU are in total control.
How do I use PassWeb? Click an entry's title to open its web site. Click the name/password field to copy (where supported) or select it for you to copy+paste. Click the padlock to generate a random, complex password for each site. Notes store additional info.
How do I create a login? Contact the administrator with the user name you want and he/she will create a new account with a temporary password. Log in, change the master password to something only you know (and won't ever forget!), then create entries for all your accounts.
What if I'm not online? Checking the "Cache encrypted passwords" box makes your data available offline. Changes are synchronized with the server next time you use PassWeb online. Simple updates merge seamlessly; overlapping updates should be avoided.
What if I leave PassWeb open? It's okay: PassWeb logs you out after three minutes of inactivity to protect your data. Names and passwords unmasked for copy+paste are re-masked after ten seconds to prevent anyone nearby from reading them.
Why shouldn't I use untrusted devices? Untrusted machines (like a library kiosk or a friend's laptop) may have malware installed that records keystrokes. Typing your master password on such a device would compromise it, allowing an attacker to use your PassWeb account.
What if I forget the master password? Sorry, your data is irretrievably lost! PassWeb's encryption algorithm is government-grade and there aren't any backdoors or secondary passwords. It's up to you to remember the master password - and keep it secure!
What browsers can I use? Because it's simple and standards-based, PassWeb works cross-platform on modern browsers like recent releases of Internet Explorer, Chrome, Firefox, and Safari. If you see a problem, please email me detailed steps to reproduce it.
Why is it important to use HTTPS? HTTPS creates a secure connection that encrypts all data and makes it difficult for others to intercept. HTTPS helps verify the identity of web servers, prevents tampering with content, and will soon be supported by all major sites.
- The client for PassWeb is a simple HTML application and can be hosted on any web server or file server.
- For offline mode to work, the
offline.appcachefile must be served as type
text/cache-manifestand should not be cached.
- For offline mode to work, the
- The server for PassWeb is a simple REST API that stores and retrieves blobs of data.
- Implementations are provided for both ASP.NET and Node.js.
- If data is stored as files (under an
App_Datadirectory), the account used by the web server needs
modifypermissions for that location.
- If data is stored as blobs (supported by the Node.js implementation for Microsoft Azure), permissions to read/write/list/delete are needed.
- Choose the ASP.NET or Node.js server based on your hosting options or background; the two implementations are (mostly) equivalent.
With default settings for the server, creation of new blobs is blocked to prevent unwanted users; the administrator should temporarily unblock when creating a login for a new user.
In the ASP.NET implementation, this is done by commenting-out the following line in
// Remove to allow the creation of new files #define BLOCK_NEW
In the Node.js implementation, this is done by changing the following variable to false in
// Set to block the creation of new files (set environment variable to "false" to override) BLOCK_NEW: process.env.BLOCK_NEW !== "false",
Or by setting the
BLOCK_NEWenvironment variable to
"false"before starting the server. This makes it easy to apply a temporary override without changing the code (such as when creating a new account).
Offline use (optional)
- The encrypted data file is read from and written to both the server API and HTML local storage after every change.
- When the server can't be reached (e.g., when offline), changes can be made locally.
- When the server is reachable during login, local and remote changes are synchronized and both locations are updated.
- Non-conflicting changes to different accounts merge seamlessly; conflicting edits to a single account are resolved by keeping the most recent entry.
- All account data is stored in a single, compressed, encrypted file.
- That file is encrypted using the Advanced Encryption Standard (AES) in Cipher-Block Chaining mode (CBC) mode.
- The file name is derived from the master user name and password by hashing with SHA-512.
- The encryption key is derived from the master password, the domain name, and a random salt via the PBKDF2 algorithm configured for SHA-512 and 1000 iterations.
- The data is only ever decrypted on the client; the server never sees the user name, password, or unencrypted data
- The default configuration blocks creation of new files to prevent unwanted accounts.
- The default configuration keeps a backup of every version of the encrypted data file as a safety measure.
- Because it is always encrypted, the account data file can be transmitted via the storage API over an unsecure HTTP connection.
- Turning on HTTPS for the storage API is strongly recommended because it prevents tampering and hides the hash of the user name/password (this is enabled by default).
- Enabling HTTPS for the PassWeb client files is also strongly recommended because it prevents tampering (this needs to be enabled on the web server).
- Mixing HTTP/HTTPS requires the storage API support Cross-Origin Resource Sharing (CORS) and requires an update to
|offline.appcache||Offline cache manifest|
- Add ability to import data from other password managers
- Convert to the Web Cryptography API (once widely available)