Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
although i'd either use an md5sum file and then check it against that or still review the entire string although usually a cursory glance of a few characters as you note is sufficient
Code:
$cd /tmp
$echo 1 > example
$md5sum example > example.MD5SUM
$echo 2 > example
$md5sum -c example.MD5SUM
Experience shows that eyeballing a few characters works most of the time, but it's a terrible habit IMHO. Not only is it much more fool-proof to have the md5sum do the checking for you, it's also simpler (since you only have to look for an "OK"). Hence, I second rayfordj's suggestion that you use a checksum file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.