I don't think it's actually used (looks like you need to jump through hoops to activate a different agentproxy implementation). And it is easy enough to exclude this with code such as [5] if that's the case. That is working for us currently. (Note jna is pulled in by pageant as well as usocket-jna).
Thanks for pointing this out, Alex! It should be hopefully easy to test whether we can
a) Exclude com.jcraft:jsch.agentproxy.usocket-jna and pageant. The latter might be useful for people running on Windows, but not sure if the pain is worth it? b) Exclude jna from those two and explicitly add the newer version, which should get rid of the problem
From what I understand, jclouds releases themselves shouldn't have a problem as this is a dependency, not code we are shipping. But of course it *does* affect any downstream users bundling this, and we want to get resolve this asap, for sure.
@nacx: you were testing the agentproxy stuff at some point, if I recall? Do you think we could get away with just sshagent for now, or are you aware of anyone that needs pageant?
ap
