-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subgroups not included in Keeshare #11537
Comments
Then at least the documentation should be updated, accordingly as it reads: "Sharing Credentials |
Every entry. Read the whole sharing section, there is a very clear discussion on this quirk. |
Sorry - the documentation is clear, if I share the root, every password in my database will be shared, hence also all in groups, thus groups are shared, too. The same is a conclusion of ChatGPT, too. The documentation of KeepassXC read "Sharing Credentials ChatGPT: Sharing at the group level: If sharing is enabled for a particular group, all password entries within that group (including subgroups or "children") are shared. If you want to confirm exactly what "sharing" includes (e.g., metadata like group names or other structural information), it would be a good idea to review further details in the settings or test the feature in a secure environment. So, documentation is misleading, and needs update. |
Overview
Keeshare Funtionality is supposed to share every credential within a selected shareable group including subgroups as per user documentation.
Subgroups are currently not shared, though.
Steps to Reproduce
Expected Behavior
all groups and subgroups with the corresponding credentials should appear in the shared database
Actual Behavior
Open the shared database file separately, the subgroups won't appear
Context
n/a
KeePassXC - Version 2.7.9
Revision: 8f6dd13
Qt 5.15.11
Diagnosemodus ist deaktiviert.
Betriebssystem: Windows 11 Version 2009
CPU-Architektur: x86_64
Kernel: winnt 10.0.26100
Aktivierte Erweiterungen:
Kryptographische Bibliotheken:
see above
The text was updated successfully, but these errors were encountered: