-
Notifications
You must be signed in to change notification settings - Fork 1
feat(3058): Allow overriding decryption keys on keys* methods, add createLockbox method to team, add self-assign role method #18
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
base: main
Are you sure you want to change the base?
Conversation
packages/auth/src/team/Team.ts
Outdated
|
|
||
| /** Give yourself a role */ | ||
| public addMemberRoleToSelf = (roleName: string, decryptionKeys: KeysetWithSecrets) => { | ||
| assert(this.selfAssignRoles.includes(roleName), `Cannot self-assign role ${roleName}`) |
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.
I think this is the wrong place to do this. This is essentially trusting people to self moderate. I think the correct place to do this is in membershipResolver:membershipRules so that peers can enforce the rules themselves and throw out invalidated links.
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.
I'm gonna do it there, too, that piece is just more complicated and this blocks the lockbox creation, too.
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.
I wanted to take more time to look at the implications of blocking updates to the chain on these sorts of checks but didn't wanna delay being able to test self-assigns.
375c8ec to
9997e86
Compare
No description provided.