search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

Cryptic error message "ppgen assertion failed before update (error 1407) #2070

Open yipal opened 8 years ago

yipal commented 8 years ago

I tried to login on a new device with my paper key. I'm not sure if this error means I typed the paper key in wrong, or if something else is wrong, but the next time I tried "keybase login", I was able to login with my keybase password alone.

alex@alex-T60:~$ keybase login How would you like to sign this install of Keybase?

(1) Use an existing device (2) Use a paper key (3) Use my Keybase passphrase Choose a signing option: 2 Please enter a paper backup key passphrase for your account: Enter a public name for this device: t60 ▶ ERROR ppgen assertion failed before update (error 1407)

strib commented 8 years ago

Hey @yipal -- for what it's worth, according to https://keybase.io/yipal/graph you did add your t60 device using your paper key. So I guess you typed it correctly. Not sure about that scary error message -- maybe @maxtaco or @patrickxb recognize it?

maxtaco commented 8 years ago

This is likely a bug!!!!

On Saturday, February 13, 2016, Jeremy Stribling notifications@github.com wrote:

Hey @yipal https://github.com/yipal -- for what it's worth, according to https://keybase.io/yipal/graph you did add your t60 device using your paper key. So I guess you typed it correctly. Not sure about that scary error message -- maybe @maxtaco https://github.com/maxtaco or @patrickxb https://github.com/patrickxb recognize it?

— Reply to this email directly or view it on GitHub https://github.com/keybase/keybase-issues/issues/2070#issuecomment-183613788 .

maxtaco commented 8 years ago

I put a ticket in Jira, I'll take a look when I can. Thanks @yipal!

maxtaco commented 8 years ago

Alex when you get a chance can you do a 'keybase log send' on the t60?

Btw have you ever changed your password on keybase? I can look it up on the DB but while I am thinking about it was just curious.

On Saturday, February 13, 2016, Maxwell Krohn themax@gmail.com wrote:

This is likely a bug!!!!

On Saturday, February 13, 2016, Jeremy Stribling <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

Hey @yipal https://github.com/yipal -- for what it's worth, according to https://keybase.io/yipal/graph you did add your t60 device using your paper key. So I guess you typed it correctly. Not sure about that scary error message -- maybe @maxtaco https://github.com/maxtaco or @patrickxb https://github.com/patrickxb recognize it?

— Reply to this email directly or view it on GitHub https://github.com/keybase/keybase-issues/issues/2070#issuecomment-183613788 .

yipal commented 8 years ago

Ok, I uploaded the logs with ID: cdc1fe060084c5b72fabf01c

I did change my keybase password once, but I may have changed it to the same value.

maxtaco commented 8 years ago

@yipal looks like your passphrase update was botched. Can you remember how you went about changing it? Did you use the CLI or the website? Did you reset or just update? Thanks, sorry about this!

yipal commented 8 years ago

I changed my password on the keybase website. I may have chosen the same password as the original password though. I don't know what the difference is between reset and upgrade.

maxtaco commented 8 years ago

Thanks for writing in @yipal. I've repro'ed the bug. There's definitely an issue here. When I make a little more progress I'll try to manually fix your account. BTW, are you having any residual issues?

yipal commented 8 years ago

I haven't tried to use it since then, but I'll update this bug report if I notice anything wrong.

coen-hyde commented 7 years ago

@maxtaco I just received this error provisioning a new device via a paper key. I saw #2524 first. Where keybase logout ; keybase login was suggested. When i try that, i get the error Wrong LKSec server length: 0 != 32. keybase db nuke doesn't seem to help. Some system info:

KBFS:
    status:    running
    version:   1.0.2-20161219190010+1335f5b
    log:       /Users/coenhyde/Library/Logs/keybase.kbfs.log

Service:
    status:    running
    version:   1.0.18-20161219185928+7868d49
    log:       /Users/coenhyde/Library/Logs/keybase.service.log

Updater:
    log:       /Users/coenhyde/Library/Logs/keybase.updater.log

Platform Information:
    OS:        darwin
    OS vers:   10.12.2-16C67
    Runtime:   go1.7.4
    Arch:      amd64

Client:
    version:   1.0.18-20161219185928+7868d49

Desktop app:
    status:    running
    version:   1.0.18-20161219185928+7868d49
    log:       /Users/coenhyde/Library/Logs/Keybase.app.log
maxtaco commented 7 years ago

That is a new one as far as I am concerned. Please do a keybase log send and I will try to take a look when I get back to the office on Thursday but it might be low priority since I will have a lot to catch up on. Thanks for the feedback.

Cc @patrickxb

On Mon, Dec 26, 2016 at 9:23 PM Coen Hyde notifications@github.com wrote:

@maxtaco https://github.com/maxtaco I just received this error provisioning a new device via a paper key. I saw #2524 https://github.com/keybase/keybase-issues/issues/2524 first. Where keybase logout ; keybase login was suggested. When i try that, i get the error Wrong LKSec server length: 0 != 32. keybase db nuke doesn't seem to help. Some system info:

KBFS:

status:    running

version:   1.0.2-20161219190010+1335f5b

log:       /Users/coenhyde/Library/Logs/keybase.kbfs.log

Service:

status:    running

version:   1.0.18-20161219185928+7868d49

log:       /Users/coenhyde/Library/Logs/keybase.service.log

Updater:

log:       /Users/coenhyde/Library/Logs/keybase.updater.log

Platform Information:

OS:        darwin

OS vers:   10.12.2-16C67

Runtime:   go1.7.4

Arch:      amd64

Client:

version:   1.0.18-20161219185928+7868d49

Desktop app:

status:    running

version:   1.0.18-20161219185928+7868d49

log:       /Users/coenhyde/Library/Logs/Keybase.app.log

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/keybase-issues/issues/2070#issuecomment-269259254, or mute the thread https://github.com/notifications/unsubscribe-auth/AA05_0HoxQbaXupUyTOGHsb9-PJXFW_nks5rMHaWgaJpZM4HZk5T .

coen-hyde commented 7 years ago

Thanks @maxtaco. Log send id: 70a4707f355e38876d25061c

maxtaco commented 7 years ago

Looks like there was an issue provisioning your most recent device, enceladus. Looking into it...

maxtaco commented 7 years ago

@coen-hyde do you remember the last time you successfully reset your passphrase? seems like we hit a bug with passphrase reset for your account here, and the server state is in a slightly broken state. I'm going to try to fix it for you. You probably need to revoke and encladus and reprovision, but luckily there are many more jovian moons to pick from :/

coen-hyde commented 7 years ago

Hi @maxtaco. I don't think i've ever reset my passphrase. Or if i have it was very close to when I first opened my account. I just tried a revoke and reprovision; same thing "ERROR ppgen assertion failed before update (error 1407)". Log send id: bf61f26de0e7d79302dac51c

coen-hyde commented 7 years ago

hi @maxtaco / @patrickxb. Sorry to bother you guys. I'm still unable to provision Keybase on my new mac. Do you have any idea's? I live in SF so if you would like to inspect / debug it I'm happy to meetup.

maxtaco commented 7 years ago

i thought about it for a while and didn't come up with any simple solutions. Do you have an data in KBFS?

coen-hyde commented 7 years ago

@maxtaco yeah, I use it pretty regularly from my other devices

maxtaco commented 7 years ago

Just getting back to this. Is your keybase password a one-off, or do you use it elsewhere? Could you potentially share it with me and then cycle it after i fix your account? I'm not fully sure this will work, but it might...

Alternatively, I might ask that you copy data out of KBFS, reset your account, reprovision your devices, redo your proofs, and then copy your data back in. An additional bummer in all this is that you won't be able to use your device names pre-reset.

maxtaco commented 7 years ago

I have one idea to try, let me see if it works....

maxtaco commented 7 years ago

ok, on your existing devices, please do keybase db nuke

then try to reprovision again....

totally uncharted waters and an untested theory, but worth a try...

coen-hyde commented 7 years ago

Woot. Thanks @maxtaco. Running keybase db nuke on my other devices seemed to fix the problem. I've provisioned a new device.

maxtaco commented 7 years ago

Awesome news

Gives me a lot of clues to look for the root bug too. Thanks!!!!!!

On Sat, Jan 21, 2017 at 7:05 PM Coen Hyde notifications@github.com wrote:

Woot. Thanks @maxtaco https://github.com/maxtaco. Running keybase db nuke on my other devices seemed to fix the problem. I've provisioned a new device.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/keybase/keybase-issues/issues/2070#issuecomment-274296931, or mute the thread https://github.com/notifications/unsubscribe-auth/AA05_yDFNMB37iCaHoDPZJYXyOvnUofOks5rUp1cgaJpZM4HZk5T .