Sv: Problems with native Unix domain sockets on Win 10/2019

2021-03-16 Thread Kristian Ivarsson via Cygwin
Hi all

Does anyone know the status of these fixes ?

I saw an announcement for cygwin-3.2.0-0.1 that seemed to contain some
AF_UNIX-related fixes but I fail to find out where that distribution exists
(if it is supposed to be publicly accessible?), but I tried out the
2021-03-01 snapshot and perhaps they are similar ?

We bumped into some AF_UNIX-related issues when trying the 2021-03-01
-snapshot though. It might be some flaws in our code base but the same code
works in quite a few Linux-distros

We're more than willing to help out with testing this and/or trying to
narrow down any possible cygwin issues, but first we'd be glad if someone
could give us some kind of status report of this (so no one is doing any
unnecessary work)


Best regards,
Kristian

p.s.
   I tried to build the topic/af_unix -branch according to the FAQ, but
there was some issues
d.s.



> > Hi Ken, Corinna
> >
> > Sorry for the delay in responding. I have just tested the fix and it
> > works great. Thank you very much for looking into it.
> >
> > When do you think it would be available in a form that regular users
> > would be able to update/install?
> 
> Corinna decides when to make a new Cygwin release.  My best guess is
> "pretty soon".
> 
> > Also, one observation FYI, is that the "ls -l" command on Unix
> > normally indicates sockets with an "s" as the first character of the
> > output: eg
> >
> > srwxr-xr-x  1 Michael None 0 Feb  7 11:19 foo.sock
> >
> > Currently, what is shown on Cygwin is
> >
> > -rwxr-xr-x  1 Michael None 0 Feb  7 11:19 foo.sock
> >
> > indicating a regular file.
> 
> Right.  From Cygwin's point of view, it is a regular file.  There might
> come a time when Cygwin's AF_UNIX implementation makes use of native
> Windows AF_UNIX sockets on systems that support them.  But that time is
> not currently in sight.
> 
> Ken
> --
> Problem reports:  https://cygwin.com/problems.html
> FAQ:  https://cygwin.com/faq/
> Documentation:https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Sv: Problems with native Unix domain sockets on Win 10/2019

2021-03-16 Thread Michael McMahon via Cygwin

I think you can download pre-released builds from:

https://cygwin.com/snapshots/

As mentioned already, the fix here is not actually support of AF_UNIX 
sockets natively. My understanding is that they are implemented over 
loopback TCP in cygwin, but the fix allows native AF_UNIX sockets to be 
handled (eg deleted) as regular files through regular cygwin commands.


Michael.


On 16/03/2021 11:06, Kristian Ivarsson via Cygwin wrote:

Hi all

Does anyone know the status of these fixes ?

I saw an announcement for cygwin-3.2.0-0.1 that seemed to contain some
AF_UNIX-related fixes but I fail to find out where that distribution exists
(if it is supposed to be publicly accessible?), but I tried out the
2021-03-01 snapshot and perhaps they are similar ?

We bumped into some AF_UNIX-related issues when trying the 2021-03-01
-snapshot though. It might be some flaws in our code base but the same code
works in quite a few Linux-distros

We're more than willing to help out with testing this and/or trying to
narrow down any possible cygwin issues, but first we'd be glad if someone
could give us some kind of status report of this (so no one is doing any
unnecessary work)


Best regards,
Kristian

p.s.
I tried to build the topic/af_unix -branch according to the FAQ, but
there was some issues
d.s.




Hi Ken, Corinna

Sorry for the delay in responding. I have just tested the fix and it
works great. Thank you very much for looking into it.

When do you think it would be available in a form that regular users
would be able to update/install?

Corinna decides when to make a new Cygwin release.  My best guess is
"pretty soon".


Also, one observation FYI, is that the "ls -l" command on Unix
normally indicates sockets with an "s" as the first character of the
output: eg

srwxr-xr-x  1 Michael None 0 Feb  7 11:19 foo.sock

Currently, what is shown on Cygwin is

-rwxr-xr-x  1 Michael None 0 Feb  7 11:19 foo.sock

indicating a regular file.

Right.  From Cygwin's point of view, it is a regular file.  There might
come a time when Cygwin's AF_UNIX implementation makes use of native
Windows AF_UNIX sockets on systems that support them.  But that time is
not currently in sight.

Ken
--
Problem reports:  
https://urldefense.com/v3/__https://cygwin.com/problems.html__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJM8jmPtbA$
FAQ:  
https://urldefense.com/v3/__https://cygwin.com/faq/__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJMQE63Mlg$
Documentation:
https://urldefense.com/v3/__https://cygwin.com/docs.html__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJMRgFcrHA$
Unsubscribe info: 
https://urldefense.com/v3/__https://cygwin.com/ml/*unsubscribe-simple__;Iw!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJPOK0x2gw$

--
Problem reports:  
https://urldefense.com/v3/__https://cygwin.com/problems.html__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJM8jmPtbA$
FAQ:  
https://urldefense.com/v3/__https://cygwin.com/faq/__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJMQE63Mlg$
Documentation:
https://urldefense.com/v3/__https://cygwin.com/docs.html__;!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJMRgFcrHA$
Unsubscribe info: 
https://urldefense.com/v3/__https://cygwin.com/ml/*unsubscribe-simple__;Iw!!GqivPVa7Brio!OrhjUwBgvLe4_I38uHpiucq3-_xiQDxazv5s7XuBkOmzXTgGhz9Vb3GrB2RYCJPOK0x2gw$

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Different symlink resolution in native console vs. terminal

2021-03-16 Thread L A Walsh

On 2021/03/10 14:51, Andrey Repin wrote:

Running `pwd -P` or `readlink -e .` in a specific directory from native
terminal provide unresolved answers.

The directory $HOME/Documents/EVE is a symlink pointing to 
$HOME\Documents\Games\EVE.

When running either command inside the directory from native terminal, the
result is literally /home/Documents/EVE, but when running the same command
from mintty inside same directory, the results may vary.

$HOME/Documents/EVE or $HOME/Documents/Games/EVE (which is expected answer).
It also seems, there are results difference between `bash -l` `and bash -i`
and `pwd -P` and `readlink -e .`.
Generally, "pwd" is more correct.
  

1) When you look at the processes(native v mintty), are both the
same #bits?

2) Can you reproduce this with any other dir?

Both Documents and Games have multiple copies due to the public
docs+games  are in the docs+games library (along with user versions).

Maybe the winterm is picking up a different file?

3) do you actually have a directory named '$HOME' or is it a real
dirname?

4) the symlink is in 'EVE' in both cases, yes?
Can you copy 'EVE' (the symlink) to a dir like /tmp and do they resolve
differently there?

I think one or both of those dirs have a GUID associated with them, maybe
one is using a different GUID than the other?

I also have Win7x64 but have never seen them misbehaving...

How was your link made?


--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Sv: Problems with native Unix domain sockets on Win 10/2019

2021-03-16 Thread Ken Brown via Cygwin

On 3/16/2021 9:00 AM, Michael McMahon via Cygwin wrote:

I think you can download pre-released builds from:

https://cygwin.com/snapshots/


Right, but see below for cygwin-3.2.0-0.1.

As mentioned already, the fix here is not actually support of AF_UNIX sockets 
natively. My understanding is that they are implemented over loopback TCP in 
cygwin, but the fix allows native AF_UNIX sockets to be handled (eg deleted) as 
regular files through regular cygwin commands.


Michael.


On 16/03/2021 11:06, Kristian Ivarsson via Cygwin wrote:

Hi all

Does anyone know the status of these fixes ?

I saw an announcement for cygwin-3.2.0-0.1 that seemed to contain some
AF_UNIX-related fixes but I fail to find out where that distribution exists
(if it is supposed to be publicly accessible?), but I tried out the
2021-03-01 snapshot and perhaps they are similar ?


You can install cygwin-3.2.0-0.1 in the usual way, through Cygwin's setup 
program.  Since it's a test release, you'll have to explicitly select that 
release; setup won't just offer it to you.



We bumped into some AF_UNIX-related issues when trying the 2021-03-01
-snapshot though. It might be some flaws in our code base but the same code
works in quite a few Linux-distros

We're more than willing to help out with testing this and/or trying to
narrow down any possible cygwin issues, but first we'd be glad if someone
could give us some kind of status report of this (so no one is doing any
unnecessary work)


Best regards,
Kristian

p.s.
    I tried to build the topic/af_unix -branch according to the FAQ, but
there was some issues


I'm still in the middle of some things on that branch, and I haven't had much 
time to work on it recently.  I hope to get back to it very soon.  In order to 
build it, you need to add -D__WITH_AF_UNIX to CXXFLAGS.  In order to test it, 
you need


#undef AF_UNIX
#define AF_UNIX 31

after including 

Ken
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


[ANNOUNCEMENT] [SECURITY] stunnel 5.58-1

2021-03-16 Thread Andrew Schulman via Cygwin-announce via Cygwin
stunnel 5.58-1 is now available in Cygwin. This release includes one
security fix related to Cygwin:

* The "redirect" option was fixed to properly handle unauthenticated
requests (thx to Martin Stein).

Plus other new features and bug fixes. Everyone should upgrade to this
release. Please see the upstream changelog[1] for the full list. 

stunnel is a program that allows you to encrypt arbitrary TCP connections
inside TLS (Transport Layer Security, the successor to Secure Sockets Layer
(SSL)).  stunnel can allow you to secure non-TLS-aware daemons and
protocols (like POP, IMAP, LDAP, etc) by having stunnel provide the
encryption, requiring no changes to the daemon's code.

Andrew E. Schulman

[1]https://www.stunnel.org/NEWS.html


***


To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com_at_cygwin.com

If you need more information on unsubscribing, start reading here:

http://cygwin.com/lists.html#subscribe-unsubscribe

Please read *all* of the information on unsubscribing that is available
starting at this URL.
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple