3 ms·
Oh great. More security theater. This should be a per repository setting. Not system wide! If someone has a "threat model" where "passwords are bad" then fine.
by ok123456 5y ago
Oh great. More security theater.
This should be a per repository setting. Not system wide! If someone has a "threat model" where "passwords are bad" then fine. Force users interacting with that particular repository to deal with this security theater of making tokens which have the same power as the account that authorized them. I guess they have better granularity, but in practice anything more complicated that Unix permissions is a total disaster and just leads to people not understanding what the different levels actually mean.
It shouldn't be imposed top-down on every user.
- jatone 5y agothey just don't want to maintain that code path anymore for whatever reason. its their product, their choice. you're just along for the ride.