| 1 |
On Fri, Jul 18, 2014 at 3:01 AM, Joshua Kinard <kumba@g.o> wrote: |
| 2 |
> On 07/17/2014 09:16, hasufell wrote: |
| 3 |
>> Rich Freeman: |
| 4 |
> |
| 5 |
> Doesn't eliminate the possibility of someone sleuthing around to eventually |
| 6 |
> link dev -> conf id, but in the event this happens in the future, the file |
| 7 |
> containing the linkages will only show hashes -> conf id. |
| 8 |
> |
| 9 |
|
| 10 |
Well, if you want to do something simple to obfuscate the dev->ID |
| 11 |
mapping, why not just have votify generate a random ID when creating |
| 12 |
the initial ballot, and store it in the ballot file? Then the dev |
| 13 |
knows what their ID is, since they can see it, and there is no need to |
| 14 |
email it to them. The only way for anybody else to find out is to go |
| 15 |
poking in home directories to look at the files. ID length would |
| 16 |
ensure uniqueness, or you could use a GUID of some sort. |
| 17 |
|
| 18 |
That is the approach those blind signing protocols use - the voter |
| 19 |
generates a unique ID and thus can ID their votes in the master |
| 20 |
ballot. All the extra magic in those designs allow them to do it |
| 21 |
without even infra being able to ID them, but you can get the |
| 22 |
user-generated-ID benefits easily enough without doing all the crypto. |
| 23 |
|
| 24 |
Rich |
Archives