Juniper/go-netconf

Plan on v2 of the library

Closed this issue · 1 comments

I think it may be a good idea to tag a v1 of the API and start working on breaking API changes in v2.

  • Remove ssh.ClientConfig wrappers. Some of these are setting InsecureSkipVerifyHostKey() which is a bad choice to make security decisions for end users (and why it was set as a breaking change in x/crypto/ssh

Dup of #24