Linux standalone builds put the bundled ssh last in PATH, so any system ssh will be preferred over it.
This commit was sponsored by Denis Dzyubenko on Patreon.
This commit is contained in:
parent
d797f750e4
commit
11d3219985
4 changed files with 33 additions and 9 deletions
|
@ -51,3 +51,4 @@ git-annex: sync: 2 failed
|
|||
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
|
||||
|
||||
|
||||
> [[done]]; moved ssh to extra directory. --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,20 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 1"""
|
||||
date="2017-03-02T21:30:55Z"
|
||||
content="""
|
||||
One way to deal with this would be to put the bundled ssh in the
|
||||
git-annex.linux/extra/ directory. Programs in that directory are added to the
|
||||
end of the path, so that system versions will be preferred when available.
|
||||
|
||||
That was earlier done for gpg and didn't cause any problems.
|
||||
|
||||
There is the potential for some sort of versioning problem. Currently the
|
||||
only thing git-annex probes about the bundled ssh is if it supports
|
||||
connection caching. That's quite an old feature by now, so a system ssh not
|
||||
supporting it would either be super out of date and insecure openssh, or
|
||||
perhaps some other ssh implementation.
|
||||
|
||||
Seems worth moving the bundled ssh to the extra directory, and see what
|
||||
breaks..
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue