Timeline for Levels of strength: The Caesar Cipher
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2016 at 21:28 | history | tweeted | twitter.com/StackCrypto/status/742106287161397248 | ||
| Jun 11, 2016 at 18:29 | answer | added | jjm | timeline score: 2 | |
| Mar 5, 2016 at 16:10 | comment | added | Sergio A. Figueroa | And with such approach, I will encourage you to keep asking as you progress. If you do it here, make sure that you state all the facts that can be relevant: what you know, what you have tried and what you can't solve. That way, the question can get a better answer and the answer can reach more people. | |
| Mar 5, 2016 at 15:41 | comment | added | user31830 | This project was more about the journey rather then the destination, and I do realize you did not know this. The Caesar Cipher is nice because I can custom write it from the ground up rather then relying on a class I did not write. If I start doing real security rather than just a project when I'm bored I will be sure to use more secure methods rather than thousand year old ciphers. Thanks for the help! | |
| Mar 5, 2016 at 14:56 | comment | added | Sergio A. Figueroa | If you insist in using "classical ciphers", you might want to take a look to One Time Pad and understand why it is not used in practical scenarios. If it is complexity what keeps you from using any real symmetric encryption approach, keep in mind that BouncyCastle, one of the most popular cryptographic libraries, is available for C#. It is well documented and you can find samples online. If your purpose is something playful, like a cryptopuzzle, then the use of real randomness isn't really critical. If still curious about PRNGs, StackOverflow recommends the RNGCryptoServiceProvider Class. | |
| Mar 5, 2016 at 14:37 | vote | accept | CommunityBot | ||
| Mar 5, 2016 at 14:37 | comment | added | user31830 | I apologize for not including the field of my intended audience as I forgot the target of this website are those who are interested in securing large amounts of data from direct attacks. The intention of this project is not necessarily to be strong against those who understand encryption. I should have included in my question that I merely want it to be strong enough that it could not be immediately broken by an online decipherer. Mea Culpa | |
| Mar 5, 2016 at 14:32 | comment | added | Sergio A. Figueroa | As mentioned in the current answer, the question is somehow stepping on the wrong ground. Caesar Cipher, and even "stronger" substitution concepts (what you describe is, in fact, closer to Vigenère or one time pad), are not suitable for ANY security purpose. As such, the source of randomness is irrelevant. If you intend to use it just as a proof of concept (to see if you can implement it), then security is irrelevant and you can use the default random generator (usually insecure) to produce your "key". | |
| Mar 5, 2016 at 8:30 | answer | added | Leo.W | timeline score: 5 | |
| Mar 5, 2016 at 3:28 | history | edited | yyyyyyy |
edit tags
|
|
| Mar 5, 2016 at 3:23 | review | First posts | |||
| Mar 5, 2016 at 10:52 | |||||
| Mar 5, 2016 at 3:21 | history | asked | user31830 | CC BY-SA 3.0 |