On Sep 4 14:12, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I couldn't start cygserver as a service with (just) the built DLL in
place.
No idea why. The patch just adds debug output to strace ouptput, nothing
else.
Whatever. I've installed all the
On Sep 5 13:16, Corinna Vinschen wrote:
On Sep 4 14:12, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I couldn't start cygserver as a service with (just) the built DLL in
place.
No idea why. The patch just adds debug output to strace ouptput,
Corinna Vinschen writes:
For simplicity I added this experimental patch to the snapshot I just
uploaded to https://cygwin.com/snapshots/.
I'm ooO so no updates from me on this until I get back.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Factory and
Corinna Vinschen corinna-cygwin at cygwin.com writes:
You already built your own Cygwin DLL, right? What you could do is to
do some good old printf debugging. First let's try to find out if it's
really one of the NetUser calls:
It looks like I need to install more than the DLL to make this
On Sep 4 11:23, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
You already built your own Cygwin DLL, right? What you could do is to
do some good old printf debugging. First let's try to find out if it's
really one of the NetUser calls:
It looks like I need
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I couldn't start cygserver as a service with (just) the built DLL in place.
No idea why. The patch just adds debug output to strace ouptput, nothing
else.
Whatever. I've installed all the binaries from that build and things work
Achim Gratz Stromeko at NexGo.DE writes:
Not the token privileges, I don't think so. But I'm not sure how to check.
If I run the sshd as the user trying to log in, then it works; regardless of
whether the user has administrative privileges or not or with or without
privilege separation enabled
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Don't use privilege separation, then the non-privileged sshd user won't
matter at all. Privsep on Cygwin is only half-useful on Cygwin anyway,
if at all.
I've switched privilege separateion off completely, but no dice. The Access
Denied
Achim Gratz Stromeko at NexGo.DE writes:
The strace shows that it doesn't even *try* to start bash, but it's
entirely unclear why.
Is it possible to run sshd in gdb?
I can attach the debugger but I didn't manage to break into something useful
(or anything at all, really). However, the
On Sep 3 07:17, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Don't use privilege separation, then the non-privileged sshd user won't
matter at all. Privsep on Cygwin is only half-useful on Cygwin anyway,
if at all.
I've switched privilege separateion off
On Sep 3 13:02, Achim Gratz wrote:
Achim Gratz Stromeko at NexGo.DE writes:
The strace shows that it doesn't even *try* to start bash, but it's
entirely unclear why.
Is it possible to run sshd in gdb?
I can attach the debugger but I didn't manage to break into something useful
(or
Achim Gratz Stromeko at nexgo.de writes:
- Windows Server 2012R2 64bit running on hardware
- domain member
- Cygwin 32bit (latest snapshot from 2014-08-31 w/ AD integration)
can anybody confirm they have gotten sshd successfully running? As far
as I can debug this, the sshd I have
On Sep 2 11:51, Achim Gratz wrote:
Achim Gratz Stromeko at nexgo.de writes:
- Windows Server 2012R2 64bit running on hardware
- domain member
- Cygwin 32bit (latest snapshot from 2014-08-31 w/ AD integration)
can anybody confirm they have gotten sshd successfully running? As far
as
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I have no idea what could be wrong in your environment, sorry.
Me neither. I've set all three Cygwin environments up exactly the same way,
using identical users and command lines (just different service names,
obviously).
I still have to
On Sep 2 15:16, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I have no idea what could be wrong in your environment, sorry.
Me neither. I've set all three Cygwin environments up exactly the same way,
using identical users and command lines (just different
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I have no idea what could be wrong in your environment, sorry.
Some more information: up until the check for /etc/nologin everything works.
Things fall apart when sshd tries to switch to the user logging on. I've
traced this again, sshd
Corinna Vinschen writes:
Don't use privilege separation, then the non-privileged sshd user won't
matter at all. Privsep on Cygwin is only half-useful on Cygwin anyway,
if at all. As for the local cyg_server account, I'm not sure. Usually,
a local machine account has no or only limited
On Sep 2 16:24, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I have no idea what could be wrong in your environment, sorry.
Some more information: up until the check for /etc/nologin everything works.
Things fall apart when sshd tries to switch to the user
Achim Gratz Stromeko at nexgo.de writes:
I'm not making progress on this, but I've come to the conclusion that it
is highly unlikely that the existence of the second (64bit) Cygwin
installation has anything to do with the problem, first reported here:
On Aug 19 13:37, Achim Gratz wrote:
I've run strace on both the 32bit and the 64bit sshd and here's the
difference between the two, right after sshd gets an exception 5 from the DC:
32bit
--- Process 5820, exception 0005 at 75BF1D4D
43239 4372793 [waitproc] sshd 2400
Corinna Vinschen writes:
This is a call to the Win32 API call NetUserGetGroups creating an
exception due to an access denied. The difference between 32 and 64
bit is probably a result of the differences in exception handling, and
given that an ExceptionCode 5 will be ignored by Cygwin's
On Aug 19 19:21, Achim Gratz wrote:
Corinna Vinschen writes:
This is a call to the Win32 API call NetUserGetGroups creating an
exception due to an access denied. The difference between 32 and 64
bit is probably a result of the differences in exception handling, and
given that an
Corinna Vinschen writes:
It doesn't matter if it's the same. An exception is generated and 32
and 64 bit versions react differently for whatever reason. It's also
really unnecessary to generate two accounts for this.
I know that now. But at one point I was wondering if somehow the fact
that
I'm not making progress on this, but I've come to the conclusion that it
is highly unlikely that the existence of the second (64bit) Cygwin
installation has anything to do with the problem, first reported here:
http://thread.gmane.org/gmane.os.cygwin/147823
Meanwhile I've tried to make sure
24 matches
Mail list logo
