You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by fasmide November 24, 2022
So, in light of #12 I've been thinking about how to authorize remote.moe's users without getting too much in the way
One way of doing it could be leveraging GitHubs public key API https://github.com/<username>.keys and use these keys for identification of users
At the moment, remotemoe does not use the username for anything, it shouldn't be a problem to have users provide their GitHub username and then lookup their keys on the fly
The text was updated successfully, but these errors were encountered:
Discussed in #14
Originally posted by fasmide November 24, 2022
So, in light of #12 I've been thinking about how to authorize remote.moe's users without getting too much in the way
One way of doing it could be leveraging GitHubs public key API
https://github.com/<username>.keys
and use these keys for identification of usersAt the moment, remotemoe does not use the username for anything, it shouldn't be a problem to have users provide their GitHub username and then lookup their keys on the fly
The text was updated successfully, but these errors were encountered: