You are not logged in.
Pages: 1
I want a command to check if the kernel or any files and programs have been maliciously tampered with. Pacman -Qkk linux-lts gives me a result of 0 altered files but I dont know how it considers a file trusted.
Offline
pacman -Qkk confirms the files size, checksum, and permissions have not changed.
Offline
Are you checking just because or do you actually suspect that somebody tampered with your system?
Offline
pacman -Qkk confirms the files size, checksum, and permissions have not changed.
I got sha256 checksum mismatch /etc/pacman.d/conf mismatch size mismatches permission mismatches and a gid mismatch is this normal? How far must the filesize and permissions deviate from what is considered normal?
Offline
Are you checking just because or do you actually suspect that somebody tampered with your system?
I know the computer has been tampered with but I want to know how I could tell.
Offline
I think https://lists.archlinux.org/archives/li … PYIWU75XQ/ also is useful for this purpose if I understand it correctly
Offline
Allan wrote:pacman -Qkk confirms the files size, checksum, and permissions have not changed.
I got sha256 checksum mismatch /etc/pacman.d/conf mismatch size mismatches permission mismatches and a gid mismatch is this normal? How far must the filesize and permissions deviate from what is considered normal?
My guess is you edited a configuration file. Pacman can not tell the difference between your edits and malicious edits.
Offline
among666 wrote:Allan wrote:pacman -Qkk confirms the files size, checksum, and permissions have not changed.
I got sha256 checksum mismatch /etc/pacman.d/conf mismatch size mismatches permission mismatches and a gid mismatch is this normal? How far must the filesize and permissions deviate from what is considered normal?
My guess is you edited a configuration file. Pacman can not tell the difference between your edits and malicious edits.
Does this mean the command pacman -Qkk is useless?
Offline
Not at all, it gives you a list of files to check against your secure, offsite backups.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Except the databases aren't signed - it's a maintainence tool, not a security one.
If you want to check the system against malicious tampering
1. this *has* to happen offline (ie. w/o booting the system because the compromisation might hide itself)
2. You need a known good external and locked away database of valid hashes for every file on the system - or the entire drive.
A malicious actor could simply shadow binaries in paths not tracked by the package manager (/usr/local) or even attack a specific user w/ LD_LIBRARY_PATH & LD_PRELOAD, so "pacman -Qkk looks god" doesn't indicate "this system hasn't been compromised" at all.
Also the rule of thumb is that a known compromised system can no longer be trusted and has to be nuked and replaced from a known good master/backup - attacks don't require system file replacements at all - a subtle touch-up of the sshd config might get the job done.
And that's even ignoring concerns regarding the UEFI - or that you might have actively (but unknowingly) installed malware and signed off on it.
Offline
Pages: 1