On Sat, Jan 26, 2019 at 5:07 PM Corinna Vinschen <vinschen@xxxxxxxxxx> wrote: > > Microsoft hijacked the sshd service name without asking. How many people use the SSH daemon from Cygwin, versus using only the client? I did some work with the daemon with rsync and tar, trying to link it to Linux backup systems. It was unreliable due to anti-virus interfering with warning when upgraded, and the workarounds being eliminated from the anti-virus software. As a server, it also had problsm doing scp, sftp, or rsync reliably due to Windows file locking, so it wasn't as effective or useful as one might nope. In other words, is this a big loss if Microsoft accidentally kills Cygwin sshd ? Is Microsoft going to use port 22? If there is a conflict, will CygWin defer to Microsoft as the vendor and use an alternate port? Nico Kadel-Garcia <nkadel@xxxxxxxxx> _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
