On 10/20/2010 06:29 PM, Brian Smith wrote: >> Brian Smith wrote: >> >>> (Because of Firefox Sync, we are now always going to have crypto >>> features that won't work in FIPS mode.) >>> >> Sigh, ignoring FIPS mode in a feature, is usually a red flag. It means >> you are handling CSP's where you really shouldn't be. Firefox Sync >> *CAN* be implemented in FIPS mode, and we should work to make sure >> that happens. >> > Because of the way key exchange and key entry are done in Firefox Sync, even > if it worked in FIPS mode, it wouldn't be FIPS compliant. Because of > usability constraints, Sync will use an unapproved key exchange mechanism > (J-PAKE). And, it also allows manual key entry. For compatibility with > previous versions we also have to support encryption/authentication keys > derived from weaker keys via PBKDF2, though the new Sync crypto design will > avoid PBKDF2 for new users. > OK, use of standard, but non-FIPS algorithms are fine. It's really the key management portions that are a bigger issue. (Of course to users that require FIPS it's not, but that's not the context we are talking about here;).
bob
-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
