ROS 4.16 supports both protocol 1 and protocol 2. Its ssh daemon is based on an ancient OpenSSH release (2.3.0); ROS 5.0rc6 supports protocol 2 only so it seems based on, at least, OpenSSH 5.4. In fact, we decided disabling legacy protocol 1 by default on march's release after a transition period of ten years. Support for protocol 1 has not been removed from OpenSSH's source code, only disabled by default in the configuration files.I've downgraded from v5rc6 to v4.16 and now I get this error when ssh-ing into the system: " Protocol major versions differ: 2 vs. 1 "/ I also noticed that when the system first boots after the downgrade, it only generates an RSA key. After a clean v4.16 install, everything works fine.
"Write failed: Broken pipe" means that packet_write_poll() cannot write some of the output on a socket because there is no process to read the data on the other side. I would suggest (1) trying another sftp client, and (2) to make sure this is not a ROS-specific problem transferring a file to a BSD or Linux system running OpenSSH 5.4 up to 5.6 (as you noted, this problem does not happen with SSH service on 4.13).I don't know if it's a bug or I need to configure something, but when I try to execute a script over ssh that is ~850 lines long in v5rc6, I get the message "Write failed: broken pipe". The script is with customer firewall and queue rules. The same script had no problem on v4.13 and if I shorten it to just a few customers (3 out of all 70) it works fine. (didn't try to see how many would work)
Any ideeas?
Hello,
OK, we will increase the maximum length.
Regards,
Normunds
My post was about work arounds, SSTP offers nothing other than being simple, if you need secure stable VPN right now work around it, 5.0 is not for production deployment!SSTP is still new and really does nothing new compared with L2TP and PPTP etc.
Wow. You might wanna watch what you say when comparing L2TP/PPTP to an actual secure VPN solution..
My post was about work arounds, SSTP offers nothing other than being simple, if you need secure stable VPN right now work around it, 5.0 is not for production deployment!SSTP is still new and really does nothing new compared with L2TP and PPTP etc.
Wow. You might wanna watch what you say when comparing L2TP/PPTP to an actual secure VPN solution..
I just noticed a post about that a little before mine, so it's likely I was in the middle of my post and started on something when that got posted.Save your efforts. The User Manager RC5 and RC6 is not working at all. Don't you read the posts here?