* sshd problem on WS2008R2 64bit
@ 2019-03-06 1:03 Stephen Carrier
2019-03-06 12:12 ` Corinna Vinschen
0 siblings, 1 reply; 18+ messages in thread
From: Stephen Carrier @ 2019-03-06 1:03 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]
Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
fail unless some user logs into Windows first. In this case, that is by
RDP, and it doesn't need to be the same user as the one logging in by ssh.
After logging out of the windows-native session, ssh continues to work.
Windows event logs report a failed attempt for "NULL SID" and
----
Failure Reason: An error occured during Logon.
Status: 0xc00000bb
Sub Status: 0x0
Caller Process Name: C:\cygwin64\usr\sbin\sshd.exe
Detailed Authentication Information:
Logon Process: Cygwin.1
Authentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Key Length: 0
----
Reversion to cygwin 2.11.2 resolves the issue, but upgrading to
cygwin1-20190304.dll snapshot does not.
The system had previously been using CygLSA, see:
----
$ HIVE='/machine/SYSTEM/CurrentControlSet/Control/Lsa'
$ regtool get $HIVE/'Authentication Packages'
msv1_0
C:\cygwin64\bin\cyglsa\cyglsa64.dll
----
I removed cyglsa64.dll from this entry (leaving msv1_0 of course!) and the
symptoms are the same. I understand that Cygwin 3.0 isn't needing Cyglsa.
Cron jobs are also unable to run. Cronevents reports "(CRON) error
(can't switch user context)" until after first windows login, and works
from that point forward.
Is this a limitation of seteuid() or msv1_0 on WS2008R2?
All important&critical windows updates have been applied.
Cron and Sshd are running as LocalSystem.
Output from cygcheck attached.
Is this a known problem? Is there any workaround or fix to let cron
and sshd work without a windows login first to prime the pump? Thanks,
Stephen Carrier
BEAR Center
UC Berkeley
[-- Attachment #2: cygcheck.out --]
[-- Type: text/plain, Size: 38495 bytes --]
Cygwin Configuration Diagnostics
Current System Time: Wed Mar 06 00:55:28 2019
Windows 2008 R2 Server Datacenter Ver 6.1 Build 7601 Service Pack 1
Path: C:\cygwin64\home\Administrator\script
C:\cygwin64\usr\local\bin
C:\cygwin64\usr\sbin
C:\cygwin64\bin
C:\windows\system32
C:\Program Files (x86)\Gow\bin
Output from C:\cygwin64\bin\id.exe
UID: 197108(Administrator)
GID: 197121(None)
197121(None)
114(Local account and member of Administrators group)
544(Administrators)
545(Users)
2(NETWORK)
11(Authenticated Users)
15(This Organization)
113(Local account)
4095(CurrentSession)
262154(NTLM Authentication)
405504(High Mandatory Level)
SysDir: C:\Windows\system32
WinDir: C:\Windows
USER = 'Administrator'
PWD = '/tmp'
HOME = '/home/Administrator'
USERDOMAIN = 'ILDB-STAGE2015'
OS = 'Windows_NT'
PROCESSOR_LEVEL = '6'
PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files (x86)\AWS Tools\PowerShell\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules\;C:\Program Files (x86)\Microsoft SQL Server\120\Tools\PowerShell\Modules\'
CommonProgramW6432 = 'C:\Program Files\Common Files'
SSH_CONNECTION = '173.164.243.238 59996 10.10.30.87 45000'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
FP_NO_HOST_CHECK = 'NO'
LANG = 'en_US.UTF-8'
TZ = 'Etc/GMT'
CommonProgramFiles = 'C:\Program Files\Common Files'
HOSTNAME = 'ILDB-STAGE2015'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/tmp'
USERNAME = 'Administrator'
LOGONSERVER = '\\ILDB-STAGE2015'
PROCESSOR_ARCHITECTURE = 'AMD64'
LOCALAPPDATA = 'C:\Users\Administrator\AppData\Local'
COMPUTERNAME = 'ILDB-STAGE2015'
SYSTEMDRIVE = 'C:'
USERPROFILE = 'C:\Users\Administrator'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
SYSTEMROOT = 'C:\Windows'
PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 62 Stepping 4, GenuineIntel'
TMP = '/tmp'
SSH_CLIENT = '173.164.243.238 59996 45000'
windows_tracing_logfile = 'C:\BVTBin\Tests\installpackage\csilogfile.log'
PROCESSOR_REVISION = '3e04'
PROFILEREAD = 'true'
NUMBER_OF_PROCESSORS = '2'
ProgramW6432 = 'C:\Program Files'
SSH_TTY = '/dev/pty1'
windows_tracing_flags = '3'
MAIL = '/var/spool/mail//Administrator'
COMSPEC = 'C:\Windows\system32\cmd.exe'
APPDATA = 'C:\Users\Administrator\AppData\Roaming'
TERM = 'vt100'
SHELL = '/bin/bash'
WINDIR = 'C:\Windows'
ProgramData = 'C:\ProgramData'
SHLVL = '1'
PRINTER = 'Microsoft XPS Document Writer'
PROGRAMFILES = 'C:\Program Files'
ALLUSERSPROFILE = 'C:\ProgramData'
TEMP = '/tmp'
LOGNAME = 'Administrator'
ProgramFiles(x86) = 'C:\Program Files (x86)'
PS1 = 'ILDB-STAGE2015# '
HOMEDRIVE = 'C:'
INFOPATH = '/usr/local/info:/usr/share/info:/usr/info'
HOMEPATH = '\cygwin64\home\Administrator'
ORIGINAL_PATH = '/usr/local/bin:/usr/sbin:/bin:/cygdrive/c/windows/system32:/cygdrive/c/Program Files (x86)/Gow/bin:/bin'
EXECIGNORE = '*.dll'
_ = '/bin/cygcheck'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
(default) = '\??\C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
(default) = 'C:\cygwin64'
obcaseinsensitive set to 1
Cygwin installations found in the registry:
System: Key: e022582115c10879 Path: C:\cygwin64
c: hd NTFS 49149Mb 72% CP CS UN PA FC QU
d: hd NTFS 65533Mb 66% CP CS UN PA FC QU
z: hd NTFS 30709Mb 1% CP CS UN PA FC QU Temporary Storage 2
C:\cygwin64 / system binary,auto
C:\cygwin64\bin /usr/bin system binary,auto
C:\cygwin64\lib /usr/lib system binary,auto
cygdrive prefix /cygdrive user binary,posix=0,auto
Found: C:\cygwin64\bin\awk
Found: C:\Program Files (x86)\Gow\bin\awk.exe
Warning: C:\cygwin64\bin\awk hides C:\Program Files (x86)\Gow\bin\awk.exe
-> C:\cygwin64\bin\gawk.exe
Found: C:\cygwin64\bin\bash.exe
Found: C:\Program Files (x86)\Gow\bin\bash.exe
Warning: C:\cygwin64\bin\bash.exe hides C:\Program Files (x86)\Gow\bin\bash.exe
Found: C:\cygwin64\bin\cat.exe
Found: C:\Program Files (x86)\Gow\bin\cat.exe
Warning: C:\cygwin64\bin\cat.exe hides C:\Program Files (x86)\Gow\bin\cat.exe
Found: C:\cygwin64\bin\cp.exe
Found: C:\Program Files (x86)\Gow\bin\cp.exe
Warning: C:\cygwin64\bin\cp.exe hides C:\Program Files (x86)\Gow\bin\cp.exe
Found: C:\cygwin64\bin\cpp.exe
Found: C:\cygwin64\bin\crontab.exe
Found: C:\cygwin64\bin\find.exe
Found: C:\windows\system32\find.exe
Warning: C:\cygwin64\bin\find.exe hides C:\windows\system32\find.exe
Found: C:\cygwin64\bin\gcc.exe
Not Found: gdb
Found: C:\cygwin64\bin\grep.exe
Found: C:\Program Files (x86)\Gow\bin\grep.exe
Warning: C:\cygwin64\bin\grep.exe hides C:\Program Files (x86)\Gow\bin\grep.exe
Found: C:\cygwin64\bin\kill.exe
Found: C:\cygwin64\bin\ld.exe
Found: C:\cygwin64\bin\ls.exe
Found: C:\Program Files (x86)\Gow\bin\ls.exe
Warning: C:\cygwin64\bin\ls.exe hides C:\Program Files (x86)\Gow\bin\ls.exe
Found: C:\cygwin64\bin\make.exe
Found: C:\Program Files (x86)\Gow\bin\make.exe
Warning: C:\cygwin64\bin\make.exe hides C:\Program Files (x86)\Gow\bin\make.exe
Found: C:\cygwin64\bin\mv.exe
Found: C:\Program Files (x86)\Gow\bin\mv.exe
Warning: C:\cygwin64\bin\mv.exe hides C:\Program Files (x86)\Gow\bin\mv.exe
Found: C:\Program Files (x86)\Gow\bin\patch.exe
Found: C:\cygwin64\bin\perl.exe
Found: C:\cygwin64\bin\rm.exe
Found: C:\Program Files (x86)\Gow\bin\rm.exe
Warning: C:\cygwin64\bin\rm.exe hides C:\Program Files (x86)\Gow\bin\rm.exe
Found: C:\cygwin64\bin\sed.exe
Found: C:\Program Files (x86)\Gow\bin\sed.exe
Warning: C:\cygwin64\bin\sed.exe hides C:\Program Files (x86)\Gow\bin\sed.exe
Found: C:\cygwin64\bin\ssh.exe
Found: C:\cygwin64\bin\sh.exe
Found: C:\cygwin64\bin\tar.exe
Found: C:\Program Files (x86)\Gow\bin\tar.exe
Warning: C:\cygwin64\bin\tar.exe hides C:\Program Files (x86)\Gow\bin\tar.exe
Found: C:\cygwin64\bin\test.exe
Found: C:\Program Files (x86)\Gow\bin\test.exe
Warning: C:\cygwin64\bin\test.exe hides C:\Program Files (x86)\Gow\bin\test.exe
Found: C:\cygwin64\bin\vi.exe
Found: C:\cygwin64\bin\vim.exe
Found: C:\Program Files (x86)\Gow\bin\vim.exe
Warning: C:\cygwin64\bin\vim.exe hides C:\Program Files (x86)\Gow\bin\vim.exe
39k 2016/09/19 C:\cygwin64\bin\cygargp-0.dll - os=4.0 img=0.0 sys=5.2
"cygargp-0.dll" v0.0 ts=2016-09-19 02:13
29k 2018/12/09 C:\cygwin64\bin\cygatomic-1.dll - os=4.0 img=0.0 sys=5.2
"cygatomic-1.dll" v0.0 ts=2018-12-08 22:53
19k 2018/12/20 C:\cygwin64\bin\cygattr-1.dll - os=4.0 img=0.0 sys=5.2
"cygattr-1.dll" v0.0 ts=2018-12-20 09:48
60k 2018/02/04 C:\cygwin64\bin\cygbind9-160.dll - os=4.0 img=0.0 sys=5.2
"cygbind9-160.dll" v0.0 ts=2018-02-04 06:26
237k 2019/01/02 C:\cygwin64\bin\cygblkid-1.dll - os=4.0 img=0.0 sys=5.2
"cygblkid-1.dll" v0.0 ts=2019-01-02 02:52
64k 2017/02/22 C:\cygwin64\bin\cygbz2-1.dll - os=4.0 img=0.0 sys=5.2
"cygbz2-1.dll" v0.0 ts=2017-02-22 07:22
13k 2013/03/06 C:\cygwin64\bin\cygcatgets1.dll - os=4.0 img=0.0 sys=5.2
"cygcatgets1.dll" v0.0 ts=2013-03-06 14:34
117k 2013/05/05 C:\cygwin64\bin\cygcloog-isl-4.dll - os=4.0 img=0.0 sys=5.2
"cygcloog-isl-4.dll" v0.0 ts=2013-05-05 16:41
13k 2019/01/02 C:\cygwin64\bin\cygcom_err-2.dll - os=4.0 img=0.0 sys=5.2
"cygcom_err-2.dll" v0.0 ts=2019-01-02 02:39
39k 2017/09/03 C:\cygwin64\bin\cygcrypt-0.dll - os=4.0 img=0.0 sys=5.2
"cygcrypt-0.dll" v0.0 ts=2017-09-03 08:18
2346k 2018/08/27 C:\cygwin64\bin\cygcrypto-1.0.0.dll - os=4.0 img=0.0 sys=5.2
"cygcrypto-1.0.0.dll" v0.0 ts=2018-08-27 18:14
507k 2018/03/15 C:\cygwin64\bin\cygcurl-4.dll - os=4.0 img=0.0 sys=5.2
"cygcurl-4.dll" v0.0 ts=2018-03-15 16:22
1552k 2017/09/28 C:\cygwin64\bin\cygdb-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb-5.3.dll" v0.0 ts=2017-09-28 20:05
267k 2017/08/10 C:\cygwin64\bin\cygdbus-1-3.dll - os=4.0 img=0.0 sys=5.2
"cygdbus-1-3.dll" v0.0 ts=2017-08-10 06:10
119k 2017/09/28 C:\cygwin64\bin\cygdb_cxx-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb_cxx-5.3.dll" v0.0 ts=2017-09-28 20:06
569k 2017/09/28 C:\cygwin64\bin\cygdb_sql-5.3.dll - os=4.0 img=0.0 sys=5.2
"cygdb_sql-5.3.dll" v0.0 ts=2017-09-28 20:06
2017k 2018/02/04 C:\cygwin64\bin\cygdns-169.dll - os=4.0 img=0.0 sys=5.2
"cygdns-169.dll" v0.0 ts=2018-02-04 06:25
154k 2013/10/20 C:\cygwin64\bin\cygedit-0.dll - os=4.0 img=0.0 sys=5.2
"cygedit-0.dll" v0.0 ts=2013-10-20 21:56
181k 2018/09/27 C:\cygwin64\bin\cygexpat-1.dll - os=4.0 img=0.0 sys=5.2
"cygexpat-1.dll" v0.0 ts=2018-09-27 18:30
30k 2014/10/14 C:\cygwin64\bin\cygfam-0.dll - os=4.0 img=0.0 sys=5.2
"cygfam-0.dll" v0.0 ts=2014-10-14 21:33
335k 2019/01/02 C:\cygwin64\bin\cygfdisk-1.dll - os=4.0 img=0.0 sys=5.2
"cygfdisk-1.dll" v0.0 ts=2019-01-02 02:52
27k 2015/11/17 C:\cygwin64\bin\cygffi-6.dll - os=4.0 img=0.0 sys=5.2
"cygffi-6.dll" v0.0 ts=2015-11-17 22:14
65k 2017/12/05 C:\cygwin64\bin\cygformw-10.dll - os=4.0 img=0.0 sys=5.2
"cygformw-10.dll" v0.0 ts=2017-12-05 08:15
122k 2018/12/17 C:\cygwin64\bin\cyggc-1.dll - os=4.0 img=0.0 sys=5.2
"cyggc-1.dll" v0.0 ts=2018-12-17 07:14
70k 2018/12/09 C:\cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
"cyggcc_s-seh-1.dll" v0.0 ts=2018-12-08 19:56
1099k 2018/03/19 C:\cygwin64\bin\cyggcrypt-20.dll - os=4.0 img=0.0 sys=5.2
"cyggcrypt-20.dll" v0.0 ts=2018-03-19 20:09
39k 2016/10/10 C:\cygwin64\bin\cyggdbm-4.dll - os=4.0 img=0.0 sys=5.2
"cyggdbm-4.dll" v0.0 ts=2016-10-10 09:26
13k 2016/10/10 C:\cygwin64\bin\cyggdbm_compat-4.dll - os=4.0 img=0.0 sys=5.2
"cyggdbm_compat-4.dll" v0.0 ts=2016-10-10 09:26
187k 2016/11/08 C:\cygwin64\bin\cygGeoIP-1.dll - os=4.0 img=0.0 sys=5.2
"cygGeoIP-1.dll" v0.0 ts=2016-11-08 18:21
1398k 2018/02/11 C:\cygwin64\bin\cyggio-2.0-0.dll - os=4.0 img=0.0 sys=5.2
"cyggio-2.0-0.dll" v0.0 ts=2018-02-11 19:03
993k 2018/02/11 C:\cygwin64\bin\cygglib-2.0-0.dll - os=4.0 img=0.0 sys=5.2
"cygglib-2.0-0.dll" v0.0 ts=2018-02-11 19:01
15k 2018/02/11 C:\cygwin64\bin\cyggmodule-2.0-0.dll - os=4.0 img=0.0 sys=5.2
"cyggmodule-2.0-0.dll" v0.0 ts=2018-02-11 19:01
527k 2017/01/21 C:\cygwin64\bin\cyggmp-10.dll - os=4.0 img=0.0 sys=5.2
"cyggmp-10.dll" v0.0 ts=2017-01-21 18:25
21k 2017/01/21 C:\cygwin64\bin\cyggmpxx-4.dll - os=4.0 img=0.0 sys=5.2
"cyggmpxx-4.dll" v0.0 ts=2017-01-21 18:25
938k 2017/05/02 C:\cygwin64\bin\cyggnutls-28.dll - os=4.0 img=0.0 sys=5.2
"cyggnutls-28.dll" v0.0 ts=2017-05-02 22:06
1207k 2018/03/15 C:\cygwin64\bin\cyggnutls-30.dll - os=4.0 img=0.0 sys=5.2
"cyggnutls-30.dll" v0.0 ts=2018-03-15 23:08
24k 2017/05/02 C:\cygwin64\bin\cyggnutls-openssl-27.dll - os=4.0 img=0.0 sys=5.2
"cyggnutls-openssl-27.dll" v0.0 ts=2017-05-02 22:06
289k 2018/02/11 C:\cygwin64\bin\cyggobject-2.0-0.dll - os=4.0 img=0.0 sys=5.2
"cyggobject-2.0-0.dll" v0.0 ts=2018-02-11 19:02
148k 2018/12/09 C:\cygwin64\bin\cyggomp-1.dll - os=4.0 img=0.0 sys=5.2
"cyggomp-1.dll" v0.0 ts=2018-12-08 20:21
95k 2018/03/19 C:\cygwin64\bin\cyggpg-error-0.dll - os=4.0 img=0.0 sys=5.2
"cyggpg-error-0.dll" v0.0 ts=2018-03-19 19:27
274k 2018/03/16 C:\cygwin64\bin\cyggssapi_krb5-2.dll - os=4.0 img=0.0 sys=5.2
"cyggssapi_krb5-2.dll" v0.0 ts=2018-03-16 03:38
9k 2018/02/11 C:\cygwin64\bin\cyggthread-2.0-0.dll - os=4.0 img=0.0 sys=5.2
"cyggthread-2.0-0.dll" v0.0 ts=2018-02-11 19:01
1333k 2018/08/07 C:\cygwin64\bin\cygguile-2.0-22.dll - os=4.0 img=0.0 sys=5.2
"cygguile-2.0-22.dll" v0.0 ts=2018-08-07 08:10
33k 2017/02/13 C:\cygwin64\bin\cyghistory7.dll - os=4.0 img=0.0 sys=5.2
"cyghistory7.dll" v0.0 ts=2017-02-11 22:39
167k 2016/03/13 C:\cygwin64\bin\cyghogweed-2.dll - os=4.0 img=0.0 sys=5.2
"cyghogweed-2.dll" v0.0 ts=2016-03-13 14:46
163k 2018/03/15 C:\cygwin64\bin\cyghogweed-4.dll - os=4.0 img=0.0 sys=5.2
"cyghogweed-4.dll" v0.0 ts=2018-03-16 00:07
210k 2018/12/15 C:\cygwin64\bin\cyghwloc-15.dll - os=4.0 img=0.0 sys=5.2
"cyghwloc-15.dll" v0.0 ts=2018-12-15 06:33
173k 2018/09/03 C:\cygwin64\bin\cyghwloc-5.dll - os=4.0 img=0.0 sys=5.2
"cyghwloc-5.dll" v0.0 ts=2018-09-03 09:50
1009k 2015/02/20 C:\cygwin64\bin\cygiconv-2.dll - os=4.0 img=0.0 sys=5.2
"cygiconv-2.dll" v0.0 ts=2015-02-20 17:07
197k 2017/05/02 C:\cygwin64\bin\cygidn-11.dll - os=4.0 img=0.0 sys=5.2
"cygidn-11.dll" v0.0 ts=2017-05-02 01:18
111k 2017/09/25 C:\cygwin64\bin\cygidn2-0.dll - os=4.0 img=0.0 sys=5.2
"cygidn2-0.dll" v0.0 ts=2017-09-25 03:16
42k 2016/10/23 C:\cygwin64\bin\cygintl-8.dll - os=4.0 img=0.0 sys=5.2
"cygintl-8.dll" v0.0 ts=2016-10-23 07:17
294k 2013/09/09 C:\cygwin64\bin\cygiodbc-2.dll - os=4.0 img=0.0 sys=5.2
"cygiodbc-2.dll" v0.0 ts=2013-09-09 16:36
66k 2013/09/09 C:\cygwin64\bin\cygiodbcinst-2.dll - os=4.0 img=0.0 sys=5.2
"cygiodbcinst-2.dll" v0.0 ts=2013-09-09 16:35
39k 2018/02/04 C:\cygwin64\bin\cygirs-160.dll - os=4.0 img=0.0 sys=5.2
"cygirs-160.dll" v0.0 ts=2018-02-04 06:26
405k 2018/02/04 C:\cygwin64\bin\cygisc-166.dll - os=4.0 img=0.0 sys=5.2
"cygisc-166.dll" v0.0 ts=2018-02-04 06:23
116k 2018/02/04 C:\cygwin64\bin\cygisccfg-160.dll - os=4.0 img=0.0 sys=5.2
"cygisccfg-160.dll" v0.0 ts=2018-02-04 06:25
888k 2013/05/05 C:\cygwin64\bin\cygisl-10.dll - os=4.0 img=0.0 sys=5.2
"cygisl-10.dll" v0.0 ts=2013-05-05 16:36
1304k 2017/11/04 C:\cygwin64\bin\cygisl-15.dll - os=4.0 img=0.0 sys=5.2
"cygisl-15.dll" v0.0 ts=2017-11-04 20:36
36k 2015/12/29 C:\cygwin64\bin\cygjson-c-2.dll - os=4.0 img=0.0 sys=5.2
"cygjson-c-2.dll" v0.0 ts=2015-12-29 18:44
192k 2018/03/16 C:\cygwin64\bin\cygk5crypto-3.dll - os=4.0 img=0.0 sys=5.2
"cygk5crypto-3.dll" v0.0 ts=2018-03-16 03:37
754k 2018/03/16 C:\cygwin64\bin\cygkrb5-3.dll - os=4.0 img=0.0 sys=5.2
"cygkrb5-3.dll" v0.0 ts=2018-03-16 03:37
37k 2018/03/16 C:\cygwin64\bin\cygkrb5support-0.dll - os=4.0 img=0.0 sys=5.2
"cygkrb5support-0.dll" v0.0 ts=2018-03-16 03:36
45k 2015/11/19 C:\cygwin64\bin\cyglber-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cyglber-2-4-2.dll" v0.0 ts=2015-11-19 14:17
303k 2017/11/27 C:\cygwin64\bin\cyglcms2-2.dll - os=4.0 img=0.0 sys=5.2
"cyglcms2-2.dll" v0.0 ts=2017-11-27 15:44
246k 2015/11/19 C:\cygwin64\bin\cygldap-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cygldap-2-4-2.dll" v0.0 ts=2015-11-19 14:18
262k 2015/11/19 C:\cygwin64\bin\cygldap_r-2-4-2.dll - os=4.0 img=0.0 sys=5.2
"cygldap_r-2-4-2.dll" v0.0 ts=2015-11-19 14:19
72k 2017/01/27 C:\cygwin64\bin\cyglmdb-0.dll - os=4.0 img=0.0 sys=5.2
"cyglmdb-0.dll" v0.0 ts=2017-01-27 18:20
35k 2018/05/29 C:\cygwin64\bin\cygltdl-7.dll - os=4.0 img=0.0 sys=5.2
"cygltdl-7.dll" v0.0 ts=2018-05-29 15:34
71k 2018/02/04 C:\cygwin64\bin\cyglwres-160.dll - os=4.0 img=0.0 sys=5.2
"cyglwres-160.dll" v0.0 ts=2018-02-04 06:26
73k 2017/06/19 C:\cygwin64\bin\cyglz4-1.dll - os=4.0 img=0.0 sys=5.2
"cyglz4-1.dll" v0.0 ts=2017-06-19 15:40
139k 2017/05/10 C:\cygwin64\bin\cyglzma-5.dll - os=4.0 img=0.0 sys=5.2
"cyglzma-5.dll" v0.0 ts=2017-05-10 01:17
129k 2017/10/05 C:\cygwin64\bin\cyglzo2-2.dll - os=4.0 img=0.0 sys=5.2
"cyglzo2-2.dll" v0.0 ts=2017-10-05 19:40
125k 2018/03/18 C:\cygwin64\bin\cygmagic-1.dll - os=4.0 img=0.0 sys=5.2
"cygmagic-1.dll" v0.0 ts=2018-03-18 15:17
736k 2018/11/19 C:\cygwin64\bin\cygmailutils-5.dll - os=4.0 img=0.0 sys=5.2
"cygmailutils-5.dll" v0.0 ts=2018-11-19 13:56
168k 2018/01/23 C:\cygwin64\bin\cygman-2-7-6-1.dll - os=4.0 img=0.0 sys=5.2
"cygman-2-7-6-1.dll" v0.0 ts=2018-01-23 20:22
22k 2018/01/23 C:\cygwin64\bin\cygmandb-2-7-6-1.dll - os=4.0 img=0.0 sys=5.2
"cygmandb-2-7-6-1.dll" v0.0 ts=2018-01-23 20:22
155k 2013/05/29 C:\cygwin64\bin\cygmcrypt-4.dll - os=4.0 img=0.0 sys=5.2
"cygmcrypt-4.dll" v0.0 ts=2013-05-29 14:09
33k 2017/12/05 C:\cygwin64\bin\cygmenuw-10.dll - os=4.0 img=0.0 sys=5.2
"cygmenuw-10.dll" v0.0 ts=2017-12-05 08:15
42k 2013/08/12 C:\cygwin64\bin\cygmetalink-3.dll - os=4.0 img=0.0 sys=5.2
"cygmetalink-3.dll" v0.0 ts=2013-08-13 00:02
163k 2013/05/29 C:\cygwin64\bin\cygmhash-2.dll - os=4.0 img=0.0 sys=5.2
"cygmhash-2.dll" v0.0 ts=2013-05-29 23:29
92k 2018/03/17 C:\cygwin64\bin\cygmpc-3.dll - os=4.0 img=0.0 sys=5.2
"cygmpc-3.dll" v0.0 ts=2018-03-17 17:05
346k 2017/11/04 C:\cygwin64\bin\cygmpfr-4.dll - os=4.0 img=0.0 sys=5.2
"cygmpfr-4.dll" v0.0 ts=2017-11-04 18:48
432k 2019/02/02 C:\cygwin64\bin\cygmpfr-6.dll - os=4.0 img=0.0 sys=5.2
"cygmpfr-6.dll" v0.0 ts=2019-02-02 18:25
64k 2018/11/19 C:\cygwin64\bin\cygmuaux-5.dll - os=4.0 img=0.0 sys=5.2
"cygmuaux-5.dll" v0.0 ts=2018-11-19 13:58
40k 2018/11/19 C:\cygwin64\bin\cygmu_auth-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_auth-5.dll" v0.0 ts=2018-11-19 13:57
22k 2018/11/19 C:\cygwin64\bin\cygmu_dbm-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_dbm-5.dll" v0.0 ts=2018-11-19 13:59
86k 2018/11/19 C:\cygwin64\bin\cygmu_imap-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_imap-5.dll" v0.0 ts=2018-11-19 13:57
24k 2018/11/19 C:\cygwin64\bin\cygmu_maildir-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_maildir-5.dll" v0.0 ts=2018-11-19 13:58
46k 2018/11/19 C:\cygwin64\bin\cygmu_mailer-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_mailer-5.dll" v0.0 ts=2018-11-19 13:58
36k 2018/11/19 C:\cygwin64\bin\cygmu_mbox-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_mbox-5.dll" v0.0 ts=2018-11-19 13:57
17k 2018/11/19 C:\cygwin64\bin\cygmu_mh-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_mh-5.dll" v0.0 ts=2018-11-19 13:58
46k 2018/11/19 C:\cygwin64\bin\cygmu_pop-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_pop-5.dll" v0.0 ts=2018-11-19 13:57
122k 2018/11/19 C:\cygwin64\bin\cygmu_sieve-5.dll - os=4.0 img=0.0 sys=5.2
"cygmu_sieve-5.dll" v0.0 ts=2018-11-19 13:59
317k 2017/12/05 C:\cygwin64\bin\cygncursesw-10.dll - os=4.0 img=0.0 sys=5.2
"cygncursesw-10.dll" v0.0 ts=2017-12-05 08:13
180k 2016/03/13 C:\cygwin64\bin\cygnettle-4.dll - os=4.0 img=0.0 sys=5.2
"cygnettle-4.dll" v0.0 ts=2016-03-13 14:46
207k 2018/03/15 C:\cygwin64\bin\cygnettle-6.dll - os=4.0 img=0.0 sys=5.2
"cygnettle-6.dll" v0.0 ts=2018-03-16 00:07
140k 2018/03/16 C:\cygwin64\bin\cygnghttp2-14.dll - os=4.0 img=0.0 sys=5.2
"cygnghttp2-14.dll" v0.0 ts=2018-03-16 02:04
1019k 2018/04/09 C:\cygwin64\bin\cygp11-kit-0.dll - os=4.0 img=0.0 sys=5.2
"cygp11-kit-0.dll" v0.0 ts=2018-04-09 01:55
15k 2017/12/05 C:\cygwin64\bin\cygpanelw-10.dll - os=4.0 img=0.0 sys=5.2
"cygpanelw-10.dll" v0.0 ts=2017-12-05 08:14
475k 2017/04/23 C:\cygwin64\bin\cygpcre-1.dll - os=4.0 img=0.0 sys=5.2
"cygpcre-1.dll" v0.0 ts=2017-04-24 00:50
11k 2017/04/23 C:\cygwin64\bin\cygpcreposix-0.dll - os=4.0 img=0.0 sys=5.2
"cygpcreposix-0.dll" v0.0 ts=2017-04-24 00:50
2209k 2018/12/01 C:\cygwin64\bin\cygperl5_26.dll - os=4.0 img=0.0 sys=5.2
"cygperl5_26.dll" v0.0 ts=2018-12-01 07:22
39k 2015/04/09 C:\cygwin64\bin\cygpipeline-1.dll - os=4.0 img=0.0 sys=5.2
"cygpipeline-1.dll" v0.0 ts=2015-04-09 21:04
41k 2016/07/13 C:\cygwin64\bin\cygpopt-0.dll - os=4.0 img=0.0 sys=5.2
"cygpopt-0.dll" v0.0 ts=2016-07-13 06:16
57k 2017/06/15 C:\cygwin64\bin\cygprocps-6.dll - os=4.0 img=0.0 sys=5.2
"cygprocps-6.dll" v0.0 ts=2017-06-15 20:30
53k 2017/08/11 C:\cygwin64\bin\cygpsl-5.dll - os=4.0 img=0.0 sys=5.2
"cygpsl-5.dll" v0.0 ts=2017-08-11 06:56
315k 2018/12/09 C:\cygwin64\bin\cygquadmath-0.dll - os=4.0 img=0.0 sys=5.2
"cygquadmath-0.dll" v0.0 ts=2018-12-08 22:57
219k 2017/02/13 C:\cygwin64\bin\cygreadline7.dll - os=4.0 img=0.0 sys=5.2
"cygreadline7.dll" v0.0 ts=2017-02-11 22:39
96k 2017/04/16 C:\cygwin64\bin\cygsasl2-3.dll - os=4.0 img=0.0 sys=5.2
"cygsasl2-3.dll" v0.0 ts=2017-04-16 19:15
11k 2015/07/17 C:\cygwin64\bin\cygsigsegv-2.dll - os=4.0 img=0.0 sys=5.2
"cygsigsegv-2.dll" v0.0 ts=2015-07-17 22:35
141k 2019/01/02 C:\cygwin64\bin\cygsmartcols-1.dll - os=4.0 img=0.0 sys=5.2
"cygsmartcols-1.dll" v0.0 ts=2019-01-02 02:51
996k 2017/11/06 C:\cygwin64\bin\cygsqlite3-0.dll - os=4.0 img=0.0 sys=5.2
"cygsqlite3-0.dll" v0.0 ts=2017-11-06 12:43
156k 2016/03/02 C:\cygwin64\bin\cygssh2-1.dll - os=4.0 img=0.0 sys=5.2
"cygssh2-1.dll" v0.0 ts=2016-03-02 18:03
406k 2018/08/27 C:\cygwin64\bin\cygssl-1.0.0.dll - os=4.0 img=0.0 sys=5.2
"cygssl-1.0.0.dll" v0.0 ts=2018-08-27 18:14
12k 2017/11/13 C:\cygwin64\bin\cygssp-0.dll - os=4.0 img=0.0 sys=5.2
"cygssp-0.dll" v0.0 ts=2017-11-13 21:52
1400k 2018/12/09 C:\cygwin64\bin\cygstdc++-6.dll - os=4.0 img=0.0 sys=5.2
"cygstdc++-6.dll" v0.0 ts=2018-12-08 21:15
377k 2017/05/03 C:\cygwin64\bin\cygsybdb-5.dll - os=4.0 img=0.0 sys=5.2
"cygsybdb-5.dll" v0.0 ts=2017-05-03 08:46
67k 2018/03/19 C:\cygwin64\bin\cygtasn1-6.dll - os=4.0 img=0.0 sys=5.2
"cygtasn1-6.dll" v0.0 ts=2018-03-19 21:41
58k 2017/12/05 C:\cygwin64\bin\cygticw-10.dll - os=4.0 img=0.0 sys=5.2
"cygticw-10.dll" v0.0 ts=2017-12-05 08:13
1612k 2018/08/16 C:\cygwin64\bin\cygunistring-2.dll - os=4.0 img=0.0 sys=5.2
"cygunistring-2.dll" v0.0 ts=2018-08-16 20:33
26k 2019/01/02 C:\cygwin64\bin\cyguuid-1.dll - os=4.0 img=0.0 sys=5.2
"cyguuid-1.dll" v0.0 ts=2019-01-02 02:51
8k 2016/06/13 C:\cygwin64\bin\cygvtv-0.dll - os=4.0 img=0.0 sys=5.2
"cygvtv-0.dll" v0.0 ts=2016-06-13 17:12
8k 2016/06/13 C:\cygwin64\bin\cygvtv_stubs-0.dll - os=4.0 img=0.0 sys=5.2
"cygvtv_stubs-0.dll" v0.0 ts=2016-06-13 17:12
3261k 2019/03/05 C:\cygwin64\bin\cygwin1-2.11.2.dll - os=4.0 img=0.0 sys=5.2
"cygwin1.dll" v0.0 ts=2018-11-08 13:34
3407k 2019/03/05 C:\cygwin64\bin\cygwin1-20190304.dll - os=4.0 img=0.0 sys=5.2
"cygwin1.dll" v0.0 ts=2019-03-04 19:39
3407k 2019/03/05 C:\cygwin64\bin\cygwin1-dist.dll - os=4.0 img=0.0 sys=5.2
"cygwin1.dll" v0.0 ts=2019-02-20 10:20
31k 2018/07/14 C:\cygwin64\bin\cygwrap-0.dll - os=4.0 img=0.0 sys=5.2
"cygwrap-0.dll" v0.0 ts=2018-07-14 11:43
1214k 2017/03/13 C:\cygwin64\bin\cygxml2-2.dll - os=4.0 img=0.0 sys=5.2
"cygxml2-2.dll" v0.0 ts=2017-03-13 17:01
83k 2017/03/03 C:\cygwin64\bin\cygz.dll - os=4.0 img=0.0 sys=5.2
"cygz.dll" v0.0 ts=2017-03-03 21:42
3407k 2019/03/05 C:\cygwin64\bin\cygwin1.dll - os=4.0 img=0.0 sys=5.2
"cygwin1.dll" v0.0 ts=2019-02-20 10:20
Cygwin DLL version info:
DLL version: 3.0.1
DLL epoch: 19
DLL old termios: 5
DLL malloc env: 28
Cygwin conv: 181
API major: 0
API minor: 338
Shared data: 5
DLL identifier: cygwin1
Mount registry: 3
Cygwin registry name: Cygwin
Installations name: Installations
Cygdrive default prefix:
Build date:
Shared id: cygwin1S5
Service : cron
Display name : CYGWIN cron
Current State : Running
Controls Accepted : Stop
Command : /usr/sbin/cron -n
stdin path : /dev/null
stdout path : /var/log/cron.log
stderr path : /var/log/cron.log
Environment : PATH="/usr/local/bin:/usr/sbin:/bin:/cygdrive/c/windows/system32" TMP="/tmp"
Process Type : Own Process
Startup : Automatic
Account : LocalSystem
Service : cygserver
Display name : CYGWIN cygserver
Current State : Running
Controls Accepted : Stop
Command : /usr/sbin/cygserver
stdin path : /dev/null
stdout path : /var/log/cygserver.log
stderr path : /var/log/cygserver.log
Process Type : Own Process
Startup : Automatic
Account : LocalSystem
Service : sshd
Display name : CYGWIN sshd
Current State : Running
Controls Accepted : Stop
Command : /usr/sbin/sshd -D -e
stdin path : /dev/null
stdout path : /var/log/sshd.log
stderr path : /var/log/sshd.log
Environment : PATH="/usr/local/bin:/usr/sbin:/bin:/cygdrive/c/windows/system32:/cygdrive/c/Program Files (x86)/Gow/bin"
Process Type : Own Process
Startup : Automatic
Dependencies : tcpip
Account : LocalSystem
Cygwin Package Information
Last downloaded files to: C:\CygwinPackages
Last downloaded files from: http://mirrors.sonic.net/cygwin/
Package Version Status
_autorebase 001007-1 OK
Empty package _update-info-dir
_update-info-dir 03000-1 OK
alternatives 1.3.30c-10 OK
base-cygwin 3.8-1 OK
base-files 4.2-4 OK
bash 4.4.12-3 OK
bind-utils 9.11.2-2.P1 OK
binutils 2.29-1 OK
bzip2 1.0.6-3 OK
ca-certificates 2.22-1 OK
coreutils 8.26-2 OK
cron 4.1-65 OK
Empty package crypt
crypt 2.1-1 OK
csih 0.9.11-1 OK
curl 7.59.0-1 OK
cygrunsrv 1.62-1 OK
cygutils 1.4.16-2 OK
cygwin 3.0.1-1 OK
cygwin-devel 3.0.1-1 OK
dash 0.5.9.1-1 OK
desktop-file-utils 0.23-1 OK
diffutils 3.5-2 OK
dos2unix 7.4.0-1 OK
editrights 1.03-1 OK
emacs 26.1-1 OK
file 5.32-1 OK
file-devel 5.32-1 OK
findutils 4.6.0-1 OK
freetds 1.00.37-1 OK
gamin 0.1.10-15 OK
gawk 4.2.1-1 OK
gcc-core 7.4.0-1 OK
GeoIP-database 20180505-1 OK
getent 2.18.90-4 OK
git 2.17.0-1 OK
Empty package gmp
gmp 6.1.2-1 OK
grep 3.0-2 OK
groff 1.22.3-1 OK
gsettings-desktop-schemas 3.24.1-1 OK
gzip 1.8-1 OK
hostname 3.13-1 OK
hwloc 2.0.3-1 OK
inetutils 1.9.4-1 OK
inetutils-server 1.9.4-1 OK
info 6.6-1 OK
ipc-utils 1.0-2 OK
less 530-1 OK
libargp 20110921-3 OK
libatomic1 7.4.0-1 OK
libattr1 2.4.48-2 OK
libbind9_160 9.11.2-2.P1 OK
libblkid1 2.32.1-1 OK
libbz2_1 1.0.6-3 OK
libcatgets1 1.1-2 OK
libcloog-isl4 0.18.0-2 OK
libcom_err2 1.44.5-1 OK
libcrypt0 2.1-1 OK
libcurl4 7.59.0-1 OK
libdb5.3 5.3.28-2 OK
libdbus1_3 1.10.22-1 OK
libdns169 9.11.2-2.P1 OK
libedit0 20130712-1 OK
libexpat1 2.2.6-1 OK
libfam0 0.1.10-15 OK
libfdisk1 2.32.1-1 OK
libffi6 3.2.1-2 OK
libgc1 7.6.10-1 OK
libgcc1 7.4.0-1 OK
libgcrypt20 1.8.2-1 OK
libgdbm4 1.12-1 OK
libGeoIP1 1.6.9-1 OK
libglib2.0_0 2.54.3-1 OK
libgmp-devel 6.1.2-1 OK
libgmp10 6.1.2-1 OK
libgmpxx4 6.1.2-1 OK
libgnutls28 3.3.27-1 OK
libgnutls30 3.5.18-1 OK
libgomp1 7.4.0-1 OK
libgpg-error0 1.28-1 OK
libgssapi_krb5_2 1.15.2-2 OK
libguile2.0_22 2.0.14-3 OK
libhogweed2 2.7.1-1 OK
libhogweed4 3.4-1 OK
libhwloc15 2.0.3-1 OK
libhwloc5 1.11.11-1 OK
libiconv 1.14-3 OK
libiconv2 1.14-3 OK
libidn11 1.33-1 OK
libidn2_0 2.0.4-1 OK
libintl8 0.19.8.1-2 OK
libiodbc2 3.52.8-2 OK
libirs160 9.11.2-2.P1 OK
libisc166 9.11.2-2.P1 OK
libisccfg160 9.11.2-2.P1 OK
libisl10 0.11.1-2 OK
libisl15 0.16.1-1 OK
libjson-c-common 0.12-1 OK
libjson-c2 0.12-1 OK
libk5crypto3 1.15.2-2 OK
libkrb5_3 1.15.2-2 OK
libkrb5support0 1.15.2-2 OK
liblcms2_2 2.9-1 OK
liblmdb0 0.9.19-1 OK
libltdl7 2.4.6-6 OK
liblwres160 9.11.2-2.P1 OK
liblz4_1 1.7.5-1 OK
liblzma5 5.2.3-1 OK
liblzo2_2 2.10-1 OK
libmailutils-sieve-extensions 3.5-1 OK
libmailutils5 3.5-1 OK
libmcrypt4 2.5.8-1 OK
libmetalink3 0.1.2-1 OK
libmhash2 0.9.9.9-2 OK
libmpc3 1.1.0-1 OK
libmpfr4 3.1.6-1p1 OK
libmpfr6 4.0.2-1 OK
libncursesw10 6.0-12.20171125 OK
libnettle4 2.7.1-1 OK
libnettle6 3.4-1 OK
libnghttp2_14 1.31.0-1 OK
libopenldap2_4_2 2.4.42-1 OK
libopenssl100 1.0.2p-1 OK
libp11-kit0 0.23.10-1 OK
libpcre1 8.40-3 OK
libpcreposix0 8.40-3 OK
libpipeline1 1.4.0-1 OK
libpopt-common 1.16-2 OK
libpopt0 1.16-2 OK
libprocps-ng6 3.3.12-2 OK
libpsl5 0.18.0-1 OK
libquadmath0 7.4.0-1 OK
libreadline7 7.0.3-3 OK
libsasl2_3 2.1.26-11 OK
libsigsegv2 2.10-2 OK
libsmartcols1 2.32.1-1 OK
libsqlite3_0 3.21.0-1 OK
libssh2_1 1.7.0-1 OK
libssp0 6.4.0-4 OK
libstdc++6 7.4.0-1 OK
libsybdb5 1.00.37-1 OK
libtasn1_6 4.13-1 OK
libunistring2 0.9.10-1 OK
libuuid-devel 2.32.1-1 OK
libuuid1 2.32.1-1 OK
libvtv0 5.4.0-1 OK
libwrap0 7.6-26 OK
libxml2 2.9.4-2 OK
login 1.12-1 OK
lynx 2.8.7-2 OK
mailutils 3.5-1 OK
make 4.2.1-2 OK
man-db 2.7.6.1-1 OK
mcrypt 2.6.8-1 OK
mintty 2.9.6-0 OK
msmtp 1.6.6-1 OK
mysql 10.1.30-1 OK
mysql-common 10.1.30-1 OK
nc 1.107-4 OK
ncurses 6.0-12.20171125 OK
openssh 7.9p1-1 OK
openssl 1.0.2p-1 OK
p11-kit 0.23.10-1 OK
p11-kit-trust 0.23.10-1 OK
p7zip 15.14.1-1 OK
perl 5.26.3-1 OK
Empty package perl-Carp
perl-Carp 1.38-2 OK
perl-CGI 4.40-1 OK
perl-Error 0.17027-1 OK
perl-HTML-Parser 3.72-2 OK
perl-HTML-Tagset 3.20-6 OK
perl-Scalar-List-Utils 1.50-1 OK
perl-TermReadKey 2.38-1 OK
perl_autorebase 5.26.3-1 OK
perl_base 5.26.3-1 OK
pkg-config 0.29.1-1 OK
Empty package popt
popt 1.16-2 OK
Empty package procps
procps 3.3.10-1 OK
procps-ng 3.3.12-2 OK
psmisc 22.20-1 OK
publicsuffix-list-dafsa 20180523-1 OK
pv 1.4.12-1 OK
python-pip-wheel 19.0.2-1 OK
python-setuptools-wheel 40.7.3-1 OK
python2 2.7.15-1 OK
python2-appdirs 1.4.3-1 OK
python2-asn1crypto 0.22.0-1 OK
python2-bcrypt 3.1.4-1 OK
python2-cffi 1.9.1-1 OK
python2-cryptography 1.8.1-1 OK
python2-enum34 1.1.6-1 OK
python2-idna 2.5-1 OK
python2-ipaddress 1.0.18-1 OK
python2-magic 5.32-1 OK
python2-nacl 1.2.1-1 OK
python2-packaging 16.8-1 OK
python2-paramiko 2.4.1-1 OK
python2-ply 3.9-1 OK
python2-pyasn1 0.2.3-1 OK
python2-pycparser 2.17-1 OK
python2-pyparsing 2.1.10-1 OK
python2-six 1.10.0-1 OK
python27 2.7.15-1 OK
python27-setuptools 40.7.3-1 OK
rebase 4.4.4-1 OK
rsync 3.1.2-1 OK
run 1.3.4-2 OK
screen 4.6.2-1 OK
sed 4.4-1 OK
shared-mime-info 1.8-1 OK
ssmtp 2.64-8 OK
tar 1.29-1 OK
tcsh 6.20.00-1 OK
terminfo 6.0-12.20171125 OK
terminfo-extra 6.0-12.20171125 OK
time 1.9-1 OK
tzcode 2018i-1 OK
tzdata 2018i-1 OK
unzip 6.0-17 OK
upx 3.91-1 OK
util-linux 2.25.2-2 OK
vim 8.0.1567-1 OK
vim-common 8.0.1567-1 OK
vim-minimal 8.0.1567-1 OK
w32api-headers 5.0.4-1 OK
w32api-runtime 5.0.4-1 OK
wget 1.19.1-2 OK
which 2.20-2 OK
windows-default-manifest 6.4-1 OK
xxd 8.0.1567-1 OK
xz 5.2.3-1 OK
zip 3.0-12 OK
zlib0 1.2.11-1 OK
Use -h to see help about each section
[-- Attachment #3: Type: text/plain, Size: 219 bytes --]
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 1:03 sshd problem on WS2008R2 64bit Stephen Carrier
@ 2019-03-06 12:12 ` Corinna Vinschen
2019-03-06 12:48 ` Corinna Vinschen
0 siblings, 1 reply; 18+ messages in thread
From: Corinna Vinschen @ 2019-03-06 12:12 UTC (permalink / raw)
To: Stephen Carrier; +Cc: cygwin
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
On Mar 5 17:02, Stephen Carrier wrote:
> Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> fail unless some user logs into Windows first. In this case, that is by
> RDP, and it doesn't need to be the same user as the one logging in by ssh.
> After logging out of the windows-native session, ssh continues to work.
>
> Windows event logs report a failed attempt for "NULL SID" and
>
> ----
> Failure Reason: An error occured during Logon.
> Status: 0xc00000bb
This is weird. Status 0xc00000bb is STATUS_NOT_SUPPORTED. That
doesn't make sense, at least not on 2008 R2 with 64 bit Cygwin.
Are you trying to login via sshd with a local account or a domain
account?
I tried to reproduce your issue with Cygwin 3.0.2 on a Windows 10
machine. I rebooted the machine and did not login locally or via
RDP. Sshd login worked in both cases (local/domain account).
Can you test this again, in particular with installing Cygwin 3.0.2?
In the meantime, I need some time to set up a Windows 2008 R2
machine for testing.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 12:12 ` Corinna Vinschen
@ 2019-03-06 12:48 ` Corinna Vinschen
2019-03-06 14:17 ` Corinna Vinschen
0 siblings, 1 reply; 18+ messages in thread
From: Corinna Vinschen @ 2019-03-06 12:48 UTC (permalink / raw)
To: Stephen Carrier; +Cc: cygwin
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Mar 6 13:11, Corinna Vinschen wrote:
> On Mar 5 17:02, Stephen Carrier wrote:
> > Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> > fail unless some user logs into Windows first. In this case, that is by
> > RDP, and it doesn't need to be the same user as the one logging in by ssh.
> > After logging out of the windows-native session, ssh continues to work.
> >
> > Windows event logs report a failed attempt for "NULL SID" and
> >
> > ----
> > Failure Reason: An error occured during Logon.
> > Status: 0xc00000bb
>
> This is weird. Status 0xc00000bb is STATUS_NOT_SUPPORTED. That
> doesn't make sense, at least not on 2008 R2 with 64 bit Cygwin.
>
> Are you trying to login via sshd with a local account or a domain
> account?
>
> I tried to reproduce your issue with Cygwin 3.0.2 on a Windows 10
> machine. I rebooted the machine and did not login locally or via
> RDP. Sshd login worked in both cases (local/domain account).
>
> Can you test this again, in particular with installing Cygwin 3.0.2?
>
> In the meantime, I need some time to set up a Windows 2008 R2
> machine for testing.
Never mind, I can reproduce the problem on Windows 7, but only
for local machine accounts. Domain accounts work fine.
Oh well,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 12:48 ` Corinna Vinschen
@ 2019-03-06 14:17 ` Corinna Vinschen
2019-03-06 14:34 ` Corinna Vinschen
0 siblings, 1 reply; 18+ messages in thread
From: Corinna Vinschen @ 2019-03-06 14:17 UTC (permalink / raw)
To: Stephen Carrier; +Cc: cygwin
[-- Attachment #1: Type: text/plain, Size: 2798 bytes --]
On Mar 6 13:48, Corinna Vinschen wrote:
> On Mar 6 13:11, Corinna Vinschen wrote:
> > On Mar 5 17:02, Stephen Carrier wrote:
> > > Since upgrading a WS2008 R2 system to 3.0.1, attempts to ssh to the server
> > > fail unless some user logs into Windows first. In this case, that is by
> > > RDP, and it doesn't need to be the same user as the one logging in by ssh.
> > > After logging out of the windows-native session, ssh continues to work.
> > >
> > > Windows event logs report a failed attempt for "NULL SID" and
> > >
> > > ----
> > > Failure Reason: An error occured during Logon.
> > > Status: 0xc00000bb
> >
> > This is weird. Status 0xc00000bb is STATUS_NOT_SUPPORTED. That
> > doesn't make sense, at least not on 2008 R2 with 64 bit Cygwin.
> >
> > Are you trying to login via sshd with a local account or a domain
> > account?
> >
> > I tried to reproduce your issue with Cygwin 3.0.2 on a Windows 10
> > machine. I rebooted the machine and did not login locally or via
> > RDP. Sshd login worked in both cases (local/domain account).
> >
> > Can you test this again, in particular with installing Cygwin 3.0.2?
> >
> > In the meantime, I need some time to set up a Windows 2008 R2
> > machine for testing.
>
> Never mind, I can reproduce the problem on Windows 7, but only
> for local machine accounts. Domain accounts work fine.
This is *so* weird.
When I run the service under the cyg_server account, then the S4U logon
for the local SAM user works as expected, even right after reboot.
The weird thing here is that my cyg_server account is a domain account.
What this has to do with the MsV1_0S4ULogon for a local SAM account
beats me. The only explanation I have for that is that the service
running under the domain cyg_server account constitutes some kind of
"local login", so MsV1_0S4ULogon subsequently starts working.
This cyg_server account does not necessarily require the "create token"
permission anymore, of course.
Big sigh here.
With S4U I had hoped to catch two birds with one stone:
- Getting rid of two old methods, cyglsa and "create token".
- Dropping the requirement for the cyg_server account.
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 not work without
some user logged in locally, even if it's just the cyg_server
service account.
Question is, what is a good solution? Reverting cyglsa as
well to allow the old methods to work as before? This is
the opposite of what I had hoped to accomplish :(
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 14:17 ` Corinna Vinschen
@ 2019-03-06 14:34 ` Corinna Vinschen
2019-03-06 15:30 ` Bill Stewart
0 siblings, 1 reply; 18+ messages in thread
From: Corinna Vinschen @ 2019-03-06 14:34 UTC (permalink / raw)
To: Stephen Carrier; +Cc: cygwin
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
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 not work without
> some user logged in locally, even if it's just the cyg_server
> service account.
FTR, Windows 8 / Server 2012 is affected as well,
Windows 8.1 / Server 2012 R2 is not.
>
> Question is, what is a good solution? Reverting cyglsa as
> well to allow the old methods to work as before? This is
> the opposite of what I had hoped to accomplish :(
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 14:34 ` Corinna Vinschen
@ 2019-03-06 15:30 ` Bill Stewart
2019-03-06 15:34 ` Corinna Vinschen
0 siblings, 1 reply; 18+ messages in thread
From: Bill Stewart @ 2019-03-06 15:30 UTC (permalink / raw)
To: cygwin
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
> > available
> >
> > - On Vista and Windows 7 MsV1_0S4ULogon does not work without
> > some user logged in locally, even if it's just the cyg_server
> > service account.
>
> FTR, Windows 8 / Server 2012 is affected as well,
> Windows 8.1 / Server 2012 R2 is not.
> >
> > Question is, what is a good solution? Reverting cyglsa as
> > well to allow the old methods to work as before? This is
> > the opposite of what I had hoped to accomplish :(
I agree that the new S4U logon method is by far the best solution.
It seems to me that this MSV1 S4ULogon behavior on versions older than NT
6.3 (Vista/Srv2008/Win7/Srv2008R2/Win8/Srv2012) is not expected.
What precisely happens when Cygwin uses MSV1 S4ULogon on versions older
than 6.3 before a user has logged on?
Bill
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 15:30 ` Bill Stewart
@ 2019-03-06 15:34 ` Corinna Vinschen
2019-03-06 15:59 ` Bill Stewart
2019-03-06 16:45 ` Bill Stewart
0 siblings, 2 replies; 18+ messages in thread
From: Corinna Vinschen @ 2019-03-06 15:34 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
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, which required to keep the create_token method
> > > available
> > >
> > > - On Vista and Windows 7 MsV1_0S4ULogon does not work without
> > > some user logged in locally, even if it's just the cyg_server
> > > service account.
> >
> > FTR, Windows 8 / Server 2012 is affected as well,
> > Windows 8.1 / Server 2012 R2 is not.
> > >
> > > Question is, what is a good solution? Reverting cyglsa as
> > > well to allow the old methods to work as before? This is
> > > the opposite of what I had hoped to accomplish :(
>
> I agree that the new S4U logon method is by far the best solution.
>
> It seems to me that this MSV1 S4ULogon behavior on versions older than NT
> 6.3 (Vista/Srv2008/Win7/Srv2008R2/Win8/Srv2012) is not expected.
>
> 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 other means...
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 15:34 ` Corinna Vinschen
@ 2019-03-06 15:59 ` Bill Stewart
2019-03-06 16:45 ` Bill Stewart
1 sibling, 0 replies; 18+ messages in thread
From: Bill Stewart @ 2019-03-06 15:59 UTC (permalink / raw)
To: cygwin
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 other means...
Agreed. It seems to me that this behavior is not expected (bug/defect).
Can someone provide a short sample test program that illustrates this
specific problem?
It is possible that I have the ability to address this with Microsoft
through a support resource.
Bill
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 15:34 ` Corinna Vinschen
2019-03-06 15:59 ` Bill Stewart
@ 2019-03-06 16:45 ` Bill Stewart
2019-03-06 20:13 ` Corinna Vinschen
1 sibling, 1 reply; 18+ messages in thread
From: Bill Stewart @ 2019-03-06 16:45 UTC (permalink / raw)
To: cygwin
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 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 not work without
> > > > some user logged in locally, even if it's just the cyg_server
> > > > service account.
> > >
> > > FTR, Windows 8 / Server 2012 is affected as well,
> > > Windows 8.1 / Server 2012 R2 is not.
> > > >
> > > > Question is, what is a good solution? Reverting cyglsa as
> > > > well to allow the old methods to work as before? This is
> > > > the opposite of what I had hoped to accomplish :(
> >
> > I agree that the new S4U logon method is by far the best solution.
> >
> > It seems to me that this MSV1 S4ULogon behavior on versions older than
NT
> > 6.3 (Vista/Srv2008/Win7/Srv2008R2/Win8/Srv2012) is not expected.
> >
> > 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 other means...
OK, so here's another potential workaround that doesn't require running the
service as a specific user...
Create a scheduled task to run using the following settings:
General -> Run using user account - > choose a local account
General -> "Run whether user is logged on or not"
Triggers -> Run at system startup
Actions -> Start a program -> Program/script: %SystemRoot%\Cystem32\cmd.exe
Actions -> Start a program -> Add arguments: /c exit
Full password logon is required (seems we can't use "do not store password"
option).
The local account does not have to be a member of Administrators, but it
does require user right "Log on as a batch job" (SeBatchLogonRight).
In my prefunctory testing this seems to fix this problem.
Does this work?
Bill
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 16:45 ` Bill Stewart
@ 2019-03-06 20:13 ` Corinna Vinschen
2019-03-06 20:48 ` Bill Stewart
0 siblings, 1 reply; 18+ messages in thread
From: Corinna Vinschen @ 2019-03-06 20:13 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 2644 bytes --]
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 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 not work without
> > > > > some user logged in locally, even if it's just the cyg_server
> > > > > service account.
> > > >
> > > > FTR, Windows 8 / Server 2012 is affected as well,
> > > > Windows 8.1 / Server 2012 R2 is not.
> > > > >
> > > > > Question is, what is a good solution? Reverting cyglsa as
> > > > > well to allow the old methods to work as before? This is
> > > > > the opposite of what I had hoped to accomplish :(
> > >
> > > I agree that the new S4U logon method is by far the best solution.
> > >
> > > It seems to me that this MSV1 S4ULogon behavior on versions older than
> NT
> > > 6.3 (Vista/Srv2008/Win7/Srv2008R2/Win8/Srv2012) is not expected.
> > >
> > > 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 other means...
>
> OK, so here's another potential workaround that doesn't require running the
> service as a specific user...
>
> Create a scheduled task to run using the following settings:
>
> General -> Run using user account - > choose a local account
> General -> "Run whether user is logged on or not"
> Triggers -> Run at system startup
> Actions -> Start a program -> Program/script: %SystemRoot%\Cystem32\cmd.exe
> Actions -> Start a program -> Add arguments: /c exit
>
> Full password logon is required (seems we can't use "do not store password"
> option).
>
> The local account does not have to be a member of Administrators, but it
> does require user right "Log on as a batch job" (SeBatchLogonRight).
>
> In my prefunctory testing this seems to fix this problem.
>
> Does this work?
This does indeed work in my local testing on Windows 7, with a local
dummy user just for this scheduled job and sshd running under SYSTEM.
Now, if that's a feasible workaround for users of these older
systems...?
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 20:13 ` Corinna Vinschen
@ 2019-03-06 20:48 ` Bill Stewart
2019-03-06 20:59 ` Corinna Vinschen
0 siblings, 1 reply; 18+ messages in thread
From: Bill Stewart @ 2019-03-06 20:48 UTC (permalink / raw)
To: cygwin
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 already logged in by other means...
> >
> > OK, so here's another potential workaround that doesn't require running
the
> > service as a specific user...
> >
> > Create a scheduled task to run using the following settings:
> >
> > General -> Run using user account - > choose a local account
> > General -> "Run whether user is logged on or not"
> > Triggers -> Run at system startup
> > Actions -> Start a program -> Program/script:
%SystemRoot%\Cystem32\cmd.exe
> > Actions -> Start a program -> Add arguments: /c exit
> >
> > Full password logon is required (seems we can't use "do not store
password"
> > option).
> >
> > The local account does not have to be a member of Administrators, but it
> > does require user right "Log on as a batch job" (SeBatchLogonRight).
> >
> > In my prefunctory testing this seems to fix this problem.
> >
> > Does this work?
>
> This does indeed work in my local testing on Windows 7, with a local
> dummy user just for this scheduled job and sshd running under SYSTEM.
>
> Now, if that's a feasible workaround for users of these older
> systems...?
Good -- this works for me also. (My wild guess, which may be wrong, is that
the older OS versions don't initialize MSV1 S4ULogon for some reason until
somebody logs on.)
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" (SeBatchLogonRight)
user right.
2. The "Network access: Do not allow storage of passwords and credentials
for network authentication" security policy must be set to "Disabled". (If
this policy is set to "Enabled", then you can't create scheduled tasks with
stored passwords.)
It's a weird problem. The best option would be for Microsoft to provide a
fix (if we can provide a short example program that reproduces it).
Regards,
Bill
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 20:48 ` Bill Stewart
@ 2019-03-06 20:59 ` Corinna Vinschen
2019-03-06 21:25 ` Bill Stewart
2019-03-07 6:15 ` Brian Inglis
0 siblings, 2 replies; 18+ messages in thread
From: Corinna Vinschen @ 2019-03-06 20:59 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 2905 bytes --]
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. Funny status code,
> > > > given it works if some user already logged in by other means...
> > >
> > > OK, so here's another potential workaround that doesn't require running
> the
> > > service as a specific user...
> > >
> > > Create a scheduled task to run using the following settings:
> > >
> > > General -> Run using user account - > choose a local account
> > > General -> "Run whether user is logged on or not"
> > > Triggers -> Run at system startup
> > > Actions -> Start a program -> Program/script:
> %SystemRoot%\Cystem32\cmd.exe
> > > Actions -> Start a program -> Add arguments: /c exit
> > >
> > > Full password logon is required (seems we can't use "do not store
> password"
> > > option).
> > >
> > > The local account does not have to be a member of Administrators, but it
> > > does require user right "Log on as a batch job" (SeBatchLogonRight).
> > >
> > > In my prefunctory testing this seems to fix this problem.
> > >
> > > Does this work?
> >
> > This does indeed work in my local testing on Windows 7, with a local
> > dummy user just for this scheduled job and sshd running under SYSTEM.
> >
> > Now, if that's a feasible workaround for users of these older
> > systems...?
>
> Good -- this works for me also. (My wild guess, which may be wrong, is that
> the older OS versions don't initialize MSV1 S4ULogon for some reason until
> somebody logs on.)
>
> 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" (SeBatchLogonRight)
> user right.
>
> 2. The "Network access: Do not allow storage of passwords and credentials
> for network authentication" security policy must be set to "Disabled". (If
> this policy is set to "Enabled", then you can't create scheduled tasks with
> stored passwords.)
>
> It's a weird problem. The best option would be for Microsoft to provide a
> fix (if we can provide a short example program that reproduces it).
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 Windows release a couple of years
ago. A fix for the problem has been refused because the problem was
fixed in the newer OS. I got told literally that the fix is to upgrade
to the newer OS.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 20:59 ` Corinna Vinschen
@ 2019-03-06 21:25 ` Bill Stewart
2019-03-06 23:44 ` Stephen Paul Carrier
2019-03-07 6:15 ` Brian Inglis
1 sibling, 1 reply; 18+ messages in thread
From: Bill Stewart @ 2019-03-06 21:25 UTC (permalink / raw)
To: cygwin
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" (SeBatchLogonRight)
> > user right.
> >
> > 2. The "Network access: Do not allow storage of passwords and
credentials
> > for network authentication" security policy must be set to "Disabled".
(If
> > this policy is set to "Enabled", then you can't create scheduled tasks
with
> > stored passwords.)
> >
> > It's a weird problem. The best option would be for Microsoft to provide
a
> > fix (if we can provide a short example program that reproduces it).
>
> 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 Windows release a couple of years
> ago. A fix for the problem has been refused because the problem was
> fixed in the newer OS. I got told literally that the fix is to upgrade
> to the newer OS.
You are probably right about that.
I guess you're stuck explaining this quirk in the documentation and
explaining the workarounds.
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
Regards,
Bill
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 21:25 ` Bill Stewart
@ 2019-03-06 23:44 ` Stephen Paul Carrier
2019-03-06 23:54 ` Stephen Paul Carrier
0 siblings, 1 reply; 18+ messages in thread
From: Stephen Paul Carrier @ 2019-03-06 23:44 UTC (permalink / raw)
To: cygwin
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 familiar with it, but I
found this bash sequence that does the trick:
-----
PW=`dd if=/dev/random bs=15 count=1 | base 64`
net user s4udummy /add
net user s4udummy $PW
wmic USERACCOUNT WHERE NAME=\'s4udummy\' SET PasswordExpires=FALSE
/usr/bin/editrights -u s4udummy -a SeBatchLogonRight
schtasks /create /tn wake-s4u /sc ONSTART /ru s4udummy /rp $PW \
/tr '"$SYSTEMROOT"\\System32\\cmd.exe /c exit'
sc config cron depend= Schedule
-----
I added the last statement, to make cron dependent on the Task Scheduler,
because my crontabs use '@reboot' and I am worried about cron trying
to spawn an important job before the Task Scheduler has a chance to
fix seteuid().
The dependency isn't logically sufficient as wake-s4u job needs some
time to finish. But its working so far. I can configure cron to start
with a delay should Task Scheduler ever lose the race.
Thanks everyone for quick attention to this problem and the workaround!
--Stephen
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 23:44 ` Stephen Paul Carrier
@ 2019-03-06 23:54 ` Stephen Paul Carrier
0 siblings, 0 replies; 18+ messages in thread
From: Stephen Paul Carrier @ 2019-03-06 23:54 UTC (permalink / raw)
To: cygwin
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: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-06 20:59 ` Corinna Vinschen
2019-03-06 21:25 ` Bill Stewart
@ 2019-03-07 6:15 ` Brian Inglis
2019-03-07 8:54 ` Corinna Vinschen
1 sibling, 1 reply; 18+ messages in thread
From: Brian Inglis @ 2019-03-07 6:15 UTC (permalink / raw)
To: cygwin
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 Windows release a couple of years
> ago. A fix for the problem has been refused because the problem was
> fixed in the newer OS. I got told literally that the fix is to upgrade
> to the newer OS.
No backports on rolling releases reminds me of some other project? ;^p
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-07 6:15 ` Brian Inglis
@ 2019-03-07 8:54 ` Corinna Vinschen
2019-03-07 14:04 ` Brian Inglis
0 siblings, 1 reply; 18+ messages in thread
From: Corinna Vinschen @ 2019-03-07 8:54 UTC (permalink / raw)
To: cygwin
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
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 2020-01-14.
> > - I opened a support case for an older Windows release a couple of years
> > ago. A fix for the problem has been refused because the problem was
> > fixed in the newer OS. I got told literally that the fix is to upgrade
> > to the newer OS.
>
> No backports on rolling releases reminds me of some other project? ;^p
Why, I can't imagine which project that could be...
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: sshd problem on WS2008R2 64bit
2019-03-07 8:54 ` Corinna Vinschen
@ 2019-03-07 14:04 ` Brian Inglis
0 siblings, 0 replies; 18+ messages in thread
From: Brian Inglis @ 2019-03-07 14:04 UTC (permalink / raw)
To: cygwin
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 Extended
>>> Support Cycle, all ending on 2020-01-14.
>>> - I opened a support case for an older Windows release a couple of years
>>> ago. A fix for the problem has been refused because the problem was
>>> fixed in the newer OS. I got told literally that the fix is to upgrade
>>> to the newer OS.
>> No backports on rolling releases reminds me of some other project? ;^p
> Why, I can't imagine which project that could be...
One that *doesn't have* design botches that can't be fixed by the maintenance
team, but needs a redesign by the product team to fix in a later major release.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2019-03-07 14:04 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-06 1:03 sshd problem on WS2008R2 64bit Stephen Carrier
2019-03-06 12:12 ` Corinna Vinschen
2019-03-06 12:48 ` Corinna Vinschen
2019-03-06 14:17 ` Corinna Vinschen
2019-03-06 14:34 ` Corinna Vinschen
2019-03-06 15:30 ` Bill Stewart
2019-03-06 15:34 ` Corinna Vinschen
2019-03-06 15:59 ` Bill Stewart
2019-03-06 16:45 ` Bill Stewart
2019-03-06 20:13 ` Corinna Vinschen
2019-03-06 20:48 ` Bill Stewart
2019-03-06 20:59 ` Corinna Vinschen
2019-03-06 21:25 ` Bill Stewart
2019-03-06 23:44 ` Stephen Paul Carrier
2019-03-06 23:54 ` Stephen Paul Carrier
2019-03-07 6:15 ` Brian Inglis
2019-03-07 8:54 ` Corinna Vinschen
2019-03-07 14:04 ` Brian Inglis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).