Timeline for Pronounceable encrypted text
Current License: CC BY-SA 4.0
22 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 7, 2020 at 7:57 | answer | added | Andy | timeline score: 0 | |
Sep 9, 2019 at 4:12 | answer | added | octo | timeline score: 0 | |
Sep 7, 2019 at 10:18 | comment | added | Maeher | @forest But that seems more like an answer than a close reason. There way that the question is posed is on topic, since OP clearly did not realize that using arbitrary encryption plus generic encoding is the solution. | |
Sep 7, 2019 at 8:46 | comment | added | forest | I'm voting to close this question as off-topic because encoding data into pronounceable text is not specific to cryptography in any way. | |
Sep 7, 2019 at 1:31 | answer | added | Foogod | timeline score: 4 | |
Sep 6, 2019 at 16:55 | review | Close votes | |||
Sep 9, 2019 at 8:42 | |||||
Sep 6, 2019 at 16:38 | comment | added | dan04 | Possible duplicate of Spoken encryption | |
Sep 6, 2019 at 13:38 | comment | added | vsz | You mean something like this: xkcd.com/257 ? | |
Sep 6, 2019 at 12:00 | history | tweeted | twitter.com/StackCrypto/status/1169943446255263744 | ||
Sep 6, 2019 at 11:00 | answer | added | WhiteWinterWolf | timeline score: 2 | |
Sep 6, 2019 at 0:26 | comment | added | John Coleman | If you are not worried about the ciphertext being substantially longer than the plaintext, you could look into grammar-based steganography. You can't get any more pronounceable than that. I don't have a good link for it, but the book "Disappearing Cryptography" has a nice chapter on it. | |
Sep 5, 2019 at 21:55 | history | became hot network question | |||
Sep 5, 2019 at 21:25 | answer | added | mentallurg | timeline score: 2 | |
Sep 5, 2019 at 16:32 | answer | added | Future Security | timeline score: 21 | |
Sep 5, 2019 at 16:18 | answer | added | poncho | timeline score: 5 | |
Sep 5, 2019 at 14:41 | comment | added | Eugene Styer | Commercial one-part codes used pronounceable words (prior to WW1, then the telegraph rules changed), but that isn't software and wasn't secure against attack even at the time. | |
Sep 5, 2019 at 14:04 | comment | added | Paul Uszak |
Just to be crystal clear, you want your cipher text to look like 46 66 72 BF 2E 3A 09 67 6D EF F3 77 14 3A A5 96 58 AA E9 79 88 2E B1 71 6F 93 11 E0 21 FA 35 rather than pronounceable English words (phonemes)? So not like what Lisa Gerard sings (glosalalia)?
|
|
Sep 5, 2019 at 13:39 | history | edited | octo | CC BY-SA 4.0 |
edited title
|
Sep 5, 2019 at 13:20 | comment | added | kelalaka |
There are many libraries depending on your programing language just Google your_programming_language FPE , and base64 is almost common in all.
|
|
Sep 5, 2019 at 13:15 | comment | added | octo | @kelalaka - thank you. Since I am a total amateur, is there any software (win, mac or web) that does this? | |
Sep 5, 2019 at 13:08 | comment | added | kelalaka | Not another language but look at Format Preserving Encryption, that you can spell, also, you can encode the output into base64... | |
Sep 5, 2019 at 13:06 | history | asked | octo | CC BY-SA 4.0 |