CE causes issues with Keybase

  • 2
  • Problem
  • Updated 2 years ago
Apparently, CE makes it impossible for Keybase to set up on a Windows desktop.  On the lateset beta (7.2.4), I believe the SSL proxy interferes with the login flow.  In versions no later than 7.2.0 (but possibly earlier), the RPC between Keybase and GPG is interrupted somehow.

Please see GitHub issues keybase/client#3486 and keybase/client#4041.  I'm still investigating a bit, but if you can reproduce, that would be great.
Photo of aggieben

aggieben

  • 58 Posts
  • 8 Reply Likes

Posted 2 years ago

  • 2
Photo of aggieben

aggieben

  • 58 Posts
  • 8 Reply Likes
Has anyone been able to look at this?  I had to uninstall CE to finally install Keybase, and then reinstall CE afterwards.  Obviously this is ....not ideal.

I'm now finding additional errors that seem to be related to the CE proxy service:




as of the last week or so, keybase will simply not connect. 

Also, the Facebook Windows 10 app seems to be hosed on certificate verification, which strikes me as highly likely to be caused by the CE proxy:
Photo of BarneyFifeFan

BarneyFifeFan

  • 18 Posts
  • 1 Reply Like
I haven't had the issue with Keybase specifically (although I do use it), but there is a much more general issue with the CE proxy. A lot of applications (for instance, Opera Developer) detect that CE is un-encrypting traffic with a local cert, and it trips up a bunch of security related features. In all honesty, there has to be a better way to do this than to proxy everything and de-encrypt it. I may be taking a shot in the dark here, but isn't there some sort of Windows API that would enable you to monitor URLs without inserting a proxy?