Zoogtfyz,
On 5/6/2016 07:34, Zoogtfyz wrote:
Websites that prefer AES-256, such as internal websites, can always
instruct their users/customers to toggle a switch in Firefox to enable
AES-256. I am proposing having AES-256 ciphersuits toggled off by
default.
IMO, that is impractical. I would recommend against doing this.
It was discussed on the Chrome mailing list. They are not yet enabled by
default in Chrome stable, it is not yet decided if/when it will be enabled.
Nevertheless, other AES-256 cipher suites are already enabled in
Chrome. I don't think anyone is proposing to remove those from Chrome.
MO, we should not remove any AES-256 cipher suites from Firefox/NSS.
I would agree with the proposal to reorder them, however, and prioritize
AES-GCM over AES-CBC. Since application developers may have different
opinions about priority order of cipher suites, I think it would be
helpful to implement the following 2 NSS ERs which I filed recently :
https://bugzilla.mozilla.org/show_bug.cgi?id=1267894
https://bugzilla.mozilla.org/show_bug.cgi?id=1267896
Only the first one is related to Firefox, but both are related.
There are other considerations to take into account other than "strength".
Indeed, and those considerations might be application-specific, or
hardware-specific, which is why I think the above 2 ERs make sense to
implement.
When it comes to signature algorithms and curves, IMO, there should be
some runtime support for configuring them and prioritizing them.
Right now, AFAIK, we don't have any kind of runtime configuration for
either. Both are hardcoded at compile-time. IMO, it is time for this to
change.
We should have at the very least runtime APIs to to enable/disable
curves and enable/disable signature algorithms. Several other libraries
already offer this.
Preferably, we should also have a configurable ordered list for those,
as I'm proposing we add for cipher suites.
Julien
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
