Thanks! FTP was the problem. SCP transferred the file without corrupting it.
Dan. On Thu, Feb 4, 2010 at 8:30 PM, Dave Thompson <dave.thomp...@princetonpayments.com> wrote: >> From: owner-openssl-us...@openssl.org On Behalf Of Dan Letkeman >> Sent: Thursday, 04 February, 2010 14:36 > >> So i'm transferring it with FTP, could that be the problem? Any other >> way to transfer it to a windows machine? > >> On Thu, Feb 4, 2010 at 11:24 AM, Patrick Patterson >> <ppatter...@carillonis.com> wrote: > >> > How are you transfering the file around? perhaps your >> getting some form of >> > corruption during your file transfer? > > Make sure you are in BINARY mode in FTP. > It's not usually (perhaps not ever) the client default. > > When you get the file on the target, check its size in bytes > matches exactly that from the origin. Even one byte difference > in a binary file (like P12 DER) is fatal. > > To answer as asked (but probably superfluous): > > You could also use SFTP (Putty provides a Windows client) > which AFAICT does ONLY binary/image/no-cleverness; > (get and) run NFS software on the Windows machine > so that Linux (or Unix) can mount and access it; > or (get and) run Samba on Linux so that Windows can access it. > > Or (re)configure a webserver on the Linux to serve > this file as application/octet-stream or a similar type > that a browser on Windows (can't render and) will store. > > Or write to removable media in a Windows-understandable > filesystem and move that to the Windows. Today that's > USB memory or disk (probably FAT) or maybe CD-R; > or floppy if you still have them. > > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-us...@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
