<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Both of these ideas are good ideas. I am using Infiniband for my cluster communications and would also prefer to disable encryption.</div><div><br></div><div>Using ~/.ssh/config instead of hard coding ciphers would be a simple way to implement the ssh cipher config.</div><div><br></div><div>Or just remove the hard coded ciphers and inform users how to create an ssh config file to set their preference.</div><div><br></div><div><br></div> <br>Stefan Priebe - Profihost AG <s.priebe@profihost.ag> wrote:<br>Hi,<br><br>is it planned to have a central cipher configuration for all ssh tasks?<br><br>Or maybe even use netcat for migration stuff instead of ssh on trusted <br>networks?<br><br>I've a patched openssl version running which supports aes-ni so i would <br>like to use aes128-cbc instead of blowfish but right now i've to change <br>a lot of scripts to archieve this for proxmox.<br><br>Greets<br>Stefan<br>_______________________________________________<br>pve-devel mailing list<br>pve-devel@pve.proxmox.com<br>http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel<br></body>