Which version are we thinking of enabling this for? For Gecko
34/FirefoxOS 2.1 or a later version?
On Wed, Sep 3, 2014 at 10:36 AM, Tim Taubert wrote:
> As of September we intend to enable the WebCrypto API by default on all
> platforms. It has been developed behind the dom.webcrypto.enabled
> pr
On 2014-09-09, 7:25 AM, Anne van Kesteren wrote:
On Tue, Sep 9, 2014 at 12:48 PM, Tim Taubert wrote:
Completely agree with Ehsan and Henri. I don't know of any plans to even
consider doing that and we currently expose the WebCrypto API to
unauthenticated origins as well.
Note https://www.w3.o
On 2014-09-09, 6:35 AM, Tim Taubert wrote:
Ehsan Akhgari wrote:
Can you please clarify what are the areas that we don't fully adhere to
the spec? Do we expect the fixes to those and potentially new spec
issues in the future to break backwards compatibility?
KeyAlgorithms were recently changed
On 9/9/2014 5:38 AM, Tim Taubert wrote:
helpcrypto helpcrypto wrote:
I'll love to know if Mozilla/Firefox is going to provide something (even
out-of-standard) to make possible using PKCS#11/NSS with Webcrypto.
The WebCrypto API basically exposes PKCS#11/NSS functionality with a DOM
API.
The c
Thanks for your answers, Tim.
On Tue, Sep 9, 2014 at 12:38 PM, Tim Taubert wrote:
> helpcrypto helpcrypto wrote:
> > I'll love to know if Mozilla/Firefox is going to provide something (even
> > out-of-standard) to make possible using PKCS#11/NSS with Webcrypto.
>
> The WebCrypto API basically ex
On Tue, Sep 9, 2014 at 12:48 PM, Tim Taubert wrote:
> Completely agree with Ehsan and Henri. I don't know of any plans to even
> consider doing that and we currently expose the WebCrypto API to
> unauthenticated origins as well.
Note https://www.w3.org/Bugs/Public/show_bug.cgi?id=25972 which I
fi
Anne van Kesteren wrote:
> In Chromium the methods only work on authenticated origins. What is
> our story?
Completely agree with Ehsan and Henri. I don't know of any plans to even
consider doing that and we currently expose the WebCrypto API to
unauthenticated origins as well.
> Is the non-overl
Dirkjan Ochtman wrote:
> Is there a list of algorithms we support somewhere, particularly the
> ones we share with Chromium? IIRC the supported algorithms is where
> the real interop problems are expected to be. (I quickly searched MDN,
> but that didn't turn up anything useful.)
Richard Barnes ma
helpcrypto helpcrypto wrote:
> I'll love to know if Mozilla/Firefox is going to provide something (even
> out-of-standard) to make possible using PKCS#11/NSS with Webcrypto.
The WebCrypto API basically exposes PKCS#11/NSS functionality with a DOM
API.
> This will fill the gap that currently exist
Ehsan Akhgari wrote:
> Can you please clarify what are the areas that we don't fully adhere to
> the spec? Do we expect the fixes to those and potentially new spec
> issues in the future to break backwards compatibility?
KeyAlgorithms were recently changed to dictionaries (from interfaces)
and we
On Thu, Sep 4, 2014 at 6:29 PM, Ehsan Akhgari wrote:
> On 2014-09-04, 4:42 AM, Anne van Kesteren wrote:
>>
>> On Wed, Sep 3, 2014 at 7:36 PM, Tim Taubert wrote:
>>>
>>> Chromium has had the WebCrypto API enabled by default since Crome 37,
>>> which was released in late June 2014. Their implementa
On 2014-09-04, 4:42 AM, Anne van Kesteren wrote:
On Wed, Sep 3, 2014 at 7:36 PM, Tim Taubert wrote:
Chromium has had the WebCrypto API enabled by default since Crome 37,
which was released in late June 2014. Their implementation supports a
subset of the algorithms that we do, and has roughly th
On Wed, Sep 3, 2014 at 7:36 PM, Tim Taubert wrote:
> Chromium has had the WebCrypto API enabled by default since Crome 37,
> which was released in late June 2014. Their implementation supports a
> subset of the algorithms that we do, and has roughly the same level of
> spec compliance. We expect t
On Wed, Sep 3, 2014 at 7:36 PM, Tim Taubert wrote:
> Chromium has had the WebCrypto API enabled by default since Crome 37,
> which was released in late June 2014. Their implementation supports a
> subset of the algorithms that we do, and has roughly the same level of
> spec compliance. We expect t
I'll love to know if Mozilla/Firefox is going to provide something (even
out-of-standard) to make possible using PKCS#11/NSS with Webcrypto.
This will fill the gap that currently exist with hardware token support
(which, is going to be discussed nexr 10th September)
Regards.
__
I'm excited to see this finally happen!
Can you please clarify what are the areas that we don't fully adhere to
the spec? Do we expect the fixes to those and potentially new spec
issues in the future to break backwards compatibility?
Thanks!
Ehsan
On 2014-09-03, 1:36 PM, Tim Taubert wrote:
As of September we intend to enable the WebCrypto API by default on all
platforms. It has been developed behind the dom.webcrypto.enabled
preference.
Tracking bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=865789
Spec:
https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html
(A CR
17 matches
Mail list logo
