Open ssemenova opened 5 years ago
Cc @zapu did we recently have this bug?
@ssemenova I think it is because your account was established a very long time ago and we made some changes that broke this vintage.
I assume you can see this, but @ssemenova's account was created 2018-03-25, which is not exactly forever ago. Mine is 2014-03-14, and my account is working OK.
Ah thanks. I was tapping on my phone so didn’t see that.
@eblanton do you and @ssemenova share a computer?
Negative. We simply work together.
@ssemenova : can you maybe try this from the CLI:
keybase logout
keybase login novasofiya
@maxtaco No. I did get a new computer a few months ago (I think this is my first time logging out of it) and had to add it as a new device to my account, but I'm not sure that would cause this.
... I'm guessing that's not going to work... This is somewhat of a surprise, but it looks as if your secret key file has been corrupted.. It might be necessary to revoke the device and then reprovision it again. You won't lose any data, but it's annoying...
@maxtaco Yeah, your guess was right, it didn't work. I have no idea how the file could have become corrupted but I can revoke the device and try to reprovision.
@maxtaco Yep, that worked. Thank you!
Logging into the mac client, I get the error "Login failed after passphrase verified". This is a distinctly different error than the error I get if typing in an incorrect passphrase.
I can log into the web client with the same passphrase with no errors. My PGP key is stored with keybase, and using the web client, I can successfully encrypt and decrypt messages with other users.
I tried, to no avail:
I have not tried logging out of my other device and attempting to log in again just in case I'm locked out of both devices and can't easily access my chats again. Looking up this error on google, both people who had this issue previously have had success with deleting all their keys and starting over, but I'd like not to do that if possible.
my log id, by just running "keybase log send": 564177cfa2822ea3c2d2a91c my log id, by running "keybase log send" immediately after attempting to log in: 361ccee1fa4171128a338d1c