search

fluencelabs / dev-rewards

Apache License 2.0
554 stars 368 forks source link

Use standard Github oauth for authentication #103

Open juangirini opened 3 months ago

juangirini commented 3 months ago

Following up on https://github.com/fluencelabs/dev-rewards/issues/48, it seems to be impossible for some developers to authenticate themselves by decrypting with age, particularly for those who sign with a yubikey.

Using oauth to authenticate against Github is a lot more user-friendly, more developers would be able to claim their rewards (those that now can't) and also would seem less dangerous for those worried about exposing their private keys.

boneyard93501 commented 3 months ago

not going to happen.

dvdplm commented 3 months ago

So let get me get this straight: contributors that strive to run a tight ship and use good security practices are the ones that you choose to penalize? That doesn't really make any sense. A better answer would be "We are looking into alternative solutions for our yubikey using contributors and will report back asap."

/cc @alari

silence48 commented 2 months ago

Github deleted my ssh keys for inactivity yet people commit a Readme to some shitcoin get to participate simply bc they used ssh instead of https? Not great planning. Will get ready for influx of shit prs too from farmers loading up for the inevitable fork of this project and their airdrops.

tupui commented 2 months ago

Oauth should definitely be the way to authenticate. Everything is wrong with the current setup as we all basically need to audit your code before doing anything. It's also just showing bad practices to other projects...