Open midnightmagic opened 10 years ago
Haven't tried this but it might be because api.keybase.io:443 appears self-signed to tor exit-nodes who don't have the CA that we ship with the client.
Tor exit-nodes don't MITM an SSL connection; the client-side itself verifies as normal the cert against signing authorities. Is there a cert that the client is specifically using? Perhaps I did the install incorrectly, I did it semi-manually because I didn't want to install as root.
I am trying to use keybase on a NetBSD machine (running node.js built from pkgsrc) using a non-root user on a Tor-connected machine via "torify" and it doesn't seem to like that very much:
-bash-4.2$ torify keybase login warn: No config file found; tried '/home/keybase/.keybase/config.json' Your keybase username or email: midnightmagic Your keybase login passphrase: *** error: socket hang up -bash-4.2$
Not sure why.
I'd prefer to use the service over Tor completely. Please consider testing against a torify'd command-line.