Difference between revisions of "Crypto API"
From MgmtWiki
(→Full Title or Meme) |
(→Full Title or Meme) |
||
Line 1: | Line 1: | ||
==Full Title or Meme== | ==Full Title or Meme== | ||
+ | The ability of any [[Progressive Web App]] to access cryptography engines on the device. | ||
+ | |||
+ | ==Context== | ||
* [https://www.coindesk.com/markets/2017/09/16/bitcoin-in-the-browser-google-apple-and-more-adopting-crypto-ready-api/ Bitcoin in the Browser: Google, Apple and More Adopting Crypto-Ready API] 2017-09-16 | * [https://www.coindesk.com/markets/2017/09/16/bitcoin-in-the-browser-google-apple-and-more-adopting-crypto-ready-api/ Bitcoin in the Browser: Google, Apple and More Adopting Crypto-Ready API] 2017-09-16 | ||
+ | |||
+ | ==Problems== | ||
+ | * Any web site can download a [[Progressive Web App]] for use whether or not the user chooses to "install" it and thereby pretend to be the user. | ||
+ | * If a wallet is installed by a web site, there is no way for another site to use it by sharing cookies as that has been blocked since 2022. | ||
==References== | ==References== |
Revision as of 12:45, 10 March 2022
Full Title or Meme
The ability of any Progressive Web App to access cryptography engines on the device.
Context
Problems
- Any web site can download a Progressive Web App for use whether or not the user chooses to "install" it and thereby pretend to be the user.
- If a wallet is installed by a web site, there is no way for another site to use it by sharing cookies as that has been blocked since 2022.
References
- Also see this wiki page PWA initiators for implementing in a Progress Web page.