Greg Clarke

Mastodon: @greg@clar.ke

  • 2 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: November 9th, 2022

help-circle













  • I’m running a search instance on a VPS so my home IP isn’t linked to my searches. The main disadvantage is that my VPS is in Toronto and I live 2hrs away so geo searches don’t work very well. For instance, if I Google “restaurants” I get results for local restaurants whereas if I Gregle (I named my search engine Gregle) I get results for results near my VPS.

    DM me if you want a link to my instance to check it out. It’s open but I don’t publicize it because bad actors could ruin my IP addresses reputation with spam queries via the API.






  • That’s fair, I can appreciate an attack vector in cases where there are bad blocks and the drive was unencrypted. Luckily bad blocks are less common with modern SSDs and assuming the disk was encrypted, a few bad blocks are unlikely to expose any contents. So knowing the number of bad blocks and what data was stored would inform if a fill and empty approach would be suitable to sanitize the drive.


  • Fill the drive 100% using data duplicator then delete everything on the drive. Repeat a few times to ensure you scrub all blocks. There is no need to physically destroy the drive.

    edit: fair criticism of this approach in cases when the data is unencryptd and the hard drives has bad blocks. I just wanted to give a counter to the destroying hardware approach which isn’t necessary warranted