Daily Linux Forensics Trivia #30 - Write a "find" expression to locate directories whose names begin with a dot (".") and which are not located in a user's home directory.
Some folks suggested looking at /etc/issue or /etc/motd. While these files often contain the distro/version info, they are also just as likely to have been edited and contain a site-specific message without the OS information.
Trivia Answer #29 - Shout out to @Grabbi_it for chiming in with the answer. Mount your evidence and look at /etc/os-release, which should be there regardless of which distro you have been given.
“Our new medicine costs thousands per month, but your insurance covers it! Oh you say it’s not covered? Here’s a coupon so you can get it for $25/mo!” — Why do we keep letting this scam play out?
That’s a lot of development and testing effort to just be abandoned. But whether it’s TSK or something new, we need an Open Source, cross-platform filesystem interpreter that supports common modern file systems.
The #DFIR community needs funding and resources put towards libsleuthkit. And everybody needs to share their "private" forks where they have fixed bugs and added new file systems support. Hackathon anybody?
Just wanted to mention that my Linux Forensics training is happening next week. There is still time to sign up, and class size will be small. Hope to see you there!
The only thing different about web browser artifacts on Linux is their location. $HOME/.mozilla/firefox (Firefox) and $HOME/.config/chromium (Chrome) are the usual locations on Linux. Otherwise it's same SQLite databases, etc. Anything else would be crazy in terms of code re-use