HEADSUP: SSHD service rename

HEADSUP: SSHD service rename

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]

Since Microsoft decided to name their own sshd service "sshd", too, we
don't have much choice than to rename our service after 16+ years.

https://github.com/PowerShell/Win32-OpenSSH/issues/1331

My patch has been accepted upstream so starting with OpenSSH 8.0, newly
installed Cygwin sshd services will be called "cygsshd" by default,
unless Microsoft renames their service yet :}

Of course, systems with already installed Cygwin sshd service will keep
the service name, even after an update to OpenSSH 8.0.

As some people (including myself) already experienced, an update of your
W10 system to 1809 may break your sshd service.  The OS update
apparently overwrites an existing sshd service with its own sshd service
without asking.  You can just remove the Windows sshd with

  $ cygrunsrv -R sshd

and reinstall Cygwin sshd, or you reinstall Cygwin sshd under another name:

  $ ssh-host-config -n cygsshd   (pre OpenSSH 8.0)
  $ ssh-host-config              (OpenSSH 8.0 or later)


Sorry for the hassle,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: HEADSUP: SSHD service rename

[Steven Hartland]

On 28/01/2019 09:00, Corinna Vinschen wrote:
> Since Microsoft decided to name their own sshd service "sshd", too, we
> don't have much choice than to rename our service after 16+ years.
>
> https://github.com/PowerShell/Win32-OpenSSH/issues/1331
>
> My patch has been accepted upstream so starting with OpenSSH 8.0, newly
> installed Cygwin sshd services will be called "cygsshd" by default,
> unless Microsoft renames their service yet :}
>
> Of course, systems with already installed Cygwin sshd service will keep
> the service name, even after an update to OpenSSH 8.0.
>
> As some people (including myself) already experienced, an update of your
> W10 system to 1809 may break your sshd service.  The OS update
> apparently overwrites an existing sshd service with its own sshd service
> without asking.  You can just remove the Windows sshd with
>
>    $ cygrunsrv -R sshd
>
> and reinstall Cygwin sshd, or you reinstall Cygwin sshd under another name:
>
>    $ ssh-host-config -n cygsshd   (pre OpenSSH 8.0)
>    $ ssh-host-config              (OpenSSH 8.0 or later)
>
>
> Sorry for the hassle,
> Corinna
Thanks for the heads up its a real pain MS did that, caused me issues a 
few times.

Also watch out for broken firewall rules after this change.

     Regards
     Steve

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: HEADSUP: SSHD service rename

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

On Jan 28 09:03, Steven Hartland wrote:
> On 28/01/2019 09:00, Corinna Vinschen wrote:
> > Since Microsoft decided to name their own sshd service "sshd", too, we
> > don't have much choice than to rename our service after 16+ years.
> > 
> > https://github.com/PowerShell/Win32-OpenSSH/issues/1331
> > 
> > My patch has been accepted upstream so starting with OpenSSH 8.0, newly
> > installed Cygwin sshd services will be called "cygsshd" by default,
> > unless Microsoft renames their service yet :}
> > 
> > Of course, systems with already installed Cygwin sshd service will keep
> > the service name, even after an update to OpenSSH 8.0.
> > 
> > As some people (including myself) already experienced, an update of your
> > W10 system to 1809 may break your sshd service.  The OS update
> > apparently overwrites an existing sshd service with its own sshd service
> > without asking.  You can just remove the Windows sshd with
> > 
> >    $ cygrunsrv -R sshd
> > 
> > and reinstall Cygwin sshd, or you reinstall Cygwin sshd under another name:
> > 
> >    $ ssh-host-config -n cygsshd   (pre OpenSSH 8.0)
> >    $ ssh-host-config              (OpenSSH 8.0 or later)
> > 
> > 
> > Sorry for the hassle,
> > Corinna
> Thanks for the heads up its a real pain MS did that, caused me issues a few
> times.
> 
> Also watch out for broken firewall rules after this change.

Good point! 👍


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: HEADSUP: SSHD service rename

[JZeman]

When I try to install Cygwin sshd, it creates the cygsshd service in windows
however, it isn't creating the cyg_server account or any other account. It
wants to use the System account. 

Is that a new item as well? I ran sc.exe delete sshd and don't have any sshd
service installed or listed in Windows services. 

referencing these two links:
http://cygwin.1069669.n5.nabble.com/HEADSUP-SSHD-service-rename-td143990.html
https://github.com/PowerShell/Win32-OpenSSH/issues/1331



--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: HEADSUP: SSHD service rename

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

On Apr 22 14:28, JZeman wrote:
> When I try to install Cygwin sshd, it creates the cygsshd service in windows
> however, it isn't creating the cyg_server account or any other account. It
> wants to use the System account. 

https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1

Also see the OpenSSH release message section "Portability" at
https://cygwin.com/ml/cygwin-announce/2019-04/msg00017.html

So, yes.  Using the SYSTEM account instead of cyg_server is correct.
We now use S4U authentication rather than trying to create our own
user token.  We only invented cyg_server to workaround the issue
that SYSTEM services are not allowed to create user tokens starting
with Windows Server 2003.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]