keybase / keybase/keybase-issues

Unable to prove HTTPS (possibly due to cypher suite issues)

Open
#807 18 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Hi,

The keybase daemon currently reports my HTTPS prove to be broken. I am however able to obtain and verify it by following the link for the HTTP prove (http://burnus.net/keybase.txt), or using https:// respectively, and piping the result into `keybase verify`. My guess is that the issue has to do with the fact that my server only accepts a few carefully selected HTTPS cypher suites (TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030), TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) and TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)), which are not yet supported by all the SSL libraries. Can you please elaborate on which cypher suites you support on your end?

Thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the HTTPS prove failure for https://burnus.net/keybase.txt and compare it with the working HTTP prove and `keybase verify` flow. Investigate compatibility with the three listed TLS cipher suites; done means the supported suites and the cause of the failed HTTPS prove are documented or the prove succeeds.

Written by the indexing model from the issue text.

Assessment

Domain
networking, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.