- v4.0.5-beta
-
ea444b0 -
Verified
This commit was signed with a verified signature.walterpg Walter Goodwin
- v4.0.5-beta
-
ea444b0 -
Verified
This commit was signed with a verified signature.
- Transparently support Drive shortcuts (issue #20).
- Fix unexpected "upgrade" popup dialog after changing the sync configuration entry.
- Disable default sync ops to shared files due to a potential security problem (issue #21).
- Implement a session-stored authorization token option.
- Fixed privacy policy link on authorization upgrade form.
- Many minor UI tweaks for better KP integration.
- Update Google support packages.
- Fix config upgrade crash, #30 (thanks to @Rookiestyle).
Drive Shortcut Feature
The release includes a solution for syncing databases to Drive files referred to by "internal" Drive shortcuts. Please see the kpsync.org documentation for details.
Addressing Shared Database Security
As of this release, the plugin, by default, will not synchronize with Drive files that are shared with other Drive accounts via Drive's
shared file feature. As discussed in issue #21, and detailed in a published security bulletin, such usage enables a means to obtain unauthorized access to the Drive account of the sharer (or a sharee). While there remain many less convenient ways to share a KP database containing valid Drive authorization tokens, the plugin is no longer complicit in such usages.
Since the shared file issue is considered a long-standing defect, some users may already be aware of it. Others may be unexpectedly impacted by the security implications and/or the change in default behavior mentioned above. The latter should follow the guidance contained in the security bulletin.
To address security hazards, the optional session-stored authorization token feature was implemented. Safe access to databases shared by any means, including Drive's shared file feature, can be enabled with this option. The security issue is mitigated by displacing authorization tokens from the database into secure KeePass session storage. To synchronize with this feature, users are required to authorize the plugin with Google Sign-in once per open database at each restart of KeePass. It is thus an effective but inadequate solution.
A more general solution for shared file security will be a subject of a future release.
Still in Beta
Maybe the last?
Do you use shared KeePass databases? If you have ideas for safely, conveniently doing so with the plugin, please raise an issue or submit a pull request.
As always, Thank you for your feedback.
Assets
5
- v4.0.3-beta
-
05a4b90 -
Verified
This commit was signed with a verified signature.
- v4.0.3-beta
-
05a4b90 -
Verified
This commit was signed with a verified signature.
- Fixed Google Sync 3.0 regression (issue #14).
- Implemented target subfolder feature.
- Implemented KeePass proxy server configuration support (#15).
- Fixed regression in Configuration drop-down control (issue #17).
Release Note
This release fixes a Google Drive Sync 3.0 compatibility problem introduced
by the Target Folder
feature. If you prefer not to use Target Folder, the database file
can reside in any Drive folder, but its name cannot be duplicated in
any other Drive folder.
The plugin now respects KeePass proxy server settings when constructing
connections to Drive. This has undergone limited testing, so please share
your experiences.
The Target Folder feature now
provides access to subfolders using a "file separator" syntax in the
specification.
Thank you for your feedback.
Assets
5
- v4.0.2-beta
-
0e9c689 -
Verified
This tag was signed with a verified signature.
- v4.0.2-beta
-
0e9c689 -
Verified
This tag was signed with a verified signature.
- Ship Google-verified OAuth 2.0 creds (woo-hooo!!).
- Add upgrade prompt, shown once for those using the legacy creds.
- Rebranding as required by the service provider.
- Fix satellite resource dll deployment.
- Change binary distribution blob names.
- Migrate to proposed OAuth 2.0 client_id.
- Add "limited access" detail docs.
- Publish https://kpsync.org (nee gdrivesync.org).
- Warn user when changing auth method if there is a refresh_token
present. - Add "issue" templates, CONTRIBUTING, and CODE_OF_CONDUCT.
- Beautify "about" tab.
Release Note
New builtin OAuth 2.0 creds are here, and about time too!
These are freshly minted, fully Google-approved, and project
(re)branded for your security and simple pleasure! Full
compatibility with prior creds is retained (both old-plugin builtin,
and user customized), but the new creds will be the default option
going forward. NO MORE scary sign-in screens! (Unless that's what
you prefer!)
Unfortunately, rebranding required for verification changed
some names and such. Please review the UPGRADE FROM ALPHA
docs for more info.
Also, everything worth documenting is now found at
kpsync.org. As always, we want to know
how the plugin works for you, whether bad or good (please
submit an "issue").
Assets
5
- Fix MRU bug.
- Fix broken links, typos. Some doc changes.
- Implement selective command disabling feature.
- Fix drive scope selection and related configuration issues.
Release Note
Many thanks to those who have started using the new plugin. Your feedback is always valuable and welcome.
Google Drive OAuth 2.0 authorization has become tricky business for Google-unverified applications such as this. Even using your own OAuth credentials may result in scary-looking warnings when authenticating your account, especially in the Chrome browser. And the built-in OAuth credentials may not work at all, or only in a limited scope. Please see the Default OAuth topic for more info, and bear with us as we prepare to apply for verification.
Assets
5
- Prepare to go public.
- First draft of documentation.
- Release build tool for signing the KeePass version manifest.
- Release build tool for managing "built-in" credentials.
- Fix global config bug.
Assets
5
Alpha 1
Fixes
- Embedded browser control replaced with browser-based Google Sign-In authentication.
- Option for less restrictive Drive access mode (may allow continued use of the
otherwise broken built-in OAuth 2.0 credentials).
Enhancements
- Improved KP-themed UI.
- Latest Google Drive API libraries.
- Global configuration options for simplifying new database setups.
- Automated password entry generation for new databases.
- Standard KP User/Password credential clipboard access for Google Sign-In.
- Framework for language translation support.
This can be safely installed side-by-side with the old plugin. A lightly-edited version of
the old readme.txt is included and its instructions for installation/usage still apply for now
(notice the name change!). More documentation will be forthcoming.