Live data from Hacker News

A recent security incident involving Dropbox Sign

sign.dropbox.com

51–60 of 76 posts

Re: A recent security incident involving Dropbox Sign

#52
post #36

Earlier quoted context omitted.

I'm not a business, I'm a paying customer on the most expensive personal tier. It's silly that they don't offer this feature for me. I also can't upgrade to a business plan because those require at least 3 users. It just feels like feature gatekeeping to me, but no way for me to pay more to get this feature. But I also understand that personal users are not Dropbox's main focus.

A Synology/QNAP/TrueNAS NAS is a far better solution, with no restriction.

I'm a big advocate for running a NAS, but using a service like Dropbox means there's one fewer personal device that needs babysitting.

Re: A recent security incident involving Dropbox Sign

#53
post #7

Earlier quoted context omitted.

OK, so there is no fundamental obstacle for providing true e2ee.

What I'd really like is for the encryption to be plugable and orthogonal to file syncing. Ie: authentication with dropbox/proton/bittorrent concerns only that you pay your storage/ingest/egress bill, but is otherwise unprotected and in the clear. Encryption of the file payload and metadata as a "bring-your-own" — on device — stream cypher (and key derivation, key management). Key exchange and sharing among devices or…

So kinda like how rclone does encrypted backends?

Re: A recent security incident involving Dropbox Sign

#54
post #36

Earlier quoted context omitted.

I'm not a business, I'm a paying customer on the most expensive personal tier. It's silly that they don't offer this feature for me. I also can't upgrade to a business plan because those require at least 3 users. It just feels like feature gatekeeping to me, but no way for me to pay more to get this feature. But I also understand that personal users are not Dropbox's main focus.

A Synology/QNAP/TrueNAS NAS is a far better solution, with no restriction.

We all are probably guilty of falling for the convenience trap here or there. But setting up the sync between Dropbox and the NAS (Synology user here) with a one-way, don't delete, don't overwrite policy is a good lifeline to have - you know, just in case...

Re: A recent security incident involving Dropbox Sign

#55
Trying to understand some of the interplay here:

> threat actor had accessed data including ... certain authentication information such as API keys, OAuth tokens, and multi-factor authentication.

> If I have a Sign account linked to my Dropbox account, is my Dropbox account affected? No. Based on our investigation to date, we believe this incident was isolated to Dropbox Sign infrastructure, and did not impact any other Dropbox products.

If you linked your Dropbox account to a Sign account, wouldn't Sign have had an OAuth token (or similar) with permissions to access documents in Dropbox accounts? One imagines that leaked, if everything else did. Would they have been able to detect this as a distinct access pattern from someone, say, choosing a file to sign via the Sign interface?

Re: A recent security incident involving Dropbox Sign

#56

I love Dropbox but stuff like this is a good reminder to re-evaluate using any service that store large amount of personal data without e2ee. I understand that partly because of block-level diffing and syncing, it's hard to provide true e2ee for Dropbox, but it's still a big reason why I'm having most of my stuff in iCloud Drive (with Advanced Data Protection), despite liking Dropbox much more. Hope they'll come arou…

I used to love Dropbox, then they limited devices and storage so much it was barely worth it, and spamming me with nag popups all day to upgrade because my storage was near full sealed the deal and I just started using OneDrive (not much better but it's integeated and convenient, probably going to just go foss with a home server eventually). Another sad downfall of a once good company.

They only limited devices for free accounts.

Re: A recent security incident involving Dropbox Sign

#57
post #43

This is Dropbox Sign, not Dropbox. It’s a document signing product akin to Docusign, and was called Hellosign before Dropbox acquired them. We are a customer of theirs at my startup, and as far as I can tell Dropbox has made very few changes since the acquisition beyond changing the branding. So I wouldn’t take this incident to be an indicator of much on the cloud-storage side of the company.

We’ve been with hellosign for years and Dropbox has done a great job of stabilizing them. I will tell you that they have put in a ton of ops work to keep the platform up more consistently.

Re: A recent security incident involving Dropbox Sign

#58
post #18

Earlier quoted context omitted.

Hashed passwords? Surely they mean hashed and salted passwords. Right? Right???

They were using SHA1, then they migrated. 68 million accounts dumped: https://www.theguardian.com/technology/2016/aug/31/dropbox-h... https://www.troyhunt.com/the-dropbox-hack-is-real/ now they first hash the password using SHA512 (with a per-account salt) then they hash the password with bcrypt (with the default strength) then they encrypt the password with a key that the application server runs with, but that is no…

They encrypt the salted password hash?

Re: A recent security incident involving Dropbox Sign

#59
post #36

Earlier quoted context omitted.

I'm not a business, I'm a paying customer on the most expensive personal tier. It's silly that they don't offer this feature for me. I also can't upgrade to a business plan because those require at least 3 users. It just feels like feature gatekeeping to me, but no way for me to pay more to get this feature. But I also understand that personal users are not Dropbox's main focus.

A Synology/QNAP/TrueNAS NAS is a far better solution, with no restriction.

You would still need somewhere to do off site backups to.

(Edit: changed offline to offsite)

Re: A recent security incident involving Dropbox Sign

#60
post #46

> For those who received or signed a document through Dropbox Sign, but never created an account, email addresses and names were also exposed. So they also leaked data of people who are not their customers, and who never agreed to have their information collected. I doubt that flies under the GDPR.

In the grand scheme of things, expecting your name and email address to really stay private is not all that reasonable. You probably gave them to the person who then used Dropbox Sign to send you a document. If you were really worried you could have used a throwaway account. The old saying is, once you tell someone, it's no longer a secret.
Post reply on HN