Score:0

storing private key on the client-side (with and without Web Cryptography API)

pk flag

I'm trying to understand what are my options(and best practices) regarding storing private key on the client-side.

There's a Web Cryptography API that can generate pair of keys with non-extractable abilities. I don't know exactly what it means, but I couldn't find a way to use it with my own pair of keys(private/public) anyways - is it even possible?

How can I implement something similar to it by myself to make it work cross-browser/application(without Web Cryptography API)?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.