Probably your perspective also varies depending on whether you’re a server who has to let popular clients connect somehow (or suffer complaints) or someone seeking a client which is ahead of the broader pack.
So that might be the best of what SSH.NET can do. Interestingly, they still recommend diffie-hellman-group14-sha1 (for now, due to availability problems for better algorithms) and so does SSH.COM.
the global standards body for such things) advice about KEX algorithms. Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH) is an effort to update IETF (Internet Engineering Task Force – a.k.a. No secure HMAC algorithms offered for SSH/SFTP seemed to say that obviously the library gets replaced, however it offers no specific suggestions for something compatible with open source. Duplicati at least keeps changing code even though the issues list sometimes seems to have no bottom… Duplicati’s lead author did do AES in C#, but I don’t know if he or anyone else here can add new KEX code. Feel free to add your comments, but I don’t see much recent code change activity. We’re definitely starting to feel the pressure of SSH.NET as a dependency # Only use strong key exchange algorithms, cipers and MACs Please have a look at the following URL: ITNerdbox/hardening-configurations/blob/master/sshd_config #-# Since the key exchange algorithms uses the sign it thinks I am sending a lot of links in a post. As a new user I am limited to the amount of links in a post.
0 kommentar(er)
