Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
max1993138810dUser input on keyring access, to hinder keyring dumping by effectively informing the user about access attempt, most have it encrypted and this gui ask for master password!
-
netikras3554410d@max19931 access attempt...? Why would it try to access the logged in user's keyring?
I'm doing git clone with a repo token for auth.Why the hell does it even touch the GUI session's keyring..? wtf does it need from it? -
max199313886d@netikras repo Token was likely dropped into keyring or how do you think macos x stored Passworts!
-
@max19931 why did it drop it to keychain...? I passed it as a cli arg and expected it to be used for that invocation alone -- I did NOT ask it to do anything with secrets' caching/storing/fetching/doing anything with kc.
Genuine question. -
@max19931 can't check it ATM. However, while git was frozen in the UI I saw interactive popups saying that it could not find some key in a KC. And it only after I close that popup by clicking on Cancel (or smth like it) and doing the same for all the other similar popups does the git command unfreeze.
It's a freshly installed MAC dedicated host (AWS).
I still fail to see how this is a security measure...
I'm assuming that if git found those ci/cd keys in KC it would not prompt me for anything in UI...
Related Rants
Soo.. over the span of 1 month, x2 MAC servers have died (hardware failure). I'm in progress of setting up the third one.
What a dumb fucking system MacOS is!!! wtf...
I've spent 4+ hours trying to figure out why the fuck `git clone` is getting stuck and timing out our CI runs.
Turns out, on MacOS you cannot run git clone via ssh IF you have that user logged in via GUI (e.g. VNC). Git is getting stuck at
11:51:26.084245 run-command.c:759 trace: start_command: /opt/homebrew/opt/git/libexec/git-core/git-credential-osxkeychain store
and just chilling there doing nothing, waiting for the user to click on a Cancel button in GUI.
Logged out my VNC session and git magically started working.
What a dumb system... Or perhaps I'm misunderstanding this "security" feature...?
rant
server
devops
git
wtf
keychain
freeze
apple
aws
macos
ci