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.

Sign up for GitHub

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

Jump to bottom

Authentication / Integrity #3

Open
stuartpb opened this issue Nov 1, 2017 · 1 comment
Open

Authentication / Integrity #3

stuartpb opened this issue Nov 1, 2017 · 1 comment

Comments

@stuartpb
Copy link
Member

stuartpb commented Nov 1, 2017

I'm thinking it might make sense to require praisefile commits to be GPG authenticated, so people can't just go forging commits that skew people's words (or, worse, forging praisefiles altogether, in a twisted and wrong realization of prasefiles' intended purpose).

Furthermore, I've been thinking it might make sense to have a mechanism to ensure that, if the author of a praisefile wishes to amend what they said for whatever reason, the presence of that amendment is highly visible (so their earlier statement can't be misrepresented as reflective of their current feelings).
@stuartpb
Copy link
Member Author

Considering that GitHub GPG authenticates all commits made via the web interface, I'd say this isn't so unreasonable of a requirement these days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stuartpb