You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This section provides in-depth information about how tusk works under the hood. We aim to provide better transparency and give users peace-of-mind. Tusk may not be perfect, but it's better than proprietary black-box applications that hide design flaws from the community.
Sensitive Data - How Tusk handles sensitive data like KeePass databases and keyfiles.
Build Setup
Tusk requires:
node
yarn
# install dependencies
yarn install
# build for production with minification
yarn build
yarn pack:zip
# Hot reload
yarn dev
Running tests
To run tests, first build them with yarn build-tests or yarn watch-tests then open tests/test.html in a browser.
Browser Permissions
Tusk requires cross-origin permissions in order to inject credentials and query the storage backends on the user's behalf.
In chrome, these permissions requests are always prompted to the user upon first use.
Because of Firefox's implementation of browser.permissions, it was necessary to request all permissions at install time to avoid code rot. A deeper explanation of the firefox permissions can be found on stackoverflow
FAQ
Why is it called Tusk?!
I originally wanted to call it Elephant, as in An elephant never forgets. I tried this name on a couple of friends and they were unimpressed. I wanted to find a name that was more concise but keep the elephant imagery. Ergo, tusk.
What happened to CKPX?
This is it! CKPX has been rebranded as Tusk to mark its Firefox release. The C in CKPX stood for 'Chrome'.