Rael
Sent: 14 February 2022 13:12
To: cygwin@cygwin.com
Subject: Re: sshd
[CAUTION: EXTERNAL SENDER]
On 2/13/22 10:56 PM, Andrey Repin wrote:
> Greetings, Ernie Rael!
>
> ...
> Open Windows Firewall (cygstart WF.msc), find all your sshd rules and
> trash them. Manually create (o
On 2/13/22 10:56 PM, Andrey Repin wrote:
Greetings, Ernie Rael!
...
Open Windows Firewall (cygstart WF.msc), find all your sshd rules and trash
them. Manually create (or tweak Windows sshd one) a single rule for port
rather than executable.
Additionally, to resolve conflicts with stock sshd,
Greetings, Ernie Rael!
> On 2/12/22 9:29 PM, Mark Geisert wrote:
>> Ernie Rael wrote:
>>> Hi all,
>>>
>>> I set up cygwin several years ago and have only had one system at
>>> home. I've recently got a 2nd, linux.
>>>
>>> I've used ssh locally under cygwin, primarily to get a term for a use
>>>
On Sun, Feb 13, 2022 at 7:38 AM Ernie Rael wrote:
> Doesn't seem to be a firewall issue. NetStat took about 90 seconds.
>
> $ ps -lp 255
>PIDPPIDPGID WINPID TTY UIDSTIME COMMAND
>255 254 255 4176 ? 1006 Feb 1
> /usr/sbin/sshd
>
Thanks Russell,
cygrunsrv's running
$ cygrunsrv --list
sshd
$ cygrunsrv --query sshd
Service : sshd
Display name : CYGWIN sshd
Current State : Running
Controls Accepted : Stop
Command : /usr/sbin/sshd -D
-ernie
On 2/12/22 10:30 PM, Russell VT wrote:
On 2/12/22 9:29 PM, Mark Geisert wrote:
Ernie Rael wrote:
Hi all,
I set up cygwin several years ago and have only had one system at
home. I've recently got a 2nd, linux.
I've used ssh locally under cygwin, primarily to get a term for a use
with admin priv. And I can ssh from cygwin to the
Note that port 5972 isn't *really* what you want, as that's arbitrary...
but port 22.
Check the Windows firewall, as was already suggested (highly suspect, if
you just timeout when trying to connect).
If you try rebuilding what you did under Windows, you're likely going to
want to look at
Ernie Rael wrote:
Hi all,
I set up cygwin several years ago and have only had one system at home. I've
recently got a 2nd, linux.
I've used ssh locally under cygwin, primarily to get a term for a use with admin
priv. And I can ssh from cygwin to the linux machine. On cygwin I see
$ ps
On Aug 6 16:16, ASSI wrote:
> Corinna Vinschen via Cygwin writes:
> >> I found the solution by myself. Installing libcbor-devel package
> >> fixes this error.
> >
> > I just uploaded libfido2-1.5.0-2, which just adds a dependency from
> > libfido2-devel to libcbor-devel.
>
> It would have
Corinna Vinschen via Cygwin writes:
>> I found the solution by myself. Installing libcbor-devel package
>> fixes this error.
>
> I just uploaded libfido2-1.5.0-2, which just adds a dependency from
> libfido2-devel to libcbor-devel.
It would have sufficed to just upload a new hint file…
:-)
On Aug 6 20:14, Takashi Yano via Cygwin wrote:
> On Fri, 6 Aug 2021 11:11:05 +0200
> Corinna Vinschen wrote:
> > On Aug 6 10:55, Takashi Yano via Cygwin wrote:
> > > Hi Corinna,
> > >
> > > On Fri, 6 Aug 2021 01:43:31 +0900
> > > Takashi Yano wrote:
> > > > Hi Corinna,
> > > >
> > > > On Thu,
On Aug 6 21:35, Takashi Yano via Cygwin wrote:
> On Fri, 6 Aug 2021 20:30:58 +0900
> Takashi Yano wrote:
> > On Fri, 6 Aug 2021 01:43:31 +0900
> > Takashi Yano wrote:
> > > In order to look into this problem, I tried to build openssh-8.5p1-1
> > > from source, however it cause the error in
On Fri, 6 Aug 2021 20:30:58 +0900
Takashi Yano wrote:
> On Fri, 6 Aug 2021 01:43:31 +0900
> Takashi Yano wrote:
> > In order to look into this problem, I tried to build openssh-8.5p1-1
> > from source, however it cause the error in configure stage:
> >
> > ...
> > checking for pkg-config...
On Fri, 6 Aug 2021 01:43:31 +0900
Takashi Yano wrote:
> In order to look into this problem, I tried to build openssh-8.5p1-1
> from source, however it cause the error in configure stage:
>
> ...
> checking for pkg-config... (cached) /usr/bin/pkg-config
> checking if /usr/bin/pkg-config knows
On Fri, 6 Aug 2021 11:11:05 +0200
Corinna Vinschen wrote:
> On Aug 6 10:55, Takashi Yano via Cygwin wrote:
> > Hi Corinna,
> >
> > On Fri, 6 Aug 2021 01:43:31 +0900
> > Takashi Yano wrote:
> > > Hi Corinna,
> > >
> > > On Thu, 5 Aug 2021 17:07:24 +0200
> > > Corinna Vinschen wrote:
> > > >
On Aug 6 10:55, Takashi Yano via Cygwin wrote:
> Hi Corinna,
>
> On Fri, 6 Aug 2021 01:43:31 +0900
> Takashi Yano wrote:
> > Hi Corinna,
> >
> > On Thu, 5 Aug 2021 17:07:24 +0200
> > Corinna Vinschen wrote:
> > > Could you perhaps bisect the issue on your machine?
> >
> > In my environment,
Hi Corinna,
On Fri, 6 Aug 2021 01:43:31 +0900
Takashi Yano wrote:
> Hi Corinna,
>
> On Thu, 5 Aug 2021 17:07:24 +0200
> Corinna Vinschen wrote:
> > Could you perhaps bisect the issue on your machine?
>
> In my environment, this does not happen with 8.4p1-1 and 8.4p1-2.
> However it happens with
Hi Corinna,
On Thu, 5 Aug 2021 17:07:24 +0200
Corinna Vinschen wrote:
> Could you perhaps bisect the issue on your machine?
In my environment, this does not happen with 8.4p1-1 and 8.4p1-2.
However it happens with 8.5p1-1.
> The fact that using Windows ssh is an issue makes me wonder if this is
On Aug 5 19:12, Takashi Yano via Cygwin wrote:
> Hi everyone,
>
> On Wed, 28 Apr 2021 07:23:02 +0300
> Andrey Repin wrote:
>
> > Greetings, Christoph Lüders!
> >
> > > I run cygwin 32-bit on Windows 10 Pro Build 19042. Cygwin is 3.2.0-1,
> > > openssh is 8.5p1-1.
> >
> > > I use sshd to
Hi everyone,
On Wed, 28 Apr 2021 07:23:02 +0300
Andrey Repin wrote:
> Greetings, Christoph Lüders!
>
> > I run cygwin 32-bit on Windows 10 Pro Build 19042. Cygwin is 3.2.0-1,
> > openssh is 8.5p1-1.
>
> > I use sshd to access the machine from afar. I notice (often multiple)
> > processes of
On 5/28/2021 7:06 PM, A. Doggy wrote:
On 5/27/2021 7:51 AM, A. Doggy wrote:
On 5/25/2021 8:23 PM, A. Doggy wrote:
On 5/20/2021 9:31 PM, A. Doggy wrote:
To cygwin.
A Little more info: I actually have 1 client that connects
regularly to the server. That client uses a program called
On 5/27/2021 7:51 AM, A. Doggy wrote:
On 5/25/2021 8:23 PM, A. Doggy wrote:
On 5/20/2021 9:31 PM, A. Doggy wrote:
To cygwin.
A Little more info: I actually have 1 client that connects regularly
to the server. That client uses a program called goodsync. When I
block goodsync from
On 5/25/2021 8:23 PM, A. Doggy wrote:
On 5/20/2021 9:31 PM, A. Doggy wrote:
To cygwin.
A Little more info: I actually have 1 client that connects regularly
to the server. That client uses a program called goodsync. When I
block goodsync from connecting, the problem goes away and I only
On 5/20/2021 9:31 PM, A. Doggy wrote:
To cygwin.
A Little more info: I actually have 1 client that connects regularly
to the server. That client uses a program called goodsync. When I
block goodsync from connecting, the problem goes away and I only have
1 sshd.exe process running. When I
Greetings, A. Doggy!
Bottom post please.
> On 5/20/2021 12:02 PM, A. Doggy wrote:
>> Anyone?
>>
>> On 5/19/2021 12:48 AM, A. Doggy wrote:
>>> To Cygwin,
>>>
>>>
>>> I am running cygwin openssh as a windows service. I have been doing
>>> so for many years with out issue. Recently, I have been
On 5/20/21 4:35 PM, Andrey Repin wrote:
> CAUTION: This email originated from outside of Leidos. Be cautious when
> clicking or opening content.
>
> Greetings, Wells, Roger K.!
>
>>> On 5/19/2021 12:48 AM, A. Doggy wrote:
I am running cygwin openssh as a windows service. I have been
To cygwin.
A Little more info: I actually have 1 client that connects regularly to
the server. That client uses a program called goodsync. When I block
goodsync from connecting, the problem goes away and I only have 1
sshd.exe process running. When I unblock goodsync, I have multiple
> -Original Message-
> From: Andrey Repin
> Sent: Thursday, May 20, 2021 4:33 PM
> To: Wells, Roger K. ; cygwin@cygwin.com
> Cc: Andrey Repin
> Subject: [cygwin] Re: EXTERNAL: Re: sshd high cpu load
>
> Greetings, Wells, Roger K.!
>
> >> O
Greetings, Wells, Roger K.!
>> On 5/19/2021 12:48 AM, A. Doggy wrote:
>>>
>>>
>>> I am running cygwin openssh as a windows service. I have been doing
>>> so for many years with out issue. Recently, I have been running into
>>> an issue where it maxes out my cpu on any version newer than 8.4p1-1.
On 5/20/21 12:02 PM, A. Doggy via Cygwin wrote:
> Anyone?
Sorry,
I noticed your initial contact and tried to duplicate what you observed
to no avail.
I set up cygwin openssh as a windows service as you described and also
have been doing it this way for many years.
sshd.exe doesn't show any cpu
> -Original Message-
> From: A. Doggy via Cygwin
> Sent: Thursday, May 20, 2021 12:03 PM
>
> Anyone?
Psst, put at bottom.
>
> On 5/19/2021 12:48 AM, A. Doggy wrote:
> > To Cygwin,
> >
> >
> > I am running cygwin openssh as a windows service. I have been doing so
> > for many years with
Anyone?
On 5/19/2021 12:48 AM, A. Doggy wrote:
To Cygwin,
I am running cygwin openssh as a windows service. I have been doing so
for many years with out issue. Recently, I have been running into an
issue where it maxes out my cpu on any version newer than 8.4p1-1. The
solution is to
On 2021-05-04 09:14, Andrey Repin via Cygwin wrote:
Wednesday, April 28, 2021, 06:23:02, "Andrey Repin" wrote:
I run cygwin 32-bit on Windows 10 Pro Build 19042. Cygwin is 3.2.0-1,
openssh is 8.5p1-1.
I use sshd to access the machine from afar. I notice (often multiple)
processes of
Greetings, Christoph Lüders!
This list is in "no top posting, please" mode.
> Wednesday, April 28, 2021, 06:23:02, "Andrey Repin" wrote:
>> Greetings, Christoph Lüders!
>>> I run cygwin 32-bit on Windows 10 Pro Build 19042. Cygwin is 3.2.0-1,
>>> openssh is 8.5p1-1.
>>> I use sshd to access
On 2021-05-03 07:40, Jason Pyeron wrote:
My teammates have been observing periodic slow login problems recently, most
recent Cygwin update was for the Git CVE, but I do not think that is related.
Guidance on troubleshooting and resolution most appreciated.
My assumptions:
BLODA (I cannot
Greetings, Christoph Lüders!
> I run cygwin 32-bit on Windows 10 Pro Build 19042. Cygwin is 3.2.0-1,
> openssh is 8.5p1-1.
> I use sshd to access the machine from afar. I notice (often multiple)
> processes of sshd.exe with 100% CPU load.
Greetings, iw875...@gmx.eu!
> sshd seems to run at 100% Load for one thread after ssh disconnect
125% or more, actually.
> (Close Terminal Window) on my Windows 10 computer.
> If I use exit it isn't so.
> I have to kill sshd or reboot the machine to kill the load.
Kill the shell (or another
On Thu, Dec 17, 2020 at 6:12 PM Bill Stewart wrote:
>
> On Thu, Dec 17, 2020 at 2:25 PM Erik Soderquist wrote:
>
> > I've had weird instances where the Windows Firewall tools lied; I
> > confirmed this by temporarily shutting down the Windows Firewall
> > entirely, then restarting the service
On Thu, Dec 17, 2020 at 2:25 PM Erik Soderquist wrote:
> I've had weird instances where the Windows Firewall tools lied; I
> confirmed this by temporarily shutting down the Windows Firewall
> entirely, then restarting the service having problems and retesting.
> On retest, it worked fine,
On Thu, Dec 17, 2020 at 3:51 PM Charles Russell wrote:
>
> On 12/17/2020 11:49 AM, Bill Stewart wrote:
>
> > Make sure to look carefully through all of the firewall rules and
> > check whether there is a rule blocking that executable or port.
> >
>
> Selecting "Advanced Settings" and then
On Thu, Dec 17, 2020 at 1:51 PM Charles Russell wrote:
> Selecting "Advanced Settings" and then "incoming rules", I see one rule
> for sshd private: enabled, allowed and one rule for sshd public:
> enabled, allowed. There is a third rule for sshd domain: (disabled,
> allowed). I believe that one
On 2020-12-17 13:51, Charles Russell wrote:
On 12/17/2020 11:49 AM, Bill Stewart wrote:
Make sure to look carefully through all of the firewall rules and
check whether there is a rule blocking that executable or port.
Selecting "Advanced Settings" and then "incoming rules", I see one rule for
On 12/17/2020 11:49 AM, Bill Stewart wrote:
> Make sure to look carefully through all of the firewall rules and
> check whether there is a rule blocking that executable or port.
>
Selecting "Advanced Settings" and then "incoming rules", I see one rule
for sshd private: enabled, allowed and one
On Thursday, April 16, 2020, 04:50:03 AM EDT, Andrey Repin
wrote:
>> sshd: PID 1721: fatal: seteuid 1610619958: No such device or address
>> I just did a clean install:
>> openssh 8.2p1-1
>> The uid corresponds to me:
>> uid=1610619958(+kevins)
> Can
Greetings, Kevin Schnitzius!
> sshd: PID 1721: fatal: seteuid 1610619958: No such device or address
> I just did a clean install:
> openssh 8.2p1-1
> The uid corresponds to me:
> uid=1610619958(+kevins)
Can we see the full output of `id` when you logged
On Tue, Apr 14, 2020 at 8:01 PM Kevin Schnitzius wrote:
> sshd: PID 1721: fatal: seteuid 1610619958: No such device or address
>
> I just did a clean install:
> openssh 8.2p1-1
>
> The uid corresponds to me:
> uid=1610619958(+kevins)
>
> Local users work
Thank you for the assistance!
I released the latest version of my installer, now available (under
"Releases" tab) here:
https://github.com/Bill-Stewart/Cygwin-OpenSSH
Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On Thu, 30 Jan 2020 12:33:28 -0700
Bill Stewart wrote:
> On Thu, Jan 30, 2020 at 9:46 AM Takashi Yano wrote:
> > I believe you do not need winpty anymore because newer cygwin
> > utilizes pseudo console in pty.
>
> Since this package is still used for older OS versions, I will still
> need winpty
On Thu, Jan 30, 2020 at 12:33 PM Bill Stewart wrote:
> I added cygwin-console-helper.exe and this resolved it, at least on
> Windows 10. My next step is to test on Server 2012 R2.
Tested, and works fine also on Server 2012 R2. Thanks for the help!
Bill
--
Problem reports:
On Thu, Jan 30, 2020 at 9:46 AM Takashi Yano wrote:
> Bill Stewart wrote:
> >
> > When I use cygwin1.dll versions newer than 3.0.7, sshd.exe hangs
> > whenever establishing a connection.
> > ...
> > Any ideas?
>
> You need cygwin-console-helper.exe for newer cygwin pty which
> supports pseudo
On Thu, 30 Jan 2020 09:27:34 -0700
Bill Stewart wrote:
> I have created an OpenSSH installer for Windows users:
>
> https://github.com/Bill-Stewart/Cygwin-OpenSSH
>
> Basically it includes only the minimum files from Cygwin needed to run
> OpenSSH and has some additional conveniences (the
so i ran into the same problem and had some difficulty in figuring out how to
apply the solution. so hopefully to save other people from the same issue.
to set the sshd service to use the SYSTEM you open the properties sheet for
sshd service, go to the "Log On" tab and then click the radio button
On Sun, May 12, 2019 at 8:31 AM L A Walsh wrote:
> This has been a feature of Windows since win98. Not officially, mind
> you, but any scheduled task in windows would eventually become
> unscheduled and stop running with out any notification.
I've never seen this behavior on any Windows machine
On 5/12/2019 6:35 AM, Enrico.Bertram wrote:
> \
>
> The service is configured to start automatically and does so on each reboot.
> The event viewer does not show any event (for example the "stopped" on
> normal shutdowns) - the service is just in shut down state every now and
> then and I have to
On Fri, Mar 29, 2019 at 4:00 AM Corinna Vinschen wrote:
> > On 2019-03-28 15:36, Bill Stewart wrote:
> > I am trying to understand the limitations when running sshd using the
> > SYSTEM account.
> >
> > Is the following complete and correct?
> >
> > ==
> >
> > OS_version* OS_bitness
On Mar 28 17:18, Brian Inglis wrote:
> On 2019-03-28 15:36, Bill Stewart wrote:
> > I am trying to understand the limitations when running sshd using the
> > SYSTEM account.
> > Is the following complete and correct?
> > ==
> > OS_version* OS_bitness sshd_bitness Notes
> >
On 2019-03-28 15:36, Bill Stewart wrote:
> I am trying to understand the limitations when running sshd using the
> SYSTEM account.
> Is the following complete and correct?
> ==
> OS_version* OS_bitness sshd_bitness Notes
> --
> < 6.3
On Fri, 15 Mar 2019 21:41:22, Corinna Vinschen wrote:
> On Mar 15 20:39, Houder wrote:
> > On Fri, 15 Mar 2019 14:42:47, Corinna Vinschen wrote:
[snip]
> > > Well, there *is* a solution by using strace. And hey, we now know what
> > > ENXIO returned from seteuid means, don't we? It's not
On Mar 15 20:39, Houder wrote:
> On Fri, 15 Mar 2019 14:42:47, Corinna Vinschen wrote:
>
> > On Mar 15 14:06, Houder wrote:
>
> > > One is forced to create the exact same environment (system) as the
> > > person who is complaining, fire up the debugger (like sticking
> > > a thermometer in a
On Fri, 15 Mar 2019 14:42:47, Corinna Vinschen wrote:
> On Mar 15 14:06, Houder wrote:
> > One is forced to create the exact same environment (system) as the
> > person who is complaining, fire up the debugger (like sticking
> > a thermometer in a patient's rear end) in order to find out where
On Mar 15 14:06, Houder wrote:
> On Thu, 14 Mar 2019 18:29:18, Corinna Vinschen wrote:
>
> > On Mar 14 16:53, Houder wrote:
>
> > > On Thu, 14 Mar 2019 12:39:30, X wrote:
> > > > Hello the list
> [snip]
> > > > sshd: PID 3777: fatal: seteuid 1049076: No such device or address
>
> > >
On Thu, 14 Mar 2019 18:29:18, Corinna Vinschen wrote:
> On Mar 14 16:53, Houder wrote:
> > On Thu, 14 Mar 2019 12:39:30, X wrote:
> > > Hello the list
[snip]
> > > sshd: PID 3777: fatal: seteuid 1049076: No such device or address
> > Corinna,
> >
> > As far as I know, seteuid() can either
On Mar 14 16:53, Houder wrote:
> On Thu, 14 Mar 2019 12:39:30, X wrote:
> > Hello the list,
> >
> > Thanks for all the work and effort put into this.
> > Since two days i cannot login anymore (password less) with ssh into my
> > server
> >
> > Server is :
> > Microsoft Windows Server 2012
On Thu, 14 Mar 2019 12:39:30, X wrote:
> Hello the list,
>
> Thanks for all the work and effort put into this.
> Since two days i cannot login anymore (password less) with ssh into my
> server
>
> Server is :
> Microsoft Windows Server 2012 R2 Essentials / 6.3.9600 N/A version 9600
>
>
> As for why, Administrator is the only local account with super-user
> permissions that is guaranteed to exist. Windows uses it in case something
> gone REALLY wrong, such as AD database recovery procedures.
>
> It is easy enough to enable a locked account with offline tools, if your
system
>
Greetings, renaud.rol...@giraudbtp.com!
>> Please remove /etc/passwd and /etc/group files. They are no longer
>> necessary, unless you have some very special needs, and even then, they
>> only needed for that one or two accounts you need special treatment for.
> They dont exists.
Then my next
Greetings, David Dombrowsky!
> On 3/14/19 10:11 AM, Andrey Repin wrote:
>> Please remove /etc/passwd and /etc/group files. They are no longer necessary,
>> unless you have some very special needs, and even then, they only needed for
>> that one or two accounts you need special treatment for.
>>
> Please remove /etc/passwd and /etc/group files. They are no longer
> necessary, unless you have some very special needs, and even then, they
> only needed for that one or two accounts you need special treatment for.
They dont exists.
> The main security concern is, why your Administrator user:
On Mar 14 10:24, David Dombrowsky wrote:
> On 3/14/19 10:11 AM, Andrey Repin wrote:
> > Please remove /etc/passwd and /etc/group files. They are no longer
> > necessary,
> > unless you have some very special needs, and even then, they only needed for
> > that one or two accounts you need special
On 3/14/19 10:11 AM, Andrey Repin wrote:
> Please remove /etc/passwd and /etc/group files. They are no longer necessary,
> unless you have some very special needs, and even then, they only needed for
> that one or two accounts you need special treatment for.
>
Wait what? What about all the
Greetings, renaud.rol...@giraudbtp.com!
>> > I can login via password, it work and lets me in.
>> > But if i tried with my keys, I get in the event viewer :
>> > sshd: PID 3777: fatal: seteuid 1049076: No such device or address
>>
>> - Make sure to login with the Administrator account
> Objet : Re: sshd: fatal: seteuid XXX : No such device or address
>
> On Mar 14 14:26, renaud.rol...@giraudbtp.com wrote:
> > >
> > > On Mar 14 12:39, renaud.rol...@giraudbtp.com wrote:
> > > > I can login via password, it work and lets me in.
>
On Mar 14 14:26, renaud.rol...@giraudbtp.com wrote:
> >
> > On Mar 14 12:39, renaud.rol...@giraudbtp.com wrote:
> > > I can login via password, it work and lets me in.
> > > But if i tried with my keys, I get in the event viewer :
> > > sshd: PID 3777: fatal: seteuid 1049076: No such device or
>
> On Mar 14 12:39, renaud.rol...@giraudbtp.com wrote:
> > I can login via password, it work and lets me in.
> > But if i tried with my keys, I get in the event viewer :
> > sshd: PID 3777: fatal: seteuid 1049076: No such device or address
>
> - Make sure to login with the Administrator account
On Mar 14 12:39, renaud.rol...@giraudbtp.com wrote:
> Hello the list,
>
> Thanks for all the work and effort put into this.
> Since two days i cannot login anymore (password less) with ssh into my
> server
>
> Server is :
> Microsoft Windows Server 2012 R2 Essentials / 6.3.9600 N/A version
David Dombrowsky writes:
> If I'm reading this correctly, using the SYSTEM account will deny access
> to user-level shares. Using the cyg_server account (or another service
> account) will allow access, but requires a password stored in the
> registry.
That was already the case if you logged in
On Wed, Mar 13, 2019 at 9:29 AM Corinna Vinschen wrote:
> > However: It's still the case that the user cannot bypass OS security
even
> > if he or she "escapes" from the jail, right?
> >
> > My goal is to restrict sftp browsing on the client side.
> >
> > Using ChrootDirectory with "ForceCommand
On Mar 13 09:11, Bill Stewart wrote:
> On Wed, Mar 13, 2019 at 2:57 AM Corinna Vinschen wrote:
>
> > > a) Why is it necessary to specify SYSTEM as user number 0 in the
> > > /etc/password file?
> > >
> > > b) Why is the sshd account required?
> >
> > sshd checks for uid 0 and requires the sshd
On Wed, Mar 13, 2019 at 2:57 AM Corinna Vinschen wrote:
> > a) Why is it necessary to specify SYSTEM as user number 0 in the
> > /etc/password file?
> >
> > b) Why is the sshd account required?
>
> sshd checks for uid 0 and requires the sshd account when chroot is
> requested.
>
> > c) Why are
On Mar 12 16:21, Bill Stewart wrote:
> On Thu, 17 Jan 2019 Corinna Vinschen wrote:
>
> > > Is the sshd disabled user account still required?
> >
> > No, actually it isn't. These days the sshd server checks if the
> > the privsep chrrot environment should be used and that the process
> > is
On Tue, Mar 12, 2019 at 8:02 PM David Dombrowsky wrote:
> > Surely you don't mean they have a plain-text copy of your password?
>
> If only I were kidding. Security through Oblivity :)
(?!) There is no reason that anyone else should have your password.
This means (among other things) that
On 3/12/19 8:54 PM, Bill Stewart wrote:
> On Tue, Mar 12, 2019 at 6:19 PM David Dombrowsky wrote:
>
>> For me, this is acceptable risk since this is a single user machine and
>> the administrators of the domain already know my domain password :)
>
> I hope you really mean that they can _reset_
On Tue, Mar 12, 2019 at 6:19 PM David Dombrowsky wrote:
> For me, this is acceptable risk since this is a single user machine and
> the administrators of the domain already know my domain password :)
I hope you really mean that they can _reset_ your domain password if needed?
Surely you don't
On 3/12/19 5:30 PM, Corinna Vinschen wrote:
>> Was that the correct solution? Is that expected? This windows box is
>> on a domain, so that might have something to do with it.
>
> Just switch the account sshd is running under from "cyg_server" to
> SYSTEM (or "LocalSystem") and you should be
On Thu, 17 Jan 2019 Corinna Vinschen wrote:
> > Is the sshd disabled user account still required?
>
> No, actually it isn't. These days the sshd server checks if the
> the privsep chrrot environment should be used and that the process
> is started under "root:root". This never matches under
On Mar 12 17:09, David Dombrowsky wrote:
> I managed to solve this problem, but I'd love some confirmation that I
> solved it the right way.
>
> After updating cygwin and rebooting, all of a sudden I couldn't ssh
> into my windows box. The remote gave the usual "connection closed by
> port 22"
On 2019-03-07 01:53, Corinna Vinschen wrote:
> On Mar 6 23:15, Brian Inglis wrote:
>> On 2019-03-06 13:59, Corinna Vinschen wrote:
>>> I'm reasonably sure there won't be any fix for these systems for at
>>> least two reasons:
>>> - All affected systems are EOLed or in the last year of their
On Mar 6 23:15, Brian Inglis wrote:
> On 2019-03-06 13:59, Corinna Vinschen wrote:
> > I'm reasonably sure there won't be any fix for these systems for at
> > least two reasons:
> > - All affected systems are EOLed or in the last year of their Extended
> > Support Cycle, all ending on
On 2019-03-06 13:59, Corinna Vinschen wrote:
> I'm reasonably sure there won't be any fix for these systems for at
> least two reasons:
> - All affected systems are EOLed or in the last year of their Extended
> Support Cycle, all ending on 2020-01-14.
> - I opened a support case for an older
On Wed, Mar 06, 2019 at 03:44:36PM -0800, Stephen Paul Carrier wrote:
> PW=`dd if=/dev/random bs=15 count=1 | base 64`
That should be 'base64' of course, without the space.
--S
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On Wed, Mar 06, 2019 at 02:24:59PM -0700, Bill Stewart wrote:
...
> For my part, I'm writing a PowerShell script that does the following:
>
> 1) Create a local user account
> 2) Grant it SeBatchLogonRight
> 3) Create a scheduled task for it
Powershell is probably more elegant if you're
On Wed, Mar 6, 2019 at 2:00 PM Corinna Vinschen wrote:
> > Whether this workaround is feasible likely depends on the end user. The
> > workaround has its own limitations. Here are at least 2 that I can
think of
> > right now:
> >
> > 1. The local user must have "Log on as a batch job"
On Mar 6 13:47, Bill Stewart wrote:
> On Wed, Mar 6, 2019 at 1:14 PM Corinna Vinschen wrote:
>
> > > > > What precisely happens when Cygwin uses MSV1 S4ULogon on versions
> older
> > > > > than 6.3 before a user has logged on?
> > > >
> > > > MsV1S4ULogon returns with STATUS_NOT_SUPPORTED.
On Wed, Mar 6, 2019 at 1:14 PM Corinna Vinschen wrote:
> > > > What precisely happens when Cygwin uses MSV1 S4ULogon on versions
older
> > > > than 6.3 before a user has logged on?
> > >
> > > MsV1S4ULogon returns with STATUS_NOT_SUPPORTED. Funny status code,
> > > given it works if some user
On Mar 6 09:45, Bill Stewart wrote:
> On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
>
> > On Mar 6 08:38, Bill Stewart wrote:
> > > On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> > > > On Mar 6 15:17, Corinna Vinschen wrote:
> > > > > But the old Systems like Windows 7
On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
> On Mar 6 08:38, Bill Stewart wrote:
> > On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> > > On Mar 6 15:17, Corinna Vinschen wrote:
> > > > But the old Systems like Windows 7 don't want to play nice.
> > > >
> > > > - On Vista
On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
> > What precisely happens when Cygwin uses MSV1 S4ULogon on versions older
> > than 6.3 before a user has logged on?
>
> MsV1S4ULogon returns with STATUS_NOT_SUPPORTED. Funny status code,
> given it works if some user already logged in by
On Mar 6 08:38, Bill Stewart wrote:
> On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> > On Mar 6 15:17, Corinna Vinschen wrote:
> > > But the old Systems like Windows 7 don't want to play nice.
> > >
> > > - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> > > at all,
On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen wrote:
> On Mar 6 15:17, Corinna Vinschen wrote:
> > But the old Systems like Windows 7 don't want to play nice.
> >
> > - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> > at all, which required to keep the create_token method
>
On Mar 6 15:17, Corinna Vinschen wrote:
> But the old Systems like Windows 7 don't want to play nice.
>
> - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> at all, which required to keep the create_token method
> available
>
> - On Vista and Windows 7 MsV1_0S4ULogon does
1 - 100 of 1100 matches
Mail list logo
