Update instructions for Sonoma 14.6+ (#54) #56
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Fixes #54 (well, works around the new normal).
This documents the workarounds I've provided here, which is the only way that works with Apple's stock
ssh-agentLaunchAgent configuration and does not rely on exploitinglaunchdsecurity weaknesses.The Homebrew formula will need to be updated to patch the new default paths in the plist: theseal/homebrew-ssh-askpass#20
I've made a couple of changes to the plist, because they have no effect on Apple
ssh-agentSonoma 14.6 and later:DISPLAYwithlaunchctl setenvcom.openssh.ssh-agent(Apple'sssh-agent)The Homebrew formula could be replaced with a cask to automate this stuff. I'll add an issue for that later.
This should work even if you installed your own
ssh-agentto replace Apple's, as long as it checks/usr/X11R6/bin/ssh-askpass.While this doesn't fix usage of third-party authentication modules like FIDO2, that's totally unrelated to
ssh-askpass.Feedback needed
This assumes that MacPorts always installs toIt's been/usr/local/bin. Homebrew uses different paths on Apple Silicon and Intel./opt/localfor at least a decade, fixed.