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

AIP 5: Forging Secret #6

Closed
Doweig opened this issue Feb 1, 2017 · 5 comments
Closed

AIP 5: Forging Secret #6

Doweig opened this issue Feb 1, 2017 · 5 comments

Comments

@Doweig
Copy link
Contributor

Doweig commented Feb 1, 2017

Forging Secret, you would need both passphrases to generate a secret, that secret would be stored in the config.json and is what enables you to forge. That secret would prove your identity and includes a nounce (number). So if your server gets hacked you can generate a new secret with nounce + 1 so the previous secret (the one that was hacked) is not usable anymore. That way no more passphrase on servers, would also solve the forging/voting account separation. Since no key on server anymore, there’s no need to separate those accounts

@2mdoty
Copy link

2mdoty commented Feb 2, 2017

This would be a big improvement, so you don't lose your delegate name and brand if hacked.

@axenter
Copy link

axenter commented Oct 24, 2017

@fix Would something like this be possible with the new AIP11?

@reConNico
Copy link

@fix : Someone has this on his mind? Maybe in another way but this would be awesome to get more security for delegates.

@doubled1c3
Copy link

Seems beneficial

@zillionn
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants