Group assignment encryption decryption process

Registered by Prunus dulcis

Group assignment needs to define these steps
1. Create, remove group (what to do with related entries?)
2. Add, remove group members
3. Set group encryption password (which would need to be stored in the database only encrypted by the universal password, unsafe... need another alternative)

Blueprint information

Status:
Not started
Approver:
Prunus dulcis
Priority:
Low
Drafter:
Prunus dulcis
Direction:
Needs approval
Assignee:
Prunus dulcis
Definition:
Drafting
Series goal:
Accepted for 11.02
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

Group assignment needs to define these steps
1. Create, remove group (what to do with related entries?)
2. Add, remove group members
3. Set group encryption password (which would need to be stored in the database only encrypted by the universal password, unsafe... need another alternative)

1. Creating a group should not be a problem
Needed
- GUI for changing element user to group
- Group dbObject

2. Add, remove group members
- think about group roles (does a group need an administrator with special rights or are all treated equally)
- remove group members (can users only remove themselves or others as well, see above)
- implement a GUI to add other users to group and to apply for being added to group
- implement a GUI to remove users from group

3. The group encryption password would probably best be encrypted for each user with their individual encryption password and be stored in a HashMap<String username [encrypted by universal password], String group password [encrypted by user password]>
- create a group password
- manage encryption/decryption of elements, that have been changed from user to group ownership
- when storing a changed group element, ask if it should be stored as group element or as private user element (changing the owner from group to user and changing encryption from group to user)

Other ToDos:
- group management
Change implementation of dbObject, since groups are then an object themselves and group membership is in these group objects, not in the user objects as a field

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.