News for hackers. Stuff that matters.
Re:GDPR for lazy people: Block all European users with Cloud... by yzmtf2008 on Friday May 25, 2018 @08:21PM (#17159281)
I encourage you to read my comment again, and point out where I mentioned merely setting a delete flag. Any reader worth their salt will point out that it’s not what I suggested at all.
Re:GDPR for lazy people: Block all European users with Cloud... by alexbecker on Friday May 25, 2018 @08:29PM (#17159321)
I believe the confusion is around your statement "mark every sensitive field". I think you mean "overwrite every sensitive field", but that definitely took a re-reading to infer, and I'm still not 100% sure.
Re:GDPR for lazy people: Block all European users with Cloud... by yzmtf2008 on Friday May 25, 2018 @08:32PM (#17159339)
Thanks, the processs reminded me of the “redaction” process, so I used mark. That’s definitely on me. Clarified.
Re:GDPR for lazy people: Block all European users with Cloud... by codexon on Friday May 25, 2018 @08:23PM (#17159291)
"you could easily not switch to a CASCADE, but instead set delete=1 and mark every sensitive field with a special value"
Re:GDPR for lazy people: Block all European users with Cloud... by dbpatterson on Friday May 25, 2018 @08:29PM (#17159323)
you ignored "and mark every sensitive field with a special value", which is the key part. As long as all sensitive data has been essentially zero'd out (for some value of zero), all is fine.
Re:GDPR for lazy people: Block all European users with Cloud... by codexon on Friday May 25, 2018 @08:33PM (#17159341)
Marking a field sounds to me like labeling and not zeroing it out.
Re:GDPR for lazy people: Block all European users with Cloud... by jachee on Friday May 25, 2018 @09:53PM (#17159685)
What if "a special value" == NULL?
Re:GDPR for lazy people: Block all European users with Cloud... by namibj on Friday May 25, 2018 @11:52PM (#17160103)
If you choose that value, and it's the only, or one of the few values that break your software, then it's your fault.