Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Election keyword #11

Open
umbernhard opened this issue May 27, 2014 · 4 comments
Open

Election keyword #11

umbernhard opened this issue May 27, 2014 · 4 comments

Comments

@umbernhard
Copy link
Collaborator

We need to investigate whether or not an election keyword is needed in the STAR-Vote process.

@umbernhard
Copy link
Collaborator Author

The original design of the keyword was to mandate that no unknown parties could run valid STAR-Vote machines on the network and futz with the network. So In theory we do need the keywords. They are sent back in forth in certain messages, but it seems to me they should be sent with all messages. I'll investigate more later.

@umbernhard
Copy link
Collaborator Author

Pending consultation.

@mpk2
Copy link
Collaborator

mpk2 commented Jun 30, 2014

We're going to be re-implementing keywords.

@umbernhard
Copy link
Collaborator Author

So I've reimplemented the keywords they way they used to be in votebox. However, from what I can tell they don't really do anything. They simply prevent a new supervisor from hearing a polls open message after sending a PollOpenQ message; they can still open and close the polls, send ballots, etc.

I'm not sure of the value of the keyword, since a machine can't join the network without the proper credentials (certificate and signature). Theoretically that should take the place of the keyword.

If we want to use keywords to enforce more security, we're going to run into trouble fast. If a supervisor comes online with the wrong keyword, the only options are to disconnect it from the network, which right now other machines can't do, or to broadcast an ignore status, which I suppose would be technically possible, but introduces some problems. For instance, if the bad supervisor hears the ignore, it could just restart itself and try to send a message before the next ignore message is sent. I'll have to consult on this.

umbernhard added a commit that referenced this issue Jul 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants