6 ms·
I experienced something similar building an internal tool on GSuite. I had a large file with sequences of 9 digit numbers specific to our use-case, all tied to
by ChicagoBoy11 5y ago
I experienced something similar building an internal tool on GSuite. I had a large file with sequences of 9 digit numbers specific to our use-case, all tied to names of people (employees). Whelp, at one point the tool I was working on stopped working, and it was flagged as apparently containing social security numbers (which I suppose matched the character length).
Whelp, on the admin panel, you can get a report of those files, and then mark it as a false positive. Which I did. But then nothing happened, and nothing changed. It was no use.
The hilarious bit: It did, of course, allow me to make a copy of the file in question, and then just point the resource I was building to the new file, which was exactly the same. Weeks later... so far, so good.
- kwhitefoot 5y agoIs this a tool that you pay money for? Sounds like it fails the 'fitness for purpose' test.
- slig 5y agoGoogle is working very hard to make everyone drop their shitty services.
- Kim_Bruning 5y agoThis is why running filters on automated data is never a good idea, and should never be accepted (at least for enterprise applications, but really for anything) .
- Arnavion 5y agoThis is another case for only pushing encrypted files to storage hosts, unless it's against Google Drive's TOS or something. Has anyone tried it? Did Google complain?
- anon9001 5y agoTarsnap is entirely encrypted and the service provider can't see the keys. They run it on EC2 and S3: https://www.tarsnap.com/infrastructure.html https://www.tarsnap.com/infrastructure.html
- xcjs 5y agoI have an Enterprise Gsuite account with 50 TB of encrypted data for around 5 years (this was of course prior to the rebranding). I've had no complaints from Google so far.
- aspenmayer 5y agoYou use rclone, or another stack? I’m always trying new tools in this space.
- stevens37 5y agoyes openssl enc -e -aes-128-cbc -in ${1} -out ${1}.cr -iter +123456 -k <password>
- aspenmayer 5y agoIf you don’t know about this feature of rclone, you’re in for a treat! Combined with unionfs or mergerfs, or the builtin union function, you can have cached local decrypted mounts of locally encrypted remote mounted directories on gdrive, mirrored to a local folder. https://rclone.org/crypt/ https://rclone.org/crypt/ https://rclone.org/union/ https://rclone.org/union/ Edit: there is also the (sorta abandoned, or finished/complete depending on your pov) plexdrive project, which does a bit of Plex server specific opinionated stuff and mounts gdrive read only, but which may help with reducing API quota usage according to some reports. I’ve never had any issues with the quotas that I’m aware of, but I did have to tune my settings a fair bit to get it dialed in on a somewhat memory constrained vps. https://github.com/plexdrive/plexdrive https://github.com/plexdrive/plexdrive
- CPAhem 5y agoSyncdocs is also an easy end-to-end encryption/sync app for Google Drive https://syncdocs.com https://syncdocs.com
- Gigachad 5y agoProblem is it makes the apps / integrations useless. I use google drive primarily from my ipad and encrypted files would mean I can't just "save to files" and have it drop in to google drive.
- spicybright 5y agoThat's ridiculous. Storing social security numbers is necessary for lots of businesses. Imagine your filing cabinet not letting you file employment forms with a SS# on them. It's the sticky note password problem all over again...
- driverdan 5y ago> That's ridiculous. Storing social security numbers is necessary for lots of businesses. They should absolutely not be stored in a GSuite document. SSNs should be treated more securely than credit card numbers.
- bonzini 5y agoWhich is a problem of its own, since they're effectively usernames. Secure usernames that have no corresponding password is already an oxymoron; that's what credit card numbers used to be, hence the introduction of the CVV, 3DSecure and so on; but at least a credit card can be blocked with relative ease. But SSNs are secure unchangeable usernames, which makes even less sense. Do any countries other than the US have such an abomination, where you can figure out the SSN of someone and ruin their life?
- spicybright 5y agoNot that I know of. It really is a horrible system. But it's not one I want Google trying to solve.
- AnthonyMouse 5y agoYou can actually change your social security number in the circumstance of "victim of identity theft continues to be disadvantaged by using the original number": https://faq.ssa.gov/en-us/Topic/article/KA-02220 https://faq.ssa.gov/en-us/Topic/article/KA-02220 It's a huge pain, obviously. Especially when you get to all the systems which blindly assume it isn't possible. But you can do it. They ought to just open it up and let anyone who requests to change it once a year no questions asked.