Workaround for #192
Workaround for #192

For the real fix, we should maybe not login during KeyGen.Run()

And that being said, maybe we need to revamp KeyGen altogether

keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client,keybase/client