Re:Remote Code Execution in OpenSSH’s forwarded SSH-agent
by throwawaaarrgh on Wednesday July 19, 2023 @02:41PM
(#36791232)
or you could just use the -c option to ssh-add and be prompted every time the key is handed over
Re:Remote Code Execution in OpenSSH’s forwarded SSH-agent
by gorkish on Wednesday July 19, 2023 @02:30PM
(#36791063)
The RCE is related to ssh-agent's support for PKCS#11, so, yeah you are right this is a valid method to prevent key access or theft via the agent (I also have to approve every use of my PK), but in this case it's not protecting against the RCE, and the workaround in the meantime is to disable PKCS#11 `ssh-agent -P ''`
Re:Remote Code Execution in OpenSSH’s forwarded SSH-agent
by toast0 on Wednesday July 19, 2023 @04:12PM
(#36792499)
The other downside is it's much harder to do bulk operations against a fleet. It's not reasonable to enter a PIN for each access when you need to push something to 1000 nodes. 100 nodes is probably ok, but not great.
Re:Remote Code Execution in OpenSSH’s forwarded SSH-agent
by gunapologist99 on Wednesday July 19, 2023 @04:23PM
(#36792673)
That won't save you for this RCE!
Re:Remote Code Execution in OpenSSH’s forwarded SSH-agent
by themoonisachees on Thursday July 20, 2023 @05:26AM
(#36798406)
It will save his keys though. It's a start.
Re:Remote Code Execution in OpenSSH’s forwarded SSH-agent
by gunapologist99 on Thursday July 20, 2023 @12:40PM
(#36803118)
It is a start, true, but it's already game over: if I can execute code on your box, then the keys are the least of the treasures I've uncovered.
I can initiate connections, keylog, request or hide confirmations, steal all your other data, piggyback on your authorized SSH connections, etc.
The downside is that compatibility in edge cases, while much better than I'd expect, is still not perfect. In particular Windows support outside of Putty gets challenging.