-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
KeeShare: Remove checking signed container
* Remove QuaZip dependency in favor of minizip * Remove signature checks, but maintain signatures for backwards compatibility * Remove UI components related to certificates except for personal certificate for backwards compatibility * Default to unsigned containers (*.kdbx)
- Loading branch information
1 parent
c88d8c8
commit 12990e5
Showing
28 changed files
with
278 additions
and
1,645 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
# MINIZIP_FOUND - Minizip library was found | ||
# MINIZIP_INCLUDE_DIR - Path to Minizip include dir | ||
# MINIZIP_LIBRARIES - List of Minizip libraries | ||
|
||
find_library(MINIZIP_LIBRARIES NAMES minizip libminizip) | ||
find_path(MINIZIP_INCLUDE_DIR zip.h PATH_SUFFIXES minizip) | ||
|
||
include(FindPackageHandleStandardArgs) | ||
find_package_handle_standard_args(Minizip DEFAULT_MSG MINIZIP_LIBRARIES MINIZIP_INCLUDE_DIR) |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
12990e5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, what is the rationale behind removing this feature?
The .share container is encrypted with KDF(password) key, which presumably can be bruteforced. I had an idea to implement a mode, in which KeePassXC will generate separate container for every public key the user has already imported and set trust, additionally encrypted the the given public key. Then during the sync/import process, every user from the team(the idea was to share credentials between team members) will lookup the .share container, for which he's got the private key, decrypt it and continue with the sync/import process. This is rough idea and lacks the public key management part, which can be arranged.
Maybe I'm missing some security feature of KeeShare, which can avoid bruteforcing the .share containers if an attacker gets to them.
12990e5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A .share container is simply a zip file with a normal kdbx database and a signature file. The signature provides absolutely no additional security, nor were we verifying the signature against any identity provider. This makes signing files completely pointless.
12990e5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what I saw and hence the idea to take this further in more useful way.