Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: Debian, Ubuntu, Redhat, Fedora, SLES, OpenSUSE, FreeBSD, Mac OS X
Checking MD5 in SFTP
I am uploading some files to the ftp server using "sftp". I want to check the authenticity of the transferred files but the problem is that "md5" is not a supported command (interactive) command that can be used along with "sftp"
Is there any other way I can check the md5 of the transferred files.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
sftp doesn't allow remote execution of commands, so if you cannot ssh to the machine, you don't have a way to remotely run md5.
You could do ls -l after the transfer (in sftp) and make sure the size is right down to the byte, but that doesn't necessarily mean it's not corrupted. You could also upload the md5 fingerprint along with the file so the other side can check that they match. You could set the md5 sum as the file name so you can inspect that it made it unaltered, something like this: README.txt-cd5e1e13f12927d85bcf7afd3c24e2b3 .