Timeline for Can third-party authentication yield a static user-specific encryption key?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24, 2022 at 7:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 24, 2022 at 6:41 | answer | added | CBHacking | timeline score: 1 | |
| Apr 24, 2022 at 4:29 | comment | added | Steffen Ullrich | The only information you get from third-party authentication is basically that the authentication was successful. This information by its own is not sufficient to derive a key. You might avoid asking the user again for the passphrase if the passphrase is already stored on the client side (maybe in local storage, maybe additionally protected with a server side secret) and you can ask the user to provide it using some Javascript. | |
| Apr 24, 2022 at 4:25 | comment | added | Steffen Ullrich | I've removed the term "private key" since it is usually associated with the concept of public key cryptography - which is both unsuitable by its own to encrypt larger documents and which you don't seem to want to use anyway. Instead it is now talking about user "user-specific key" only to avoid such confusion when reading your question. | |
| Apr 24, 2022 at 4:24 | history | edited | Steffen Ullrich | CC BY-SA 4.0 |
deleted 3 characters in body; edited title
|
| Apr 23, 2022 at 19:01 | history | edited | RatherBeLunar | CC BY-SA 4.0 |
added 194 characters in body
|
| S Apr 23, 2022 at 18:38 | review | First questions | |||
| Apr 23, 2022 at 18:43 | |||||
| S Apr 23, 2022 at 18:38 | history | asked | RatherBeLunar | CC BY-SA 4.0 |