Most people treat the Recycle Bin, and emptying it, as the final word on a deleted file. This lab walked through why that assumption is wrong, and why both sides of that fact matter for a network defender.
muhakeem.hashnode.dev/recove…
builder.aws.com/content/3LCK…
github.com/devmuhakeem/File-…
After the scan completed, the tool produced a report and the recovered files showed up, organized in a structure reflecting the original filesystem.
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.
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.
Check the full documentation here:
muhakeem.hashnode.dev/encryp…
builder.aws.com/content/3LBC…
github.com/devmuhakeem/Disk-…
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…
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

