Passé is a SuperGenPass compatible password tool. It uses one-way cryptographic hashing to generate a unique (but repeatable) password for every site you visit online, while you only need to remember one "master" password.
Unlike most other password solutions, SuperGenPass is completely stateless. That means:
- Your passwords are never stored anywhere - there is no secret database to steal!
- It's 100% portable - you can use SuperGenPass anywhere, you don't need to bring anything with you.
So why not just use SuperGenPass?
In addition to the core SuperGenPass functionality, Passé allows you to store a central, non-sensitive database of the domains you visit and the particular settings associated with each one. This is strictly a convenience; you can still use any other SuperGenPass implementation in a pinch to generate a compatible password (since they all use the same algorithm).
Having said that, it's a very nice convenience. It means you can change certain settings and store notes per-domain. Like perhaps which master password a given site uses, if you have multiple or are in the process of changing your master password. It also helps you out when a site gets hacked - you can store a non-sensitive "suffix" which alters your generated password without having to change your master password."
But you're storing my data online! Is that safe?
If your stored data were to be hacked, the attacker would have access to:
- the list of your saved domains
- the length, suffix and note associated with each domain
That would be bad, but your master password and any individual site's generated password are never sent to the server, and are never stored anywhere. If you're not happy with that, you should just use SuperGenPass. Personally, I'm willing to trade that minor risk for the convenience offered by Passé.
Is my Passé database encrypted?
Nope. If you use the command-line tool, it'll be stored as a plain file. If you use your browser, it's saved in local storage (unless you use the "incognito" checkbox). If you use notes to remind you which master password you've used for a given site, you should make these as obtuse as possible; assume they could someday be read by someone else.
Do I need to be online?
Nope. It uses the HTML5 Application Cache, and stores your DB locally so you can do anything while offline, and it'll sync any DB changes when you're next online.
What's the "suffix" field for?
Sites get hacked with alarming frequency. If your generated password is compromised you may want to add (or change) a suffix for the affected domain. Passé will append the stored suffix to your master password when generating the site-specific password, giving you a completely new site password without having to change your master password.
Of course, if you suspect your master password could have been compromised (e.g your site-specific password was divulged, and an attacker tries to brute-force your master passsword with the knowledge that you might be using SuperGenPass), you should definitely change your master password rather than simply changing the suffix.
Why is it called Passé?
Well, the idea of using the same password (or a few passwords) for everything online is pretty much broken and outdated. And yet there doesn't seem to be a clear way out of this mess. Passé doesn't try to change the internet, it just acts as a smart layer between you and your passwords.Also, Passé shares a lot of letters with "pass" / "password". It turns out a lot of these sorts of names are already taken, but nobody else is scrambling for the self-deprecating ones :-)
I don't trust you!
Good! Depending on how little you trust me, you can do any (or all) of these things:
- check out the source code on github.com/gfxmonk/passe
- audit the code to your heart's content
- build it yourself
- run your own instance, and never even talk to the public server
Passé is written in Ocaml (both the server and client; which is compiled for the browser using
js_of_ocaml). Some of the build tools require nodejs.
If you have nix, you can just use
nix-shell to get the required dependencies (or just run
nix-build to build the whole thing).
If you don't have
nix, you'll need:
- opam (for ocaml dependencies)
- nodejs (for the less compiler + twitter bootstrap sources)
- then use
opamto install dependencies. You can see the current set of dependencies by looking at
./nix/opam-deps/*.nix. Unless you're building a unikernel, you can ignore the dependencies from
mirage-*.nixfiles (but note that you'll still need the
mirage-*packages which appear in
common.nixetc, since they provide necessary type definitions.
To just build everything, run:
This will build your current workspace from scratch.
For development, you can build incrementally instead. Get into a shell with:
Then build with:
$ gup all
This will build into
./_build, listing individual targets that can be built (with
gup) as it goes.
$ ./result/bin/passe-server # (replace `./result` with `./_build` if required) # You can now hit up http://localhost:8080/ in a browser, # or run the CLI with: $ env PASSE_SERVER="http://localhost:8080" ./result/bin/passe
This is not really recommended (because it there is no uninstall) but if you're cool with that, run:
Run your own openshift instance:
To build a portable image, run
gup openshift/all from a nix shell. That'll make a self-contained
installation including all required libraries, as long as you're building on an x86_64 machine.
MIT (see ./LICENSE file).