Hi, We are working for a bank that implements a plugin for signing login and transactions in an e-banking solution. This is a key part of the application, it supports the three major browsers (FF and IE through npapi, Chrome through native messaging). When we investigated the problem half-a-year ago, the FF implementation of the Crypto API was not suitable, since the most important use-case (for each operation, PIN has to be entered) could not be enforced.
Therefore, we still use the plugin to do all the stuff necessary for signing transactions, and managing functionalities (PIN change, etc). If any of you have some wisdom regarding this matter, please advice, it will be much appreciated. Thanks, Peter _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
