4 ms·
The contract you are required to agree to view the source code [0] is unreasonable: It requires that you work for free if you think you find a problem (i.e. yo
by gpm 8y ago
The contract you are required to agree to view the source code [0] is unreasonable:
It requires that you work for free if you think you find a problem (i.e. you are not allowed to just stop):
> Participants who have found or believe they have found a vulnerability are obliged to submit a report in the GitLab platform as an issue set explicitly to confidential
> Researchers shall provide sufficient information to reproduce the Vulnerability so that the Owners can act as quickly as possible. Usually, a vulnerability description is sufficient, but for more complex vulnerabilities, more detailed information may be needed.
> The Researcher accepts to provide support to the Owners to verify the potential Vulnerability,
It requires that you agree to an indefinite NDA, that extends to not disclosing issues you discover:
> No Vulnerability shall be published within a period of forty five (45) days since the last communication exchanged with the Owners with regards to such potential Vulnerability, unless the Owners have agreed to a shorter period or defined a longer period.
(In other words they can extend the NDA indefinitely by pinging you every 45 days, and the last sentence means they might not even need to bother pinging you every 45 days). Also:
> the information received in the Researcher e-mail account must not be shared with or forwarded to any other e-mail account.
It requires that you are not a company (or government) or acting on behalf of one, despite various companies providing, for free, some of the best security research (see project zero)
> Registration for the Program is open to all natural persons willing to comply with the Agreement, with the exception of natural persons who do not act under their own responsibility, but as employees, civil servants, officers or any other subordinate capacity. Registration is therefore not open to organizations, associations, institutions, administrations, governments, government agencies, foreign states, or any other entity that is not a natural person.
On the contrary to the article (which currently states "The source code is published permanently to ensure Swiss Post meets the legal requirements."), source code access is not permanent, but only until the end of the production release. I.e. research into past vulnerabilities appears to be forbidden:
> The Agreement and Source Code Access expires at the termination of the productive use of the release to which the Program is dedicated.
I'm not a lawyer, I'm certainly not a Swiss lawyer, but it is my understanding that the purpose of this program is to comply with article 7a and 7b of [1] (which is linked from [0]). I hope someone who is a Swiss lawyer (some equivalent of the EFF) is looking closely at this, because I don't see how it complies. I don't see how it can be said that "The source code for the system software must [has] be[en] made public" when companies are not allowed to view it and access is temporary. I don't see how it can be said that "Anyone is entitled to examine, modify, compile and execute the source code for ideational purposes, and to write and publish studies thereon." when you aren't allowed to publish vulnerabilities until they choose to release you from the indefinite NDA you signed.
[0] https://www.post.ch/-/media/post/evoting/dokumente/nutzungsbedingungen-quellcode.pdf?la=en&vs=1 https://www.post.ch/-/media/post/evoting/dokumente/nutzungsb...
[1] https://www.bk.admin.ch/dam/bk/de/dokumente/pore/Federal_Chancellery_Ordinance_on_Electronic_Voting_V2.0_July_2018.pdf.download.pdf https://www.bk.admin.ch/dam/bk/de/dokumente/pore/Federal_Cha...
- nairboon 8y agoThis program doesn't comply with VEleS 7b but it doesn't have to, yet. The requirement for publishing the source code only applies when the system is actually authorized for a real trial.
- gpm 8y agoOh, interesting. Do you know what sort of time frame a "real trial" will happen in? I'd love to give the source a once over when I can do so on reasonable terms.
- nairboon 8y agoI don't know about the time frame, there is a current proposition which would allow e-voting at the national level which is up for public comments until the 30.4.2019, but then it'll go back to parliament and at some point should be up for a vote. So it may take another year or two. But you can check out the source code as it is, the lawyers of swiss post just added all kinds of random stuff to that TOS. I think this TOS only applies if you participate in the pentest. Otherwise it makes absolutely no sense. The propositions that the researchers shall conduct tests etc. would create a contract for work, which only applies for the pentest due to the potential compensation. But Swiss post clearly state that they publish the source code to comply with VEleS 7a, therefore it is public as in "It must be easily obtainable, free of charge, on the internet." any restrictions like we must conduct tests is clearly a charge and thus not valid with 7a.
- gpm 8y agoAccess to the source without participating in the pen test is clearly governed by the contract I linked, both because that's what the page you need to click through to access the source says [0], and there is a different contract governing participants in the pentest [1]. I'm frankly more concerned with the indefinite NDA than the "you must continue to work for free clause". I'm reasonably confident that Swiss law doesn't allow for a clause to force me to work without compensation, and I'm quite confident that local law does not regardless of what Swiss law says. The indefinite NDA though strikes me as legally valid, and could plausibly put me in a situation where I'm stuck between keeping silent about vulnerabilities and civil disobedience [2]. I emphasized "without participating in the pen test" above because I just noticed an amusing loophole in the contract that makes the NDA somewhat (not completely, and still not the rest of the contract) reasonable.... The pen test agreement states > If you sign up to the source code access programme and there is a conflict between the E-Voting Solution Source Code Access Agreement and the TC&CoC, the latter shall take precedence. It also states > Participants / researchers are allowed to publish their findings following a publication date agreed with the organizers. This date will be 45 days after the initial confirmation of the reported finding at the latest. As such I think if I sign up for both programs the NDA on disclosing vulnerabilities is not indefinite. [0] https://www.post.ch/en/business/a-z-of-subjects/industry-solutions/swiss-post-e-voting/e-voting-source-code?shortcut=evoting-sourcecode https://www.post.ch/en/business/a-z-of-subjects/industry-sol... [1] https://onlinevote-pit.ch/conduct/ https://onlinevote-pit.ch/conduct/ [2] A similar example in Finland where companies and government agencies conspired to try and keep vulnerabilities secret: https://www.reddit.com/r/talesfromtechsupport/comments/9m8fzj/cant_approve_payroll_blackhat_sysadmin_when_my/ https://www.reddit.com/r/talesfromtechsupport/comments/9m8fz... This story is largely verifiable via Google - The author has asked that his reddit account/recounting not be directly linked to his name, please respect that here as well.