andrewcmyers/civs

Some email addresses can be entered twice and they'll receive two voting keys

mweinelt opened this issue · 14 comments

Hi, we're trying out the hosted CIVS and for some reason we can sometimes add email addresses again and that will result in them receiving multiple voting keys.

What we did was:

  1. Import bulk list of addresses (n authorized voters)
  2. Add some email addresses again, these addresses didn't appear as authorized and therefore got additional keys (now n+m authorized voters)

I'll gladly provide more input when you tell me what you need.

Are all the voting keys a given email receives the same? That would be harmless.

No, that's the thing, they aren't. I'll gladly forward you those mails. For example these two:

https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_4f44cbb02982d36c&key=715a64b4d248d7fd
https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_4f44cbb02982d36c&key=79a37530650a668d

Please do send those to me by email. Thanks.

They're on their way.

I have tried to follow your instructions but I haven't been able to reproduce this bug so far. Any non-default settings on the poll I should know about?

Uhm, private poll with extended ballot reporting. E-mail address of supervisor always matched that of one participant. Besides that nothing.

And suddenly I can't seem to repro anymore. 😞

Is it possible you confused keys coming from two different polls? Different polls generate entirely different keys for the same voters.

#39 (comment)

As you can see in this post I got two different keys for the same id. I guess that means two votes in the same poll.

Those were taken from the "Poll: The Chaotic Primary II" mails.

Okay, we can still reproduce this and can demo this in a Jitsi Meet screensharing session or create a screencast (have to look into how to do what on wayland though).

Edit: OBS studio did the trick, link on it's way to you.

Hey, I haven't heard back yet. Have you received the video? Could you confirm the issue yet?

Great, just wanted to make sure there was no problem at my end.

Found the bug. Sometimes Perl semantics are really error-prone! Thanks a lot for creating the video, which let me reproduce the bug once I followed it to the T!