Table of Contents

Guide: Obtaining Hashes of Files on Linux using Built-in Tools

Introduction

In the world of Linux systems, obtaining file hashes is essential for ensuring data integrity and verifying file authenticity. File hashes serve as unique identifiers that allow users to detect tampering attempts and validate data integrity. In this comprehensive guide, we will explore how to obtain SHA256, MD5, and SHA1 hashes of files on Linux using built-in tools. Follow the step-by-step instructions and learn through specific examples.

Obtaining Hashes on Linux using Built-in Tools

Linux provides several built-in tools that enable users to calculate file hashes without the need for additional software installations. We will explore three widely used hashing algorithms: SHA256, MD5, and SHA1.

Obtaining the SHA256 Hash

To obtain the SHA256 hash of a file on Linux, you can use the sha256sum command. Open a terminal and navigate to the directory where the file is located. Then, execute the following command:

sha256sum file_path

Replace file_path with the actual path to your file.

Obtaining the MD5 and SHA1 Hashes

You can also obtain the MD5 and SHA1 hashes of a file on Linux using similar commands:

  • To obtain the MD5 hash:
md5sum file_path
  • To obtain the SHA1 hash:
sha1sum file_path

Replace file_path with the path to your file in both commands.

Examples

Let’s dig into specific examples to illustrate the process of obtaining hashes using built-in tools on Linux.

Example 1: Obtaining SHA256 Hash

Imagine you have a file named document.pdf located in the directory /home/user/docs. To obtain the SHA256 hash of this file on Linux, execute the following command:

sha256sum /home/user/docs/document.pdf

The output will display the SHA256 hash value of the file.

Example 2: Obtaining MD5 Hash

Suppose you have a file named image.jpg stored in the directory /home/user/pictures. To obtain the MD5 hash of this file on Linux, run the following command:

md5sum /home/user/pictures/image.jpg

The terminal will display the MD5 hash value of the file.

Example 3: Obtaining SHA1 Hash

Consider a scenario where you have a file named data.txt located in the directory /home/user/files. To obtain the SHA1 hash of this file on Linux, execute the following command:

sha1sum /home/user/files/data.txt

The output will display the SHA1 hash value of the file.

Advanced Linux Hashing Operations

Hash Multiple Files at Once 

# Hash all PDF files in directory
sha256sum /home/user/docs/*.pdf

# Hash all files recursively
find /home/user/data -type f -exec sha256sum {} \;

Create Hash Manifest File

Generate a file containing hashes for verification later:

# Create checksum file
sha256sum /home/user/important/* > checksums.txt

# Verify files against checksum file
sha256sum -c checksums.txt

Output when files match:

file1.txt: OK
file2.pdf: OK
file3.jpg: OK

Compare Hash Against Expected Value 

# Method 1: Manual comparison
expected_hash="e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
actual_hash=$(sha256sum /path/to/file | awk '{print $1}')

if [ "$actual_hash" == "$expected_hash" ]; then
    echo "✓ File verified - hash matches"
else
    echo "✗ WARNING: Hash mismatch!"
fi

# Method 2: Using echo and checking
echo "$expected_hash  /path/to/file" | sha256sum -c -

Hash from Standard Input 

# Hash text directly
echo -n "Hello World" | sha256sum

# Hash command output
cat /etc/passwd | sha256sum

# Hash without trailing newline (important!)
echo -n "text" | sha256sum  # Correct
echo "text" | sha256sum     # Different hash (includes newline)

Practical Use Cases

1. Verify Downloaded ISOs

Linux distributions provide hash checksums to verify downloads:

# Download Ubuntu ISO hash
wget https://releases.ubuntu.com/SHA256SUMS

# Verify your downloaded ISO
sha256sum ubuntu-26.04-desktop-amd64.iso

# Compare against published hash
grep ubuntu-26.04-desktop-amd64.iso SHA256SUMS

2. Detect File Tampering

Monitor critical system files:

# Create baseline
sudo sha256sum /etc/passwd /etc/shadow /etc/sudoers > /secure/baseline-hashes.txt

# Later, check for changes
sudo sha256sum -c /secure/baseline-hashes.txt

# Script for monitoring
#!/bin/bash
if ! sudo sha256sum -c /secure/baseline-hashes.txt > /dev/null 2>&1; then
    echo "ALERT: System files modified!" | mail -s "Security Alert" admin@example.com
fi

3. Deduplicate Files

Find duplicate files using hashes:

# Find duplicates in directory
find /home/user/photos -type f -exec sha256sum {} \; | sort | uniq -w 64 -D

4. Verify Backup Integrity 

# Create hash manifest before backup
find /data -type f -exec sha256sum {} \; > /backup/manifest-$(date +%Y%m%d).txt

# After restore, verify
sha256sum -c /backup/manifest-20260524.txt

Automation Scripts

Script 1: Recursive Hash Generator 

#!/bin/bash
# hash-directory.sh
# Usage: ./hash-directory.sh /path/to/directory

if [ $# -eq 0 ]; then
    echo "Usage: $0 <directory>"
    exit 1
fi

directory="$1"
output="hashes-$(date +%Y%m%d-%H%M%S).txt"

echo "Generating SHA256 hashes for: $directory"
find "$directory" -type f -exec sha256sum {} \; > "$output"
echo "✓ Saved $(wc -l < "$output") file hashes to: $output"

Script 2: Hash Verification Tool 

#!/bin/bash
# verify-hashes.sh
# Usage: ./verify-hashes.sh checksums.txt

if [ ! -f "$1" ]; then
    echo "Error: Checksum file not found"
    exit 1
fi

echo "Verifying file integrity..."
if sha256sum -c "$1" 2>/dev/null; then
    echo "✓ All files verified successfully"
    exit 0
else
    echo "✗ Some files failed verification"
    exit 1
fi

Script 3: Download Verification 

#!/bin/bash
# verify-download.sh <file> <expected-sha256>

file="$1"
expected="$2"

if [ ! -f "$file" ]; then
    echo "Error: File not found"
    exit 1
fi

actual=$(sha256sum "$file" | awk '{print $1}')

if [ "$actual" == "$expected" ]; then
    echo "✓ Download verified - SHA256 matches"
    exit 0
else
    echo "✗ DANGER: SHA256 mismatch!"
    echo "Expected: $expected"
    echo "Actual:   $actual"
    exit 1
fi

Performance Optimization

Hash Large Files Efficiently

For very large files, you can monitor progress:

# Using pv (pipe viewer) to show progress
pv large-file.iso | sha256sum

# Install pv if needed
sudo apt install pv  # Debian/Ubuntu
sudo dnf install pv  # Fedora

Parallel Hashing

Hash multiple files in parallel using GNU Parallel:

# Install parallel
sudo apt install parallel

# Hash files in parallel (4 jobs)
find /data -type f | parallel -j 4 sha256sum {} > hashes.txt

Benchmark Hash Algorithms 

# Compare speed of different algorithms
time sha256sum large-file.bin
time sha1sum large-file.bin
time md5sum large-file.bin

# Typical results (1GB file):
# MD5:    ~1-2 seconds (fastest, insecure)
# SHA1:   ~2-3 seconds (deprecated)
# SHA256: ~3-5 seconds (recommended)

Hash Algorithm Security Comparison

AlgorithmHash LengthStatus 2026Use Case
SHA-256256-bit (64 char)✅ SecureRecommended for all security purposes
SHA-512512-bit (128 char)✅ SecureExtra security for sensitive data
SHA-1160-bit (40 char)⚠️ DeprecatedLegacy compatibility only
MD5128-bit (32 char)❌ BrokenNon-security purposes only

2026 Recommendation: Always use SHA-256 or SHA-512 for security-critical applications.

Integration with Package Managers

Verify APT Packages (Debian/Ubuntu) 

# Check package integrity
debsums -c

# Verify specific package
debsums openssh-server

Verify RPM Packages (Fedora/RHEL) 

# Check all packages
rpm -Va

# Verify specific package
rpm -V openssh-server

Best Practices for 2026

  1. Use SHA-256 as default: It’s the current security standard
  2. Avoid MD5 and SHA-1 for security: Only for legacy compatibility
  3. Always use -c flag for verification: sha256sum -c checksums.txt
  4. Store checksums separately: Don’t store hashes with the files they verify
  5. Use -b for binary mode: sha256sum -b file.bin (important on some systems)
  6. Automate verification: Create cron jobs for critical file monitoring
  7. Use --quiet in scripts: Suppress OK messages with sha256sum -c --quiet

Troubleshooting

“No such file or directory”

Solution: Use quotes for paths with spaces:

sha256sum "/path/with spaces/file.txt"

“WARNING: X lines are improperly formatted”

Solution: Checksum file format must be:

hash_value  filename

Note the two spaces between hash and filename.

Permission Denied

Solution: Use sudo for system files:

sudo sha256sum /etc/shadow

Cross-Platform Verification

Verify Linux Hashes on Windows 

# PowerShell on Windows
Get-FileHash -Algorithm SHA256 file.txt

Verify Linux Hashes on macOS 

# macOS uses shasum
shasum -a 256 file.txt

Conclusion

Linux provides powerful built-in tools (sha256sum, md5sum, sha1sum) for file hashing. Whether you’re verifying downloads, monitoring file integrity, detecting duplicates, or ensuring backup validity, mastering these commands is essential for system administration and security in 2026.

main points:

  • Use sha256sum for all security-related hashing
  • Create hash manifests with sha256sum * > checksums.txt
  • Verify files with sha256sum -c checksums.txt
  • Automate hash checking in scripts for critical files
  • Avoid MD5 and SHA-1 for security purposes

References

  1. sha256sum - Linux man page
  2. md5sum - Linux man page
  3. sha1sum - Linux man page
  4. GNU Coreutils - Checksums
  5. NIST Hash Functions