Hamdan (@devmuhakeem) header
Hamdan (@devmuhakeem) profile picture

ChemE | WordPress Developer | CMS Expert | Social Media & Community Manager | Open to Remote & Freelance Opportunities | Web3 lover ❤️

Nigeria, Lagos
Joined November 2022
Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)Photo by Hamdan (@devmuhakeem)
After the scan completed, the tool produced a report and the recovered files showed up, organized in a structure reflecting the original filesystem.
1
3
What stuck with me is that this skill cuts both ways for a security practitioner. On one side, it's a genuinely useful operational capability, recovering data lost to accidental deletion, a crash, or hardware failure is a real, recurring need.
1
There's a meaningful difference between encrypting a file and encrypting a volume, and it's not just a matter of scale. A single encrypted file still reveals its own existence, its name, its size, roughly when it was last touched. An encrypted volume,hides all of that.
1
18
I dismounted the volume, and the I: drive didn't just lock or show an access-denied message, it disappeared entirely. All that remained was the original My Volume file, giving zero indication of the file names, folder structure, or content it held inside.
1
5
I worked through three labs in a cryptography and PKI module recently, two on hashing, one on building a self-signed certificate, and together they made something clear that's easy to blur: hashing and certificates answer genuinely different questions. muhakeem.hashnode.dev/hashes…
1
22
then bound it to the site (port 443, the right IP, the hostname, the new cert). Reloading the site over HTTPS, the browser threw a very specific, correct warning: connection not private. That's not a bug, it's the browser correctly declining to vouch for a certificate
1
2
A self-signed cert gives you real encryption, but zero identity verification, which is exactly right for a local testing environment and exactly wrong for anything public-facing.