delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2019/02/20/17:43:57

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; q=dns; s=
default; b=CxKoQYyI9HVVZXN1dfPrv2qx8lQMUXyx/UC61ZshukMwvJSu8v9C1
csVEfFNBROgltbx51USmU0SiVsQR//6ptPA0zxDH7g2CgyoJEtIF5j7D/HsSLE4/
dVJJk1jv6G3nW0MXa5PduFTT2HnfZqJU/UlH2L/CSoGlvx1KZr1iTQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; s=default;
bh=jCPsSF0zfkJSy6efTZTTC4tthWo=; b=xCiWmttpUnCSbJP2YhtQM4gcKlaM
DWwVjo5hrYrpd1AO/bLBgSaHjJcjtgQdQrC+qjLWph6W6HPURwi1sV4OeJY84D9Q
WV3cVNYTwcgIZK6p7728L2gzoRkYK+g/U7wZLTpikOz9yAYEKwENAE4hBPre0I27
6gXT2BO/Egu+xe4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-100.9 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=privileges, probability, H*F:D*cygwin.com, click
X-HELO: mout.kundenserver.de
Date: Wed, 20 Feb 2019 23:43:40 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
Message-ID: <20190220224340.GC4256@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <19759126 DOT 568100 DOT 1550686604174 DOT ref AT mail DOT yahoo DOT com> <19759126 DOT 568100 DOT 1550686604174 AT mail DOT yahoo DOT com> <alpine DOT DEB DOT 2 DOT 21 DOT 1902201038580 DOT 32163 AT ckhb05> <47883ab06634fed3ecdaa375016dc3fb AT smtp-cloud8 DOT xs4all DOT net> <20190220202536 DOT GX4256 AT calimero DOT vinschen DOT de> <vz1pnrmnoat DOT fsf AT gmail DOT com> <cf5bae0d3d06c3bb508cc766c5c18226 AT smtp-cloud8 DOT xs4all DOT net> <20190220223629 DOT GA4256 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
In-Reply-To: <20190220223629.GA4256@calimero.vinschen.de>
User-Agent: Mutt/1.10.1 (2018-07-13)

--Ht+/lPZLak6eP81R
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb 20 23:36, Corinna Vinschen wrote:
> On Feb 20 22:49, Houder wrote:
> > On Wed, 20 Feb 2019 21:27:22, Andy Moreton  wrote:
> >=20
> > > I've seen a similar failure, on a domain-joined Windows 10 box running
> > > cygsshd using a local cyg_server user account. I've fixed it by:
> > > 1) Open the "Computer Management" app
> > >    Select "Services and Applications", then "Services", and
> > >    choose the cygsshd service from the list.
> > > 2) Stop the service
> > > 3) Select the "Log On" tab, choose "Local System Account" and click O=
K.
> > > 4) Restart the service.
> > >=20
> > > This changed the account reported by "cygrunsrv -VQ" from "./cyg_serv=
er"
> > > to "LocalSystem".
> >=20
> > 64-@@ uname -a
> > CYGWIN_NT-6.1 Seven 3.0.1(0.338/5/3) 2019-02-20 10:19 x86_64 Cygwin
> >=20
> > First I replaced cygwin1.dll again w/ the last version, as you can see =
...
> >=20
> > Then I carried out you instruction ...
> >=20
> > To my surprise it did the trick! Thank you!
> >=20
> > Perhaps Corinna can give a hint of why the modification made the differ=
ence.
>=20
> Actually, I can't.  I'm surprised, too, because it still runs
> fine for me under the cyg_server account.

Actually, maybe I can.  On second thought there's a quite high
probability that my AD cyg_server account I'm using for 10 years
or longer, has not the same privileges as a cyg_server account
created via ssh-host-config script.  May it works for me because
of these extra permissions the account got during years of playing
around with it.

I guess I have to crate another, local cyg_server account via
ssh-host-config and try the same with that account.

Not having much time tomorrow, but at least on Friday I should
be able to test this.


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--Ht+/lPZLak6eP81R
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxt2BwACgkQ9TYGna5E
T6C2zQ//ZcZVJbYMeHZq3qljXt7gyQcCqJlO/XajDxPKa1oQ02Rc1ea28XS2KcBF
z8op44IwK2DaYl7hembZpLW2dgKL1RjnzhOvWq4L6mTFWx7Yb1lcKLXTako5vCKA
mlA5pyqbwuiwhWEDIzbCjkKr/dN6N849EkYCteNzP8LkVtfqhnXYD49rr2Gei/p3
eij7FtOJ5ls9dtw0KZCzdoI+vYpnODQkYm0avSoKAfS+pYMTn/o/XBt4UDVrOvKu
vFi3ZBV0VmaSbRN98U053rIn8nbVGSQI9MpcgWUgsVLQj2uptbieYWbwFpdi9Qyp
RP6MfJWyuot5y5lDp+G0RlgRgFZYh4I2OY6K3sr+nyRw+tnD00bVBBH6NTw8U3hN
Z2jr+3/vf3cFxz+FAJvVfwmKyjapvyfEJOLVavqTvgErpqEE8bFR0T/Zrd+wLbuY
kjoN3Rdc6uBSwv2AbmtT1nJTIDgTXIm7GVYxOLBFrTjbeo1KSCVn1L1luinofv6C
iX4zdfYx78fj60/UKd1QfwD+GdfXjs3IA0Iq+e91JRDNQdHgsh5X1nJolehwt41k
/3BiidydRt9IOLvs2SpZtpmdtkU+UATgEz7+oUSO1ZjiDSYYdi6Pgtj777OgUtPk
1bWIVnrQRSS4c5fld847PXKrSyvZo8LLa2ahu1o/V9S6YtG0vOM=
=frYp
-----END PGP SIGNATURE-----

--Ht+/lPZLak6eP81R--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019