4 ms·
> plus their own log files covering those deletions This is the really unreasonable part. Some convoluted internal process that ends up accidentally flagging a
by throw10920 4y ago
> plus their own log files covering those deletions
This is the really unreasonable part. Some convoluted internal process that ends up accidentally flagging a file as suspicious and then deleting it is bad enough, but still partially understandable if you're very conservative with assigning blame. But deleting the log files? Either extreme technical incompetence or plain malice.
- bell-cot 4y agoOur assumption: Log files of everything still existed, but were flagged "Hide & Never Admit To, per $SecretReason".
- deanCommie 4y agoHanlon's razor: At dropbox's scale, guaranteed logfile durability is expensive, and retaining them indefinitely even more so. They either got auto-deleted or they were never there in the first place.
- therealdrag0 4y agoI agree with Hanlon, but the size for basic audit ability is pretty small. Fileid, action, date, actorID. Maybe a bit more nice to haves. If it’s expensive store it for a couple weeks before archiving to cold storage. Here’s another Hanlon, it wasn’t Dropbox that deleted the files it was an authorized user, OP or coworker, accidentally who forgot or wouldn’t fess up