Should be, although some versions of the linker don't gc-sections hard enough,
so you wind up with functions that never get called in your libnss3.so. If the
toolchain's linker has that bug, you won't see any win from it. See:
https://sourceware.org/bugzilla/show_bug.cgi?id=12975
https://bugzi
Is #1 something we can backport to b2g-2.0?
- Kyle
On Fri, Jun 27, 2014 at 8:56 AM, Nathan Froyd wrote:
> Hi all,
>
> Two changes to how NSS is built for Firefox's purposes have landed recently:
>
> 1. Bug 1018375 changed our build process on Android/B2G such that the
> libnss3.so that we build
On Fri, Jun 27, 2014 at 9:19 AM, David Keeler wrote:
> On 06/27/2014 07:37 AM, Nathan Kinder wrote:
> > On 06/27/2014 12:13 AM, Frederik Braun wrote:
> >> To be frank, I have only ever seen the non-standard crypto functions
> >> used in attacks, rather than in purposeful use.
> >
> > That doesn't
On 06/27/2014 07:37 AM, Nathan Kinder wrote:
> On 06/27/2014 12:13 AM, Frederik Braun wrote:
>> To be frank, I have only ever seen the non-standard crypto functions
>> used in attacks, rather than in purposeful use.
>
> That doesn't mean that aren't being purposefully used. The current
> crypto f
On 06/27/2014 05:11 AM, Jürgen Brauckmann wrote:
> David Keeler schrieb:
>> Meanwhile, we are making progress on implementing the webcrypto
>> specification[3]. When complete, webcrypto should provide compatible
>> functionality for what these functions are currently being used to do.
>> Any functi
Hi all,
Two changes to how NSS is built for Firefox's purposes have landed recently:
1. Bug 1018375 changed our build process on Android/B2G such that the
libnss3.so that we build there now has proper symbol exports applied to it.
This change enables the linker to discard any functions and/or
On 06/27/2014 12:13 AM, Frederik Braun wrote:
> To be frank, I have only ever seen the non-standard crypto functions
> used in attacks, rather than in purposeful use.
That doesn't mean that aren't being purposefully used. The current
crypto functions are used pretty heavily by Dogtag Certificat
David Keeler schrieb:
> Meanwhile, we are making progress on implementing the webcrypto
> specification[3]. When complete, webcrypto should provide compatible
> functionality for what these functions are currently being used to do.
> Any functionality not implementable using webcrypto is available
To be frank, I have only ever seen the non-standard crypto functions
used in attacks, rather than in purposeful use.
+1 to unimplement.
On 26.06.2014 22:40, David Keeler wrote:
> [dev.platform cc'd for visibility - please follow-up to dev.tech.crypto]
>
> Summary:
> We intend to remove the propr
9 matches
Mail list logo
