Yes, I noticed how the SSH code likes to insist on Bouncy Castle; any work on that would be appreciated.
In a similar vein, I've got my prototype for SSHD-211 (RFC compliant mechanism for adding custom services) to the point where it "works for me". Code is at https://github.com/cagney/mina-sshd-service/commits/master . If someone could look at SSHD-214, SSHD-215, SSHD-218, SSHD-220, and SSHD-221 (patches included); I can see about extracting patches for SSHD-222 and SSHD-223. On Wed, May 15, 2013 at 4:46 PM, Guillaume Nodet <[email protected]> wrote: > I don't think there are any plans to implement those, but I don't see why > those would not fit well into SSHD, so you're more than welcomed to work on > these RFCs. > > > 2013/5/15 Jeffrey Hawkins <[email protected]> > >> Is there a roadmap to support a broader technical compliance to the SSH >> IETF >> RFCs. In the nearer term, I am interested in additional Transport Layer >> Key Exchange >> Algorithms (RFC4523, RFC4419, RFC4432) and Transport Layer Integrity >> Checking Algorithms (RFC6668). Longer term I/we are interested in support >> of Suite B >> Cryptography (RFC6239). The Support of these would make MINA SSHD viable >> for Application environments requiring stronger cryptography SSH. If no >> plans, then I/we may be able to contribute effort towards adding this >> functionality via patches, assuming the MINA Project feels this is >> acceptable. >> Thanks,Jeff
