in reply to FTP & MD5

Your "bright spark" isn't very bright at all. FTP access to a server doesn't imply the ability to obtain an MD5 sum of files on said server. Moreover, in the general case, it is not a requirement that the files have the same bytes on the local and remote side. Transferring in ASCII mode will convert line endings to the local notion; if the two systems have a different idea of what constitutes an end of line ("\r\n" vs "\n" vs "\r"), ftp will convert them on-the-fly. So, the two files needn't even hash to the same value. However, you said that you're transferring from one PC to another, so that might help. The only way I could see pulling this off is to have pre-computed md5 files lying around for each file that you'd want to transfer. You'd grab the file you want, it's corresponding hash file, hash the file when you're done transferring it, and compare the computed value with the hash file that you got from the server.

HTH,
thor

Feel the white light, the light within
Be your own disciple, fan the sparks of will
For all of us waiting, your kingdom will come

Replies are listed 'Best First'.
Re^2: FTP & MD5
by Fletch (Bishop) on Jun 21, 2005 at 13:46 UTC

    Not to mention that if you're not doing any sort of authentication of the conversation with the other end there's nothing to stop someone able to muck with the data in transit from mucking with the MD5 as well.

    --
    We're looking for people in ATL

Re^2: FTP & MD5
by shiza (Hermit) on Jun 22, 2005 at 00:13 UTC
    Transferring in BINARY should eliminate size differences, but, that still doesn't solve the problem.