Jeremy Stribling

All: we have "lockdown" mode now, which gives you the benefits of 2FA without having to deal with codes: https://keybase.io/docs/lockdown/index

@programehr can you please share more info about what operation system you're running on, and what version/distribution of git you're using? And running `keybase log send` and posting the resulting...

Are you using cygwin or some other non-standard terminal when you're running the commands?

Not familiar with that one. Does `git-remote-keybase.exe` exist in an executable location?

That's the same location as your `keybase.exe`, which I assume works fine in this shell. In the past, there was a user who fixed a similar issue by restarting bash...

Ok, thanks for the update. That's not really a great solution since it won't get updated when we put out new releases. You might want to do some more investigation...

Weird. Yeah from this log snippet I agree that it appears to be a network connection initialization issue, which definitely points to your VPN. I know nothing about TunnelBear though....

Weird. Sorry I don't know any tips for debugging TunnelBear. On our end, we don't do anything funny as far as I know with accepting connections from VPNs. Everything is...

@eli-schwartz this is working as intended. `kbfsfuse` is not supposed to create any directories, esp. since the parent dirs may have to be made as root (such as `/run/user/$UID`). Note...

I understand your points, but that's not the way we've viewed it historically. We consider `run_keybase` to be part of our official distribution and a required part of running things....