Identity/WeeklyMeeting/2011-10-24: Difference between revisions
< Identity | WeeklyMeeting
Jump to navigation
Jump to search
(→Dev) |
(→Dev) |
||
Line 11: | Line 11: | ||
* Error values for all network calls, working on a better abstraction/generalizing. | * Error values for all network calls, working on a better abstraction/generalizing. | ||
* In review on {{bug|665057}} "Design and implement crypto API for Mozilla ID", should have a patch for ID team to play with very soon -ddahl | * In review on {{bug|665057}} "Design and implement crypto API for Mozilla ID", should have a patch for ID team to play with very soon -ddahl | ||
* {{bug|440046}} is very close to r+ (window.crypto.getRandomValues) | |||
* {{bug|673432}} "Implement window.crypto.getRandomValues for e10s/mobile" is in smaug's review queue, already has f+ from mfinkle -ddahl | |||
= Security & Privacy = | = Security & Privacy = |
Revision as of 16:08, 24 October 2011
Last Week's Actions
- roadmap needed
- post-mortem on security bug, plus script
Major Progress
Dev
- Android 2.2, 2.3 support
- Lots of smoothing out rough edges
- Error values for all network calls, working on a better abstraction/generalizing.
- In review on bug 665057 "Design and implement crypto API for Mozilla ID", should have a patch for ID team to play with very soon -ddahl
- bug 440046 is very close to r+ (window.crypto.getRandomValues)
- bug 673432 "Implement window.crypto.getRandomValues for e10s/mobile" is in smaug's review queue, already has f+ from mfinkle -ddahl
Security & Privacy
Ops
QA
- The 10/13/2011 Train made it successfully through Beta last week
- QA is now working on our tenth train:
- Bug 696415 - QA and deploy BrowserID train-2011.10.20 to production
- QA to get some help from Lloyd on the BrowserID install issues on our ID2 VM.