Skip to content
Kee Vault is a password manager for your web browser. Password databases (Vaults) are encrypted using the KeePass storage format before being sent to a remote server for synchronisation across any modern device/browser
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
.vscode KeeWeb 1.7 patching fixup / deps update Feb 25, 2019
app Hide demo from mobile users Mar 22, 2019
build/util
static
util KeeWeb 1.7 patching fixup / deps update Feb 25, 2019
.editorconfig Initial commit Feb 18, 2019
.eslintrc
.gitignore
CHANGELOG.md Version bump Mar 20, 2019
CONTRIBUTING.md Initial commit Feb 18, 2019
DEPS-LICENSE
Gruntfile.js Removing comments to workaround Googlebot bug Mar 4, 2019
LICENSE
README.md Initial commit Feb 18, 2019
backupProductionDeploy.js Initial commit Feb 18, 2019
grunt.entrypoints.js moved grunt stuff Feb 24, 2019
grunt.tasks.js Followup Kee 1.7 build env update work and deps updates Feb 25, 2019
package-lock.json
package.json Version bump Mar 20, 2019
pipeline.gocd.yml
webpack.config.js
yarn.lock Initial commit Feb 18, 2019

README.md

Kee Vault

Kee Vault is a password manager for your web browser. Password databases (Vaults) are encrypted using the KeePass storage format before being sent to a remote server for synchronisation purposes.

This is the bulk of the user-visible part of Kee Vault app, based on a heavily modified fork of KeeWeb. To see the complete picture of what source code executes in the browser (and hence verify that sensitive data is protected) you'll need to look at some of the npm dependencies too:

  • kee-frontend: Offers a simplified API for interacting with the hosted Kee Vault service.
  • kdbx-placeholders: Enables support for KeePass placeholders.
  • kprpc: A KeePassRPC server for the KeePassRPC client within the Kee browser extension to connect to.

Obviously all npm dependencies in the project impact upon the behaviour of the app but we highlight those above since they are the ones authored by the Kee Vault team and hence would be the place to find any funny business on our part.

Client support

We aim for the project to be compatible with all browsers released in 2018 or later. Most modern browsers and devices will have already automatically updated to versions that support Kee Vault and many browsers from 2017 or earlier will also work, although we make no effort to validate this.

In future we may further increase the requirement to even newer browsers if we decide that failing to do so will put users of older browsers at a significantly increased risk. However, we'll try to introduce most features in a way that gracefully degrades the experience for users that are stuck on the "current modern".

Initial build prep per machine

npm install
mkdir cert
openssl req \
    -newkey rsa:2048 \
    -x509 \
    -nodes \
    -keyout cert/server.key \
    -new \
    -out cert/server.crt \
    -subj /CN=app-dev.kee.pm \
    -reqexts SAN \
    -extensions SAN \
    -config <(cat /usr/lib/ssl/openssl.cnf \
        <(printf '[SAN]\nsubjectAltName=DNS:app-dev.kee.pm')) \
    -sha256 \
    -days 3650

Build and run dev server

npm start

License

AGPL3 with permitted extra clauses

You can’t perform that action at this time.