You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A huge problem when publishing documents in the context of whistleblowing are metadata leaks. It seems currently the documents are directly fully published - without anyone taking care of protecting the whistleblower. The submission is only one of the deanonymization vectors. This is dangerous - especially as there is nothing like that indicting it on your website:
There it looks as it is safe and private to submit documents. You state: "Zikileaks helps advocates get sensitive documents published without fear."
I urge you to add a warning - this can cost life in the worst case.
And this is without a look in the source code - because this problem exists even with perfect code. And I guess as this is a hackathon project done in a haste - there are other problems hidden. And seeing that it is deployed on vercel instead of an onion service makes this feeling even stronger.
Also it is counter-productive to just publish the documents directly. This removes the incentive of journalists to look into it in the current system. And without journalists doing the next step after publishing - the publishing will very likely have no effect (other than endangering the whistleblower)
Please look into the works of previous whistleblowing projects before "improving" it. E.g. watch https://media.ccc.de/v/25c3-2916-en-wikileaks / https://media.ccc.de/v/26c3-3567-en-wikileaks_release_10 )
The text was updated successfully, but these errors were encountered:
Hey, ligi. Thanks for the feedback. This indeed was a hackathon project we built in <48 hours. There are for sure many improvements that can be made and we admittedly aren't experts in the field of helping whistleblowers. We didn't intend the project to be used IRL (it would need auditing and to not be on Vercel to say the least haha). We thought it was pretty obvious it was just a hackathon project but can add a disclaimer. We completely understand your feedback and appreciate your time digging into what we build. Thank you!
A huge problem when publishing documents in the context of whistleblowing are metadata leaks. It seems currently the documents are directly fully published - without anyone taking care of protecting the whistleblower. The submission is only one of the deanonymization vectors. This is dangerous - especially as there is nothing like that indicting it on your website:
There it looks as it is safe and private to submit documents. You state: "Zikileaks helps advocates get sensitive documents published without fear."
I urge you to add a warning - this can cost life in the worst case.
And this is without a look in the source code - because this problem exists even with perfect code. And I guess as this is a hackathon project done in a haste - there are other problems hidden. And seeing that it is deployed on vercel instead of an onion service makes this feeling even stronger.
Also it is counter-productive to just publish the documents directly. This removes the incentive of journalists to look into it in the current system. And without journalists doing the next step after publishing - the publishing will very likely have no effect (other than endangering the whistleblower)
Please look into the works of previous whistleblowing projects before "improving" it. E.g. watch https://media.ccc.de/v/25c3-2916-en-wikileaks / https://media.ccc.de/v/26c3-3567-en-wikileaks_release_10 )
The text was updated successfully, but these errors were encountered: