Thanks David, That worked a treat. I missed it somehow when I was adding a return.
Matt On 31 May 2011 21:32, Dave Thompson <dthomp...@prinpay.com> wrote: >> From: owner-openssl-us...@openssl.org On Behalf Of Kyle Hamilton >> Sent: Thursday, 26 May, 2011 21:28 > >> It looks like you've base64-encoded the actual ciphertext. > > $alg(enc) -d -a decodes base64 AND decrypts. > >> On Thu, May 26, 2011 at 3:01 PM, Matt Thompson >> <thompson...@gmail.com> wrote: >> > I get an error when I try the following: >> > >> > PS C:\bin\OpenSSL-Win32\bin> gc .\secrets.m.text >> > U2FsdGVkX1+21O5RB08bavFTq7Yq/gChmXrO3f00tvJaT55A5pPvqw0zFVnHSW1o >> > PS C:\bin\OpenSSL-Win32\bin> .\openssl aes-256-cbc -d -a -in >> > .\secrets.m.text -k password >> > error reading input file >> > >> > I've tried different formats for the file (ANSI, Unicode >> (big endian) >> > and UTF-8) but no joy... >> > > "ANSI" in notepad etc. works for me IF the file ends with newline > as previously suggested; no newline gives exactly the error posted. > On Windows newline actually is normally the CR LF pair; plain LF > also works for me, although this may depend on the C-library used, > which in turn may depend on the build options and/or run system. > > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
