On Jan 22 17:31, Watson, Hal M (MNIT) wrote:
> >From what I've seen on the mailing list announcements, it appears that this
> >bug has been addressed in test release 1.7.34-005
>
> Can anyone confirm this is true?
No, this is not true. The ssh-host-config and ssh-user-config scripts
are not par
ndrey Repin
Sent: Thursday, January 08, 2015 12:42 PM
To: Corinna Vinschen; cygwin@cygwin.com
Subject: Re: SSHd configuration problems (System error 1376)
Greetings, Corinna Vinschen!
>> Speaking of ssh-host-config, how to specify domain user to run SSHD, while
>> setting up the service th
Greetings, Corinna Vinschen!
>> Speaking of ssh-host-config, how to specify domain user to run SSHD, while
>> setting up the service through script? (Yes, I'm experimenting with
>> snapshot.)
> The ssh-host-config script is supposed to work for simple standalone
> environments, not for AD enviro
On Jan 8 06:09, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> Speaking of ssh-host-config, how to specify domain user to run SSHD, while
> setting up the service through script? (Yes, I'm experimenting with snapshot.)
The ssh-host-config script is supposed to work for simple standalone
On Jan 8 02:38, Houder wrote:
> Corinna wrote:
>
> > The aforementioned message is a result of a change in how the function
> > underlying `id' works.
> [snip]
>
> > The old getgroups iterated through the groups from /etc/groups, and then
> > checked for each group if its SID is available in the
uired:
if ( csih_is_nt2003 || [ "x$csih_FORCE_PRIVILEGED_USER" = "xyes" ] )
then
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/Re-SSHd-configuration-problems-System-error-1376-CONFIRMED-tp113955p114109.html
Sent from the Cygwin list mailing
Greetings, Corinna Vinschen!
Speaking of ssh-host-config, how to specify domain user to run SSHD, while
setting up the service through script? (Yes, I'm experimenting with snapshot.)
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 08.01.2015, <06:07>
Sorry for my terrible english...
--
Problem rep
Corinna wrote:
> The aforementioned message is a result of a change in how the function
> underlying `id' works.
[snip]
> The old getgroups iterated through the groups from /etc/groups, and then
> checked for each group if its SID is available in the user's token.
>
> This behaviour only makes se
ould run.
+ mkpasswd -l > /etc/passwd
+
# use the following procedure if a privileged account is required:
if ( csih_is_nt2003 || [ "x$csih_FORCE_PRIVILEGED_USER" = "xyes" ] )
then
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/Re-SSHd-configurat
-
View this message in context:
http://cygwin.1069669.n5.nabble.com/Re-SSHd-configuration-problems-System-error-1376-CONFIRMED-tp113955p114108.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http:/
rying to add to the group "root"
rather than "Administrators". I had to hack
/usr/share/csih/cygwin-service-installation-helper.sh in a couple of places
to finally make it work for me:
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/Re-SSHd-configurat
On Dec 29 11:30, Ken Brown wrote:
> On 12/29/2014 9:07 AM, Ilya Dogolazky wrote:
> > Hi Ken!
> >
> > I followed your advise:
> > 1) Reinstalled windows again
> > 2) Started setup_x86-64.exe from cygwin web site
> > 3) Changed two things in the package list:
> > a) Changed version of package cygw
*
sc delete sshd
...and rerun ssh-host-config:
ssh-host-config -y
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/Re-SSHd-configuration-problems-System-error-1376-CONFIRMED-tp113955p114101.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports
lly make it work for me:
--
View this message in context:
http://cygwin.1069669.n5.nabble.com/Re-SSHd-configuration-problems-System-error-1376-CONFIRMED-tp113955p114100.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.c
Ok, I'm hopeful this message is going to reach the correct thread.
Thanks for your patience, I was accessing and posting to the discussion via web
browser which is how I discovered it. Now that I'm properly subscribed to the
list and using my email client... on to business.
Regarding sshd co
Greetings, Will Parsons!
Can you include cygcheck output as outlined in the link below?
> Problem reports: http://cygwin.com/problems.html
>>
>>> I've got the plain text file cygcheck.out, but it is unclear to me how I can
>>> attach it to a post in this discussion per t
On 01/05/2015 04:56 PM, Hal Watson wrote:
Larry Hall (Cygwin cygwin.com> writes:
Can you include cygcheck output as outlined in the link below?
Problem reports: http://cygwin.com/problems.html
I've got the plain text file cygcheck.out, but it is unclear to me how I can
attach it to
Andrey Repin wrote:
> Greetings, Hal Watson!
>
>>> Can you include cygcheck output as outlined in the link below?
>>>
>>> > Problem reports: http://cygwin.com/problems.html
>>>
>
>> I've got the plain text file cygcheck.out, but it is unclear to me how I can
>> attach it to a post in this di
Greetings, Hal Watson!
>> Can you include cygcheck output as outlined in the link below?
>>
>> > Problem reports: http://cygwin.com/problems.html
>>
> I've got the plain text file cygcheck.out, but it is unclear to me how I can
> attach it to a post in this discussion per the guidelines (I
Larry Hall (Cygwin cygwin.com> writes:
> Can you include cygcheck output as outlined in the link below?
>
> > Problem reports: http://cygwin.com/problems.html
>
I've got the plain text file cygcheck.out, but it is unclear to me how I can
attach it to a post in this discussion per the guid
On 01/02/2015 05:27 PM, Hal Watson wrote:
Hello all, thanks for this thread.
I just got a request for several new servers this week, and System error
1376 issue has cropped up for the first time. These are fresh installs of
stable release Cygwin X64 on a fresh Windows 2012 Server. The "1376" er
Hello all, thanks for this thread.
I just got a request for several new servers this week, and System error
1376 issue has cropped up for the first time. These are fresh installs of
stable release Cygwin X64 on a fresh Windows 2012 Server. The "1376" error
seems to have cropped up in the last mon
>> If you were really running in an elevated shell, I don't know why 544 didn't
>> show up in the output of "id -G".
>>
>> Ken
> Because Ilya's /etc/group file has a line that reads:
>
> root:S-1-5-32-544:0:
>
> in stead of:
>
> Administrators:S-1-5-32-544:544:
>
> ?
>
> Put differently, he has c
>>>If you were really running in an elevated shell, I don't know why 544
>>>didn't show up in the output of "id -G".
>>>
>>>Ken
>>Because Ilya's /etc/group file has a line that reads:
>>
>>root:S-1-5-32-544:0:
>>
>>in stead of:
>>
>>Administrators:S-1-5-32-5
On 12/29/2014 11:27 PM, Houder wrote:
If you were really running in an elevated shell, I don't know why 544
didn't show up in the output of "id -G".
Ken
Because Ilya's /etc/group file has a line that reads:
root:S-1-5-32-544:0:
in stead of:
Administrators:S-1-5-32-544:544:
?
Put different
12/29/2014 06:30 PM, ext Ken Brown пишет:
If you were really running in an elevated shell, I don't know why 544 didn't show up in
the output of "id -G".
But that's exactly what's happening with the testing version of cygwin
DLL (I wrote a bug report as a new mail thread)
--
Problem reports
> If you were really running in an elevated shell, I don't know why 544 didn't
> show up in the output of "id -G".
>
> Ken
Because Ilya's /etc/group file has a line that reads:
root:S-1-5-32-544:0:
in stead of:
Administrators:S-1-5-32-544:544:
?
Put differently, he has copied an old group fi
On 12/29/2014 9:07 AM, Ilya Dogolazky wrote:
> Hi Ken!
>
> I followed your advise:
> 1) Reinstalled windows again
> 2) Started setup_x86-64.exe from cygwin web site
> 3) Changed two things in the package list:
> a) Changed version of package cygwin to 1.7.34.003
> b) Marked package "ssh" to be
Hi Ken!
I followed your advise:
1) Reinstalled windows again
2) Started setup_x86-64.exe from cygwin web site
3) Changed two things in the package list:
a) Changed version of package cygwin to 1.7.34.003
b) Marked package "ssh" to be installed
4) After installation started terminal (icon right
On 12/29/2014 3:15 AM, Ilya Dogolazky wrote:
Hi Ken !
12/23/2014 05:25 PM, ext Ken Brown wrote:
I'm using the test
release of cygwin in case that's relevant.
I would like to try this.
How do I install the "test release"?
Is it the same as to select "EXP" instead of "CURR" in the top right cor
Hi Ken !
12/23/2014 05:25 PM, ext Ken Brown wrote:
I'm using the test
release of cygwin in case that's relevant.
I would like to try this.
How do I install the "test release"?
Is it the same as to select "EXP" instead of "CURR" in the top right
corner of setup.exe GUI or should I do something
p://cygwin.1069669.n5.nabble.com/SSHd-configuration-problems-System-error-1376-tp113637p113919.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://
On 12/23/2014 8:41 AM, Ilya Dogolazky wrote:
Hi Ken !
12/13/2014 02:30 PM, ext Ken Brown пишет:
admingroup=$(/usr/bin/mkgroup -l | /usr/bin/awk -F: '{if ( $2 ==
"S-1-5-32-544" ) print $1;}')
On my system this yields "Administrators". Apparently it yields "root"
on your system. Any idea wh
Hi Ken !
12/13/2014 02:30 PM, ext Ken Brown пишет:
admingroup=$(/usr/bin/mkgroup -l | /usr/bin/awk -F: '{if ( $2 ==
"S-1-5-32-544" ) print $1;}')
On my system this yields "Administrators". Apparently it yields "root"
on your system. Any idea why?
I have the same error message as PolarSto
Greetings, PolarStorm!
> So to summarize, the following issues have not been addressed:
> (a) The user "sshd" user account password expires after 42 days.
This is your system policy. Never had such issues myself.
> (b) The user is not part of "Administrator" group, severely limiting its
> usabi
On 12/12/2014 8:32 PM, PolarStorm wrote:
*** Warning: Adding user 'cyg_server' to local group 'root' failed!
[...]
Now, the reason for that is that there is no "root" group
in Windows. Instead it's called "Administrators".
The group is obtained in line 2827 of
/usr/share/csih/cygwin-service-in
YGWIN for the daemon: []" is
incomprehensible
For everybody convenience, to fix the password expiration (a), use this
line:
$ wmic useraccount where "Name='sshd'" set PasswordExpires=FALSE
(The extra quotes there are crucial!)
Happy Holiday Wishes!
# CYGWIN_NT-6
37 matches
Mail list logo
