Timeline for How can A pass a message to B, while preventing a third party from sniffing infos?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:48 | history | edited | CommunityBot |
replaced http://crypto.stackexchange.com/ with https://crypto.stackexchange.com/
|
|
| Jan 8, 2014 at 16:47 | comment | added | tylo | Creating a random key is not that difficult, it does not even need the properties provided by CPRNGs - depending on the attacker model, ofc. But letting the server know the session keys is putting a lot of trust in this instance, it means the server (or anyone who can access its data) can listen to the entire communication. | |
| Jan 8, 2014 at 15:02 | comment | added | amanraj | @tylo but,letting users to generate session key faces one problem, both Alice and Bob should be capable enough to generate completely random session key!! | |
| Jan 8, 2014 at 14:39 | comment | added | tylo | There is also a drawback here, which is that the server knows the session key. This is not ideal, but there are better ways. For example, Alice could just request Bob's public key instead, and then she creates a session key, encrypts with Bob's public key, and sends this to Trend, and Trend just passes is on. Oh, and the users should create their private and public keys themselves and only give the server the public key in the setup. | |
| Jan 8, 2014 at 13:47 | history | edited | Gilles 'SO- stop being evil' | CC BY-SA 3.0 |
English improvement; link to the mentioned answer; get rid of obfuscating link
|
| Jan 8, 2014 at 13:03 | review | First posts | |||
| Jan 8, 2014 at 13:48 | |||||
| Jan 8, 2014 at 12:45 | history | answered | amanraj | CC BY-SA 3.0 |