Security 101 for SaaS startups

Re:Security 101 for SaaS startups by joshvm on Sunday March 05, 2017 @08:19PM (#13800048)

I would advise against Google Drive for document sharing. Recently I tried to share a trial build of an application (an exe I built) with a client. I zipped everything up and created a share link. Google auto-flagged it as a terms of service violation and blocked the file. No way of getting round it, and no way Google will bother to remedy the situation in time.

There's also OneDrive for business which seems to work well for sharing, though syncing options are totally broken. There's no way to selectively sync a share folder, so either you have your entire filesystem downloaded or you go online to get files. That sucks when your backup is terabytes of data.

I ended up sending a Dropbox link instead. So far it seems to be more or less foolproof.

[ Parent | on HN ]

Re:Security 101 for SaaS startups by itaifrenkel on Sunday March 05, 2017 @11:42PM (#13800745)

I am not sure that binaries are the use case for g-docs.

I would have used s3 for that.

[ Parent | on HN ]

Re:Security 101 for SaaS startups by joshvm on Monday March 06, 2017 @10:01AM (#13803059)

For mass distribution, sure a solution like S3 is the way to go. However, this was more of a "The file is too large to email, I'll zip the build and send a shared link" occasion. Using S3 for that is a sledgehammer approach especially when you're working with people who aren't tech savvy.

The concern is that G-Drive (not Docs) seems to arbitrarily decide what you can and can't share using it. In this case, it was a binary and associated files. I was able to share an earlier build without problems. Was it a DLL I'd bundled? VCpp redistributable? Was there some pattern of bits in the code that bothered the file checker? I don't know what triggered the violation and probably never will.

[ Parent | on HN ]