Releases: subdavis/Tusk
Keepass Tusk 🐘 Back from the Dead 🧟
Tell your friends. The Elephant raises her head in proud defiance. I'm pleased to announce version 2024.8.2, the first update since 2018 😮. Available for Firefox and Chrome.
❗Having problems? ⛔ Authorization error? Read the troubleshooting guide.
Why now?
Google is requiring extension developers to either upgrade to Manifest Version 3 (MV3) or get taken down. Tusk still has ~50K weekly active users at the time I wrote this post. I wanted those people to be able to continue to use Tusk.
Plans for the future
I have un-archived the Github repository to begin accepting new issues again, and will do my best to keep things in working order and responding to reports. I don't expect to build any new features, but I'd like to at least make sure the existing features work properly and reliably.
I want to emphasize that my goal here is not to continue to grow Tusk's user base. It's just one of a number of great options in the ecosystem. The goal is simply to maintain Tusk as a trustworthy and stable tool.
What changed?
The bulk of this update can be filed under a couple of topics.
- Manifest and Chrome API Updates. The biggest change to the Web Extension API between 2 and 3 is a migration to service workers rather than background processes. Tusk was already using all the right hooks and made the switch to service workers easily. There were some security changes to the scope of that runtime context (no more document or window access) that also didn't give me much trouble.
- Google Drive integration improvements, notes below.
- Some bug fixes to the Shared URLs provider. TL;DR only Dropbox shared urls and direct links still work in 2024.
- Clipboard clear. Due to changes in the MV3 api, Tusk is no longer able to clear the clipboard after a set period of time when you copy your password. I'm exploring using chrome.offscreen as an alternative to the Clipboard API.
- Dropped support for PCloud. At some point in the past, PCloud deleted my whole developer account and application keys. I attempted to make a new account, but their developer portal is broken. Tusk no longer offers PCloud as a provider.
- Build system updates. Trying to revive the old build system after not touching it for 6 years proved challenging. It was based on Webpack and who knows what version of Node.js. Seven or something, I have no idea. After a little bit of tinkering, I decided to scrap the whole build system and upgrade to Vite.js. Browser support for JS language features is much better now than it was in 2018.
Changes to Google Drive Integration
It's been a struggle. The result is an dramatically improved, more secure Google Drive integration. It will also hopefully be more stable and handle expired tokens better.
Before I came along, Tusk was written to request full read/write access to a user's entire Google Drive for the purpose of searching for *.kdbx
files. Google used to be OK with this, but they've cracked down in recent years and now, developers asking for that level of access are subject to a litany of additional verification requirements culminating in something called CASA verification. I don't have the time or resources to do that, and it needs to be renewed anually.
Instead, I've taken great pains to build the Google Picker into Tusk so that a user can specify an individual file or files Tusk can access. This requires a much smaller scope of access to your GDrive and as a result, doesn't impose these verification requirements.
Due to technical requirements mostly related to how Google chose to build its javascript SDK (which requires remote script execution) and the strict script-src: self
CSP of MV3 chrome extensions, I was forced to iframe
the Picker interface in from a page hosted at https://subdavis.com/Tusk. It's sort of an interesting solution, and I'm planning to write more about it later.
There's more work to do.
Tusk is still based on some old libraries.
- Vue.js upgrade. While I was able to upgrade the Vue.js version from 2.4 to 2.7, this is still an End-of-Life release stream. The good news is that a lot of people are still using 2.7 (700K downloads this week) and I don't see it posing any risk for now.
- KdbxWeb upgrade. The wonderful JS implementation of the Keepass database management library from the Keeweb project is still on v1. Version 2 came out in 2021 and hasn't really updated since, but it introduced enough changes that I decided to make this upgrade later.
Get involved
You wanna help maintain Tusk? I'd love if some others wanted to get involved 💙
- Triage GitHub issues. Come help me provide users with technical support and prioritize tickets.
- Help people resolve problems in the web store reviews. People treat the review section like it's a support forum, and leave 1 star reviews when they can't get something to work. Anyone can reply to reviews with advice and technical support.
Tusk 2018.9.27
v2018.9.27 Bump version 2018.9.27
Tusk 2018.9.23
Fixes:
- Unlock database with only keyfile
- Better explanation of limitations with local upload.
Tusk 2018.9.8
Includes a new logo, some UI design changes, bugfixes, additional advanced settings, and more.
Tusk 2018.6.27
Tusk 2018.6.16
v2018.6.16 Bump version 2018.6.16
Tusk 2018.5.19
Includes pCloud support and feature toggle for keyboard navigation.
Tusk 2018.1.16
Includes bugfixes for reading XML keyfiles and Google Chrome Google Drive authentication
Tusk official release
This is it, folks.
Tusk 2018.1.3 beta
Update mechanisms for caching and forgetting secrets.