Community
Participate
Working Groups
A boolean yes/no setting controlling whether an SSH agent shall be used at all. This can be implemented properly only once Apache MINA sshd 2.8.0 is released. Currently the framework is too opinionated to do this.
(In reply to Thomas Wolf from comment #0) > A boolean yes/no setting controlling whether an SSH agent shall be used at > all. I must have been asleep when I wrote this. It's not a yes/no setting. * 'none': don't use an agent. * 'SSH_AUTH_SOCK': use environment variable SSH_AUTH_SOCK. * otherwise (in OpenSSH): path to Unix socket file, with ~ and environment variable expansion. For Windows, it makes sense to support additionally: * 'pageant': use Pageant via its shared memory mechanism. * '\\.\pipe\*' : use a windows named pipe instead of an AF_UNIX socket (this is used by Win32-OpenSSH, the Microsoft port of OpenSSH available on modern Windows.) Maybe even allow 'openssh' as a shorthand for the default named pipe Win32-OpenSSH uses: \\.\pipe\openssh-ssh-agent. Note that on Windows, %SSH_AUTH_SOCK% _must not_ be set if Win32-OpenSSH is to be used. But that's a problem for the user, who has to set up his environment correctly. We might perhaps support 'SSH_AUTH_SOCK' to use a WinSocket2 AF_UNIX socket and try to talk to the git bash ssh-agent, even if the environment variable is not set.
Note: beware of backslash handling in OpenSSH config file parsing. It handles some backslash-escapes and collapes \\ to a single \. We might need to compensate for this, or users would need to do the escaping ("\\\\.\pipe\...") or use forward slashes on Windows. Also double-check what our "tilde expansion and relative filename" code does with a string starting with "\\" or "//": are these properly recognized as absolute (UNC) filenames on Windows and thus left unchanged? (OpenSSH handles backslash as an escape only for \\, \', and \", and outside of strings delimited by " or ' also for \ followed by a blank. All other backslashes are left alone, so \foo remains unchanged.)
New Gerrit change created: https://git.eclipse.org/r/c/jgit/jgit/+/189372
New Gerrit change created: https://git.eclipse.org/r/c/jgit/jgit/+/189373
New Gerrit change created: https://git.eclipse.org/r/c/jgit/jgit/+/189375
New Gerrit change created: https://git.eclipse.org/r/c/jgit/jgit/+/189374
New Gerrit change created: https://git.eclipse.org/r/c/egit/egit/+/189924
Gerrit change https://git.eclipse.org/r/c/jgit/jgit/+/189373 was merged to [master]. Commit: http://git.eclipse.org/c/jgit/jgit.git/commit/?id=071084818cae26fd3f1075d4e6763218197c94d5
Gerrit change https://git.eclipse.org/r/c/jgit/jgit/+/189375 was merged to [master]. Commit: http://git.eclipse.org/c/jgit/jgit.git/commit/?id=68bd2c146239b87d355ed6169ca0ec227a69995d
Gerrit change https://git.eclipse.org/r/c/jgit/jgit/+/189372 was merged to [master]. Commit: http://git.eclipse.org/c/jgit/jgit.git/commit/?id=4efc6a396af3f5a112dc87e708d339b51f376c1d
Gerrit change https://git.eclipse.org/r/c/jgit/jgit/+/189374 was merged to [master]. Commit: http://git.eclipse.org/c/jgit/jgit.git/commit/?id=e0281c5adb89f0b109abca57970c7b89df63ede4
Gerrit change https://git.eclipse.org/r/c/egit/egit/+/189924 was merged to [master]. Commit: http://git.eclipse.org/c/egit/egit.git/commit/?id=464dcc5e8dedeebdd6906d4607efb777c6fd75c9