Timeline for Why can one box decrypt a file with openssl, but another one can't?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2017 at 13:02 | history | edited | Jeff Schaller♦ |
edited tags
|
|
| Feb 13, 2017 at 16:04 | vote | accept | Carrot | ||
| Feb 13, 2017 at 10:04 | answer | added | dave_thompson_085 | timeline score: 13 | |
| Feb 11, 2017 at 23:15 | comment | added | Carrot |
We have a winner! @dave_thompson_085, that's exactly what the problem was. I just added -md md5 to the command, and it worked perfectly. Thanks! If you want to write an answer, I'll accept it. If not, I'll answer it myself, just so there's an answer here.
|
|
| Feb 11, 2017 at 9:18 | comment | added | dave_thompson_085 |
Is one of them 1.1.0 and the other not? The default hash for the KDF used by enc changed in 1.1.0; to get old behavior on a new version specify -md md5 and for new behavior on an old version -md sha256 (supported at least back to 0.9.8 but not documented then).
|
|
| Feb 11, 2017 at 1:29 | comment | added | SauceCode | Also it looks like you've run one command as root, and the other not. Although that's probably not relevant, since the successful one was non-root, try them in the most comparable state you can. Finally (as you probably know) you're running them in different directories. | |
| Feb 11, 2017 at 1:22 | comment | added | SauceCode |
Also maybe openssl version on both machines is worth checking.
|
|
| Feb 11, 2017 at 1:21 | comment | added | SauceCode |
I once spent ages troubleshooting a similar issue where I mistyped a 0 as a o. I doubt it's the same issue here, but try if you can to make sure you've cut/pasted the command rather than retyping.
|
|
| Feb 11, 2017 at 1:10 | history | migrated | from serverfault.com (revisions) | ||
| Feb 11, 2017 at 0:21 | history | asked | Carrot | CC BY-SA 3.0 |