Upd: the trick with pre-logging in by other means does not work:
$ /usr/bin/editrights -u git -l
SeBatchLogonRight
I've created the wake-s4u scheduled job following the instructions from the ml
thread: "sshd problem on WS2008R2 64bit"
cmd.exe is running as that user, but seteuid still fails.
Changing the sshd service to run as localsystem rather than cyg_server
allows me to again ssh into the machine.
Thanks for everyone on this mailing list - I spent hours trying to figure
this out - and because the list doesn't seem to get indexed by google, the
web searches I was doing were of no
I’m seeing a similar issue. Will try using localsystem.
> On Feb 21, 2019, at 6:43 AM, Houder wrote:
>
>> On Thu, 21 Feb 2019 11:09:11, Corinna Vinschen wrote:
>>
>> I managed it today already but I'm somewhat stumped.
>>
>> I ran ssh-host-config and let the script install a new local
On Thu, 21 Feb 2019 11:09:11, Corinna Vinschen wrote:
> I managed it today already but I'm somewhat stumped.
>
> I ran ssh-host-config and let the script install a new local account
> "test_server" to use for the sshd service. I started the service and
> tried to login with a local account and
On Feb 20 23:43, Corinna Vinschen wrote:
> 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:
> > >
> > > > I've seen a similar failure, on a domain-joined Windows 10 box running
> > > > cygsshd using a local
On Wed, 20 Feb 2019 23:38:17, Corinna Vinschen wrote:
> On Feb 20 23:25, Houder wrote:
> > As a final step I rebooted my system (W7, 64 bits, Uising 64-bits Cygwin).
> >
> > I can still connect to the localhost w/ ssh ...
> >
> > But I cannot start and stop the "sshd service" using cygrunsrv.
>
On Feb 20 14:31, scow...@ckhb.org wrote:
>
> On Wed, 20 Feb 2019, Houder wrote:
> > On Wed, 20 Feb 2019 22:41:08, Corinna Vinschen wrote:
> >
> > > On Feb 20 22:35, Houder wrote:
> > [snip]
> >
> > > >
> > > > Perhaps I missed something in the last couple of month. Did I have
> > > > to
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:
> >
> > > 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
On Feb 20 23:25, Houder wrote:
> On Wed, 20 Feb 2019 23:01:01, Houder wrote:
> > On Wed, 20 Feb 2019 22:41:08, Corinna Vinschen wrote:
> >
> > > On Feb 20 22:35, Houder wrote:
> > [snip]
> >
> > > >
> > > > Perhaps I missed something in the last couple of month. Did I have
> > > > to change
>
On Feb 20 22:49, Houder wrote:
> On Wed, 20 Feb 2019 21:27:22, Andy Moreton wrote:
>
> > 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
On Wed, 20 Feb 2019, Houder wrote:
On Wed, 20 Feb 2019 22:41:08, Corinna Vinschen wrote:
On Feb 20 22:35, Houder wrote:
[snip]
Perhaps I missed something in the last couple of month. Did I have
to change
something in the setup of openssh?
I really don't know, this all works fine for
On Wed, 20 Feb 2019 23:01:01, Houder wrote:
> On Wed, 20 Feb 2019 22:41:08, Corinna Vinschen wrote:
>
> > On Feb 20 22:35, Houder wrote:
> [snip]
>
> > >
> > > Perhaps I missed something in the last couple of month. Did I have
> > > to change
> > > something in the setup of openssh?
> >
> > I
On Wed, 20 Feb 2019, Corinna Vinschen wrote:
On Feb 20 21:27, Andy Moreton wrote:
On Wed 20 Feb 2019, Corinna Vinschen wrote:
On Feb 20 21:01, Houder wrote:
On Wed, 20 Feb 2019 10:53:09, scowles at ckhb dot org wrote:
i can confirm the same behaviours on a 3.0.0 system. i've done
On Wed, 20 Feb 2019 22:41:08, Corinna Vinschen wrote:
> On Feb 20 22:35, Houder wrote:
[snip]
> >
> > Perhaps I missed something in the last couple of month. Did I have
> > to change
> > something in the setup of openssh?
>
> I really don't know, this all works fine for me. Try switching the
On Wed, 20 Feb 2019 21:27:22, Andy Moreton wrote:
> 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
>
On Feb 20 22:35, Houder wrote:
> On Wed, 20 Feb 2019 21:25:36, Corinna Vinschen wrote:
>
> > Sorry guys, but I can't reproduce this problem at all. I tested ssh
> > login on Vista, W7 and W10 1809, in each case on 64 bit and under
> > WOW64. On all systems I can login with domain as well as
On Feb 20 21:27, Andy Moreton wrote:
> On Wed 20 Feb 2019, Corinna Vinschen wrote:
>
> > On Feb 20 21:01, Houder wrote:
> >> On Wed, 20 Feb 2019 10:53:09, scowles at ckhb dot org wrote:
> >> >
> >> > i can confirm the same behaviours on a 3.0.0 system. i've done
> >> > several checks and have
On Wed, Feb 20, 2019 at 1:25 PM Corinna Vinschen wrote:
> Sorry guys, but I can't reproduce this problem at all. I tested ssh
> login on Vista, W7 and W10 1809, in each case on 64 bit and under
> WOW64. On all systems I can login with domain as well as local
> accounts.
>
> For completeness
On Wed, 20 Feb 2019 21:25:36, Corinna Vinschen wrote:
> Sorry guys, but I can't reproduce this problem at all. I tested ssh
> login on Vista, W7 and W10 1809, in each case on 64 bit and under
> WOW64. On all systems I can login with domain as well as local
> accounts.
Understood.
> For
On Wed 20 Feb 2019, Corinna Vinschen wrote:
> On Feb 20 21:01, Houder wrote:
>> On Wed, 20 Feb 2019 10:53:09, scowles at ckhb dot org wrote:
>> >
>> > i can confirm the same behaviours on a 3.0.0 system. i've done several
>> > checks
>> > and have been unable to find the source of the
On Feb 20 21:01, Houder wrote:
> On Wed, 20 Feb 2019 10:53:09, scowles at ckhb dot org wrote:
> >
> > i can confirm the same behaviours on a 3.0.0 system. i've done several
> > checks
> > and have been unable to find the source of the problem. ssh -vvv shows
> > that the
> > connection
On Wed, 20 Feb 2019 10:53:09, scowles at ckhb dot org wrote:
>
> i can confirm the same behaviours on a 3.0.0 system. i've done several
> checks
> and have been unable to find the source of the problem. ssh -vvv shows that
> the
> connection proceeds all the way through the connection
0 8661
Key fingerprint = A156 277B 875A D6E3 A00C 23D9 869E 72BE 1FD3 5B80
On Wed, 20 Feb 2019, Bill Stewart wrote:
Date: Wed, 20 Feb 2019 11:04:29
From: Bill Stewart
To: cygwin@cygwin.com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
In Cygwin 3.x, the case of the username must match exactly
On Wed, Feb 20, 2019 at 11:53 AM scowles wrote:
> i can confirm the same behaviours on a 3.0.0 system. i've done several checks
> and have been unable to find the source of the problem. ssh -vvv shows that
> the
> connection proceeds all the way through the connection process, sends the
>
D6E3 A00C 23D9 869E 72BE 1FD3 5B80
On Wed, 20 Feb 2019, James R. Phillips via cygwin wrote:
Date: Wed, 20 Feb 2019 10:16:44
From: James R. Phillips via cygwin
Reply-To: James R. Phillips
To: "cygwin@cygwin.com"
Subject: cygwin 3.0.1-1 breaks my sshd install
Hello,
My sshd ins
Hello,
My sshd install stops working when upgrading from cygwin 2.11.2-1 to 3.0.1-1.
After upgrading and restarting sshd, an attempted connection is always closed,
even coming from localhost.
I have verified that I can get a server response with "$ telnet localhost 22",
so I'm quite sure this
26 matches
Mail list logo
