Timeline for Secure encryption algorithm with decryption key per user
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 9:49 | history | edited | CommunityBot |
Commonmark migration
|
|
| Nov 3, 2016 at 9:21 | comment | added | David P | @XiongChiamiov Yes it is something like a DRM we are talking about. We have rewritten the example to be more understandable. | |
| Nov 3, 2016 at 9:19 | history | edited | David P | CC BY-SA 3.0 |
re-written example
|
| Nov 2, 2016 at 18:53 | answer | added | John Deters | timeline score: 1 | |
| Nov 2, 2016 at 18:16 | comment | added | Xiong Chiamiov | What this sounds like to me is a form of DRM: instead of trying to control access to the files, you let everyone have them in encrypted form, and control just the decryption keys. Is that right? | |
| Nov 2, 2016 at 16:26 | comment | added | Mr. E | I don't get it. Are all the files the same for all users? If it is,why you need a key per user? What about encrypting the files with AES and give the user the AES key encrypted with the user's public key? | |
| Nov 2, 2016 at 16:21 | comment | added | David P | @Mr.E because it would be costly to encrypt the file each file, and store the file in the p2p platform, each time an user buys the access. | |
| Nov 2, 2016 at 16:12 | comment | added | Mr. E | If the person who buys the access has a public and a private key why don't encrypt the files with his public key and let him decrypt it with his private key? | |
| Nov 2, 2016 at 15:52 | history | edited | David P | CC BY-SA 3.0 |
added 42 characters in body
|
| Nov 2, 2016 at 15:29 | history | edited | David P | CC BY-SA 3.0 |
added 40 characters in body
|
| Nov 2, 2016 at 15:24 | review | First posts | |||
| Nov 2, 2016 at 16:39 | |||||
| Nov 2, 2016 at 15:22 | history | asked | David P | CC BY-SA 3.0 |