search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.82k stars 1.22k forks source link

Link signer does not have permission to rotate key #10308

Open dbd opened 6 years ago

dbd commented 6 years ago

Unable to post messages to a team or sub team. When I try to review them with the following command I receive the following error.

bash-3.2$ keybase team show-tree mtu
▶ ERROR appending 31->32: link signer does not have permission to rotate key: {{d9065d6da185ec28758619fc14b75519 69} false} is a READER
maxtaco commented 6 years ago

Thanks for the bug report. Can you keybase log send. Also, what were you in the process of doing?

dbd commented 6 years ago

Sorry about that brevity of the first message, hit enter to return line. This is affecting everyone in the team.

my log id: 5cdee6a5acc5140f1a5e1f1c

maxtaco commented 6 years ago

Hmm ok, thanks for the info, we'll take a look. It's certainly a bug somewhere, we'll have to figure out what/where.

maxtaco commented 6 years ago

Can you try keybase db nuke and then try it again?

maxtaco commented 6 years ago

We think we found the bug, your subteam is likely going to be broken until we push a release. The bug is in our "team player" so it'll work once a new release is out. Sorry about that and thanks for your feedback!

dbd commented 6 years ago

It looks like there is a similar problem with the base team and we are unable to see the directory for the base team. Is the base team affected by the sub team is this another issue?

Do you still want me to do the db nuke?

Thanks for your quick response!

maxtaco commented 6 years ago

I think the db nuke will not help...

Cc: @mlsteele

mlsteele commented 6 years ago

@dbd Doing db nuke won't help the subteam, need a new release for that.

For the base team, I did not see a similar failure in your logs. You said that /keybase/team/mtu doesn't show up? Do other team folders work?

keybase team show-tree mtu will continue to fail as long as the subteam is busted unfortunately. keybase team list-members mtu should work even if the subteam is broken, as a quick way to test whether things are working at all.

dbd commented 6 years ago

Sounds good, list-members worked as expected as you mention. I'll just wait and test the later release. Thanks guys!

mlsteele commented 6 years ago

Ok, great. If you're having any issues with the root team folder now there's a good chance it's a separate issue. So that would be good to know.

BrandonIngalls commented 6 years ago

@mlsteele

I am the owner of the mtu team, and I have lost the ability to change users roles of the root team.

[~]$ keybase team edit-member mtu -u dbd -r admin
▶ ERROR appending 31->32: link signer does not have permission to rotate key: {{d9065d6da185ec28758619fc14b75519 69} false} is a READER

Log Id: 7466430997ce6f2b0589cb1c

mlsteele commented 6 years ago

@BrandonIngalls Oh, I see. Admins need to be keyed for all subteams, and your client can't read the subteam, so it fails. This will all be fixed in the upcoming release! I've tested your case specifically.

You can still set people to below-admin roles, fwiw.

jrespeto commented 6 years ago

Have the same issue joining an open team redhat.public.

screen shot 2018-01-27 at 12 28 38 pm

error_keybase

Then try to leave the team get the same error.

keybase team leave redhat.public ▶ ERROR appending 35->36: link signer does not have permission to rotate key: {{a37f05ea8eca22a2fbe7fbb516752d19 1} false} is a READER

Success! Your log ID is:

5b1ae2237edb72318dc1841c

Here's a URL to submit new bug reports containing this ID:

https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%205b1ae2237edb72318dc1841c

Thanks

derekbelrose commented 6 years ago

I, too, am seeing the same problem with redhat.public:

log: 2a308ea53a5622b27c4e3c1c