Timeline for Does my receiver have a public key for email encryption?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2022 at 15:47 | comment | added | Esa Jokinen | Yes, but it is still better to evaluate an actual system than one's depiction of it. | |
| May 14, 2022 at 15:26 | vote | accept | Summit2 | ||
| May 14, 2022 at 15:26 | comment | added | Summit2 | Actually it wasn't relevant in the question because whatever their standard is (I understood that they've created their own modification of PGP), it is not the same for the receiver, so the answer would be the same - that the public key wouldn't be generated. | |
| May 14, 2022 at 14:07 | comment | added | Esa Jokinen | Exactly. If the encryption scheme is different from the standards like S/MIME (RFC 8551) & OpenPGP Message Format (RFC 4880), you should have mentioned it. | |
| May 14, 2022 at 14:01 | comment | added | Summit2 | What do you mean by including the system? Should I have mentioned Tutanota in the question text? | |
| May 14, 2022 at 12:47 | comment | added | Esa Jokinen | It would have been nice if you had included the system in your question, too. Their FAQ keeps bragging about how innovative their encryption scheme is, but doesn't tell much about the technical details. | |
| May 14, 2022 at 9:15 | history | edited | Summit2 | CC BY-SA 4.0 | added 4 characters in body |
| S May 14, 2022 at 9:14 | review | First answers | |||
| May 14, 2022 at 10:18 | |||||
| S May 14, 2022 at 9:14 | history | answered | Summit2 | CC BY-SA 4.0 |