|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Well, apart from the typed arrays compatibility, it is clear that AeroGear JS Crypto does not support browsers which does not implement the Web Crypto API.
The Web Crypto API getRandomValues() compatibility map (http://stackoverflow.com/questions/16084766/compatibility-of-window-crypto-getrandomvalues) is:
IE: no
IE Mobile: no
Firefox: will be in 21
Firefox Mobile: will be in 21
Safari: from 3.1
Safari Mobile: from iOS 6
Chrome: from 11
Chrome for Mobile: from 23
Android browser (before 4.0 as replaced with Chrome): no
Opera: no (though will probably get it when moving to WebKit)
Opera Mobile: no
Opera Mini: no
In conclusion I think that this issue is acceptable and cannot be fixed. If the Web Crypto API is not supported then encryption does not make sense since the random value will not be cryptographically strong. Even the polyfill of Web Crypto does not support Android browser (https://github.com/polycrypt/polycrypt).