GPG should become the default-standart way of authorization in m8sh for following reasons:
It is much more secure then password, and does not require to remember extra passwords, except GPG
It does not require central institution to prove the user identity, and does not require to rely on that
It allows user to prove his indentity on any node on the network in a single step
When modern browser clients (which would be developed in that project later) will support integrated GPG - won't even have a need in running local commands (though - they would be supported for backward compatability)
Integration includes following actions:
Remove all endpoints related to other form of registration and authorization from GPG
Remove settings and ui representation for other registration/auth methods
Add an endpoint to give a full user's gpg armor (chained)
Add an endpoint to validate user's GPG key against registration possibility
Add a public endpoint to generate a nonce for a user's signature
Add a GPG registration endpoint
Add a GPG login endpoint
Change registration and login UI to use GPG (including initial setup page)
Add translations
WIP 🔨
GPG should become the default-standart way of authorization in m8sh for following reasons:
1. It is much more secure then password, and does not require to remember extra passwords, except GPG
2. It does not require central institution to prove the user identity, and does not require to rely on that
3. It allows user to prove his indentity on any node on the network in a single step
4. When modern browser clients (which would be developed in that project later) will support integrated GPG - won't even have a need in running local commands (though - they would be supported for backward compatability)
Integration includes following actions:
1. Remove all endpoints related to other form of registration and authorization from GPG
2. Remove settings and ui representation for other registration/auth methods
3. Add an endpoint to give a full user's gpg armor (chained)
4. Add an endpoint to validate user's GPG key against registration possibility
5. Add a public endpoint to generate a nonce for a user's signature
6. Add a GPG registration endpoint
7. Add a GPG login endpoint
8. Change registration and login UI to use GPG (including initial setup page)
9. Add translations
WIP 🔨
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
GPG should become the default-standart way of authorization in m8sh for following reasons:
Integration includes following actions:
WIP 🔨
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.