Re: [HTTPS-Everywhere] Verifying signatures in a FF extension?

2014-07-04 Thread Yan Zhu
At a glance, it seems like your signature string is not properly encoded. The first bytes should be "MII" for a Base64 encoding of a DER-encoded signature. Unfortunately I don't think I can make the usual IRC meeting tonight because I'm in France - let's try to meet on Monday instead? -Yan On 07

Re: [HTTPS-Everywhere] Verifying signatures in a FF extension?

2014-07-04 Thread Red
I appreciate the suggestion. I'll play around with the encodings of the key and signature a bit and see if doing so leads to a solution. It's fine with me if we delay our meeting to Monday. Hopefully by then I'll have this test working. Cheers, Zack On 2014-07-04, 2:02 AM, Yan Zhu wrote: > At a

Re: [HTTPS-Everywhere] Verifying signatures in a FF extension?

2014-07-04 Thread Red
I've been looking into the options available to the `openssl dgst` and `openssl rsautl` commands, and can't find anything regarding DER-encoding of signatures. I have already found that keys can be der-encoded, and that going on to base64-encoding those keys (obviously) produces the same result as

Re: [HTTPS-Everywhere] Verifying signatures in a FF extension?

2014-07-04 Thread Yan Zhu
One idea is to look through the signing code from Uhura (command line signing utility for Mozilla extensions): http://www.softlights.net/download.html. This should make the correct signature format, since we use it to generate the signature field in update.rdf for HTTPS Everywhere. Actually, it lo

Re: [HTTPS-Everywhere] Verifying signatures in a FF extension?

2014-07-04 Thread Vijay P
You guys might want to look at keybase.io -- their strategy for verification of public keys is really nice (look at public locations such as twitter) and they have an api that can sign and verify directories nicely. On Thu, Jul 3, 2014 at 1:00 AM, Red wrote: > Hello everyone, > I've been work

Re: [HTTPS-Everywhere] Verifying signatures in a FF extension?

2014-07-04 Thread Red
On 2014-07-04, 3:57 PM, Yan Zhu wrote: > One idea is to look through the signing code from Uhura (command line > signing utility for Mozilla extensions): > http://www.softlights.net/download.html. This should make the correct > signature format, since we use it to generate the signature field in >