Hi, The SSHTM is not (yet) implemented in SNMP4J 2.0. Interfaces have been created to provide a hint for the upcoming implementation (which is in fact an integration of a 3rd party SSH implementation).
Since the implementation of such an integration is not finished yet, the interface may change however. Best regards, Frank On 26.08.2011 16:09, Stath, Paul wrote: > I'm glad to see support for Transport Security Model (RFC5591) in SNMP4J 2.0. > > It looks like communicating using TLS-TM (RFC6353) will work "out of the box" > with SNMP4J 2.0. > > However, it looks like communicating with a device supporting SSH-TM > (RFC5592), > will require more work. > > Firstly, it looks like only outgoing SSHTM connections can be creating using > DefaultSshTransportMapping(), since listen() is an empty method that doesn't > open any listen sockets, and isListening() always returns false. > > Since there is no implementation of the SshTransportAdapter interface, > it is rather difficult to construct the DefaultSshTransportMapping() class > with > the stock 2.0 SNMP4J library. (grin) > > Is it fair to say that the SSHTM implementation in SNMP4J is incomplete at > this point, or > would it be expected to work if implementations of the SshSession<I> and > SshTransportAdater<I> > interfaces were written to work with a 3rd party SSH java library like JSch or > Apache SSHD? > _______________________________________________ > SNMP4J mailing list > SNMP4J@agentpp.org > http://lists.agentpp.org/mailman/listinfo/snmp4j -- AGENT++ http://www.agentpp.com http://www.snmp4j.com http://www.mibexplorer.com http://www.mibdesigner.com _______________________________________________ SNMP4J mailing list SNMP4J@agentpp.org http://lists.agentpp.org/mailman/listinfo/snmp4j