Open kennygx opened 6 years ago
UPDATE:
Those cert errors are probably innocuous. I just created a new directory, /keybase2, and it worked fine. I guess something got borked with my original directory.
You have to update your client software.
On Sat, Nov 4, 2017 at 9:33 AM kennygx notifications@github.com wrote:
UPDATE:
Those cert errors are probably innocuous. I just created a new directory, /keybase2, and it worked fine. I guess something got borked with my original directory.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/keybase/client/issues/9388#issuecomment-341897314, or mute the thread https://github.com/notifications/unsubscribe-auth/AA05_7X2OcXR8qQVtpmQQOv3N6QM0E9kks5szGejgaJpZM4QSAgf .
Thanks. I'll do that.
cc: @songgao and @strib
My guess is the same as your @maxtaco, the first mount was likely done with a version of the kbfs
repo that is too old. Maybe @kennygx updated it before the second mount? In any case, just update your kbfs repo and the cert error should go away.
I receive errors like this when running kbfsfuse:
▶ WARNING (CONN MDServerRemote e9a7ea08) Connection: error dialing transport: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "Keybase KBFS CA prod")
my log id: 8f2d513a4214eedcd404471c