Skip to main content


for anyone who was in any of the #GNOME #matrix rooms a week or so ago... the flatpak version of element keeps its cache at ~/.var/app/im.riot.Riot/config/Element/Cache/Cache_Data/. you can use something like wipe to securely erase it.

EDIT: wipe and shred and co. won't work on an SSD. use something like blkdiscard instead.

This entry was edited (3 weeks ago)
in reply to Lynnesbæn :bune_ylw:

i'm on an SSD and wipe's last update was in 2004 to add support for solaris so uh i don't know if it will work the way it's mean to
in reply to Lynnesbæn :bune_ylw:

it certainly won’t work properly on any CoW filesystem, or if you have LVM snapshots, or any other number of things. That tool is for extremely basic cases only (ext4 on an hdd).
in reply to Lorgo Numputz

@lorgonumputz @pauldoo alright so according to this: https://unix.stackexchange.com/a/593340

shred, wipe, et al just won't work on SSDs because of how they function. the best you can do is a tool called blkdiscard which will politely ask the SSD to wipe the file. failing that, you have to wipe the entire SSD :face_think_thonking:

in reply to Lynnesbæn :bune_ylw:

@pauldoo

I concur; this inherent issue is why I've moved all of my infrastructure to use LUKS encrypted disks - which means I don't have to worry about wiping and destroying disks that I need to dispose of.

BUT - that doesn't really help much if the person trying to recover the file has access to the unencrypted filesystem data.

shred(1) does try to do some renaming tricks (see -z) but not at all a guarantee that will obfuscate *enough*.

in reply to Pinguin :debian: :matrix:

@pinguin i didn't see any of the images, but apparently they contained some pretty horrible illegal stuff

if you want a more explicit answer: https://matrix.to/#/!guvcqdhipvyuqxhmyk:gnome.org/$b1prccrdi4979cbes94zqdymylgptbce8utl1w1myn8

Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.