Re:GDPR for lazy people: Block all European users with Cloud...
by henrikeh on Saturday May 26, 2018 @01:26AM
(#17160379)
It is simple. You have to apply reasonable measures to delete the data.
That is vague, for sure, but hopefully you have the engineering skills and domain knowledge to make a good call.
Dealing with credit card data? Think a lot about it.
Dealing with movie preferences? Deleting from the database should be adequate.
Dealing with attendants from a local conference? Delete the files when you don’t need them.
(And remember: nobody will ever show up with a fine one day. It will always start with a warning and a chance to improve before any fine is applied – unless there is serious neglect.)
Re:GDPR for lazy people: Block all European users with Cloud...
by yzmtf2008 on Friday May 25, 2018 @11:34PM
(#17160049)
I’m well aware of that, but are you aware of any SQLi that can output a deleted file? There’s a big difference between the two things you’re trying to equalize.
Re:GDPR for lazy people: Block all European users with Cloud...
by berti on Saturday May 26, 2018 @12:21AM
(#17160198)
Does the GDPR actually draw that line somewhere above the filesystem, but below the database?
Re:GDPR for lazy people: Block all European users with Cloud...
by philjohn on Saturday May 26, 2018 @12:47PM
(#17162958)
Totally different. deleted=1 would be like adding a tag to a file saying "hey, this file is deleted" and never doing anything again.
A filesystem will remove the entry pointing to the data on disk, and mark that region as free and ready to be reused - and it will get overwritten.
Are you aware that setting “delete=1” is essentially what file systems do when deleting a file? What file system do you suggest companies to use when they want to comply with GDPR?