HTTPS support

[mbarulli]

Hi Tagide, great job, this is a very much needed extension!

I've configured clipperz.bit to work both on http and https using the following configuration:

{
    "ip": "46.149.20.251",
    "fingerprint": "27:6B:76:B0:43:08:41:94:88:CB:7A:8C:46:BF:EF:8C:19:D7:A3:76"
}

https works when using FreeSpeechMe, but not with other approach. Your extension returns

ERR_PROXY_CERTIFICATE_INVALID

What is missing to your extension to validate fingerprints?

Thanks! Marco

[Tagide]

Thank you! I would love to get https working but cannot find a solution. If you have any ideas, please let me know

[mbarulli]

I'm afraid I'm not qualified to provide valuable ideas.

My understanding is that you should get the SLL certificate from the IP contained in the namecoin record and verify it using the fingerprint contained in the same namecoin record before establishing the SSL channel.

Support Clipperz, donate now! https://clipperz.is/donations

Marco Barulli email: [email protected] mobile: +39 348 2476970 skype: mbarulli

On Mon, Mar 17, 2014 at 1:59 PM, Tagide [email protected] wrote:

Thank you! I would love to get https working but cannot find a solution. If you have any ideas, please let me know

— Reply to this email directly or view it on GitHubhttps://github.com/Tagide/chrome-bit-domain-extension/issues/2#issuecomment-37812049 .

[mbarulli]

Any update?

[Tagide]

Sorry no, I have not found any solution.

2014-04-09 22:43 GMT+02:00 Marco Barulli [email protected]:

Any update?

— Reply to this email directly or view it on GitHubhttps://github.com/Tagide/chrome-bit-domain-extension/issues/2#issuecomment-40013958 .

[bryanph]

There is no API in chrome for handling certificates differently. I suppose without support for chrome and other major browsers, things like this will never take off.

https://code.google.com/p/chromium/issues/detail?id=93636 https://www.imperialviolet.org/2011/09/07/convergence.html