Timeline for With openssl des3, what are the passphrase parameters?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 31, 2017 at 11:43 | comment | added | dave_thompson_085 |
Nitpick: if 'control characters' includes newline, shell command expansion with backticks or (preferred) $( ) discards trailing newlines even if they were intended as data and unquoted it also discards leading and trailing whitespace and any embedded whitespace will and anything resembling a glob pattern may cause an error. OTOH if passphrase is the first or only line in the file, -kfile filename or -pass file:filename reads from the file without making it visible in ps or similar.
|
|
| Jan 14, 2016 at 16:38 | comment | added | sethmlarson |
The formatting is making the back-ticks into a code block, for the record. If you're wondering how you can use a key with control characters, if you have it saved to a file you can run openssl des3 -salt -k (BACKTICK)cat password.txt(BACKTICK) < plaintext.txt > encrypted.txt
|
|
| Jan 14, 2016 at 16:25 | comment | added | Daniel Griscom | Yes, but where do those 168 bits come from? The ASCII representation of the first 21 characters of my passphrase? If so, then that's throwing away approximately 30 bits of entropy (assuming I don't use high ASCII or control characters). (I'm adding this to my question.) | |
| Jan 14, 2016 at 16:21 | history | answered | sethmlarson | CC BY-SA 3.0 |