Re: Problems with ssh-host-config and /var/run directory

[Brian Inglis]

On 2017-05-26 15:21, Henning Peters wrote:
> Am 25.05.17 23:36, schrieb Brian Inglis:
>> On 2017-05-25 13:24, Henning Peters wrote:
>>> I switched from 32bit to 64 bis a week ago, moved "cygwin" to "cygwin32" and
>>> reinstalled from scratch into a new "cygwin" directory.
>>> when trying to setup sshd using ssh-host-config, I get this message when
>>> using StrictModes (which I want to and did before on cygwin32 on this 
>>> system):
>>> *** Warning: The owner and the Administrators need
>>> *** Warning: to have .w. permission to /var/run.
>>> *** Warning: Here are the current permissions and ACLS:
>>> *** Warning: drwxrwxrwt+ 1 faroul root 0 May 19 20:56 /var/run
>>> *** Warning: # file: /var/run
>>> *** Warning: # owner: faroul
>>> *** Warning: # group: root
>>> *** Warning: # flags: --t
>>> *** Warning: user::rwx
>>> *** Warning: group::rwx
>>> *** Warning: group:root:rwx
>>> *** Warning: group:SYSTEM:rwx
>>> *** Warning: mask:rwx
>>> *** Warning: other:rwx
>>> *** Warning: default:user::rwx
>>> *** Warning: default:group::rwx
>>> *** Warning: default:other:r-x
>>> *** Warning:
>>> *** Warning: Please change the user and/or group ownership,
>>> *** Warning: permissions, or ACLs of /var/run.
>>> *** ERROR: Problem with /var/run directory. Exiting.
>>> I tried a lot, but cannot find any solution.
>>> Any hints?
>> It's telling you that the Administrators group is missing write access.
>> Do you have a root id on your system or are you using passwd and group
>> files?
> passwd/group files.
> root and admin entries:
> root:S-1-5-32-544:0:
> Administratoren:S-1-5-32-544:544:
>> You could either change group ownership from root to Administrators:
>>  $ chgrp -cR Administrators /var/run
>> and if your admin id is not faroul:
>>  $ chown -cR  /var/run
>> or, to add explicit Administrators group access, and default access to
>> files created, explicit admin id ACL and DACL, and others read and search:
>>  $ setfacl -m g:Administrators:rwx,d:g:Administrators:rwx,\
>> u::rwx,d:g::rwx,o::r-x /var/run
>> add Administrators and admin id to existing files:
>>  $ setfacl -m g:Administrators:rwx,u::rwx,\
>> o::r-x /var/run/*
> Nothing helps... (German Windows, "Administratoren" is "Administrators")
> *** Warning: The owner and the Administrators need
> *** Warning: to have .w. permission to /var/run.
> *** Warning: Here are the current permissions and ACLS:
> *** Warning: drwxrwxrwt+ 1 Administratoren root 0 May 25 21:07 /var/run
> *** Warning: # file: /var/run
> *** Warning: # owner: Administratoren
> *** Warning: # group: root
> *** Warning: # flags: --t
> *** Warning: user::rwx
> *** Warning: user:Administratoren:rwx
> *** Warning: group::rwx
> *** Warning: group:SYSTEM:rwx
> *** Warning: mask:rwx
> *** Warning: other:rwx
> *** Warning: default:user::rwx
> *** Warning: default:user:Administratoren:rwx
> *** Warning: default:group::rwx
> *** Warning: default:mask:rwx
> *** Warning: default:other:r-x
> *** Warning:
> *** Warning: Please change the user and/or group ownership,
> *** Warning: permissions, or ACLs of /var/run.
> *** ERROR: Problem with /var/run directory. Exiting.
> /var> la
> total 18
> drwxr-xr-x+ 1 faroul  None   0 May 25 21:17 ./
> drwxr-xr-x+ 1 faroul  None   0 May 19 20:15 ../
> drwxr-xr-x+ 1 faroul  None   0 May 18 23:21 cache/
> drwxr-xr-x+ 1 cyg_server  root   0 May 18 23:25 empty/
> drwxr-xr-x+ 1 faroul  None   0 May 18 23:21 lib/
> drwxrwxrwt+ 1 faroul  None   0 May 19 21:40 log/
> drwxrwxrwt+ 1 Administratoren root   0 May 25 21:07 run/

I would expect the group owner to be Administratoren not root and the
user owner of run to be faroul or root:
# ls -dl /var/{run,empty}/
drwxr-xr-x+ 1 cyg_server Administrators 0 Nov 19  2013 /var/empty/
drwxrwxrwt+ 1 userid Administrators 0 May 23 19:01 /var/run/

except on my system actually /var/run -> ../run, as on Linux, and don't
have any problems - I have a bunch of Linux-compatible symlinks all
over, including to Windows directories for homes and other non-Cygwin
stuff, and other similar customizations to make working with Windows
from Cygwin easier, with no problems.

You might want to try:
# chgrp Administratoren /var/{empty,run}
# chown root /var/run
or compare your old and current directories:
# ls -dl {/proc/cygdrive/c/cygwin32,}/var/{empty,run}
and reset security by reference to your old directories:
# chown --reference {/proc/cygdrive/c/cygwin32,}/var/empty
# chgrp --reference {/proc/cygdrive/c/cygwin32,}/var/empty
# chmod --reference {/proc/cygdrive/c/cygwin32,}/var/empty
# chown --reference {/proc/cygdrive/c/cygwin32,}/var/run
# chgrp --reference {/proc/cygdrive/c/cygwin32,}/var/run
# chmod --reference {/proc/cygdrive/c/cygwin32,}/var/run

Ensure your /etc/passwd and /etc/group files 

Installing sshd on W7 reveals errors in CSIH_SCRIPT -- patch file

[Houder]

Hi,

For those of you who like to look at a patch file, the patch
file should have been attached to this post.

Henri--- orig/cygwin-service-installation-helper.sh   2015-10-28 10:23:49.0 +0100
+++ new/cygwin-service-installation-helper.sh   2017-05-26 21:43:04.308202700 +0200
@@ -2566,7 +2566,7 @@
 #
 # Otherwise, we need the files.
 #
-#   Returns 0 if files shall be used, 1 otherwise.
+#   Returns 1 if files shall be used, 0 otherwise.
 # ==
 csih_use_file_etc()
 {
@@ -3003,6 +3003,12 @@
  csih_inform "the '${csih_PRIVILEGED_USERNAME}' account."
  echo ""

+  # If we use /etc account DB only, write new account to /etc/passwd
+  if csih_use_file_etc passwd
+  then
+/usr/bin/mkpasswd -l -u "${csih_PRIVILEGED_USERNAME}" >> "${SYSCONFDIR}/passwd"
+  fi
+
  if ! passwd -e "${csih_PRIVILEGED_USERNAME}" >/dev/null
  then
csih_warning "Setting password expiry for user '${csih_PRIVILEGED_USERNAME}' failed!"
@@ -3063,12 +3069,6 @@
 fi
   fi

-  # If we use /etc account DB only, write new account to /etc/passwd
-  if csih_use_file_etc passwd
-  then
-   /usr/bin/mkpasswd -l -u "${username}" >> "${SYSCONFDIR}/passwd"
-  fi
-
   return "${ret}"
 fi # ! username_in_sam
 return 1 # failed to create user (or prevented by auto-answer veto)

--
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

Re: setup release candidate - please test

[Peter A. Castro]

On Fri, 26 May 2017, Jon Turney wrote:


Date: Fri, 26 May 2017 18:25:17 +0100
Subject: Re: setup release candidate - please test

On 26/05/2017 16:01, Ian Lambert via cygwin wrote:

On Fri, 5/26/17, Jon Turney <> wrote:
  Subject: Re: setup release candidate - please test
  Date: Friday, May 26, 2017, 8:05 AM

  > Can you give an example of a setup command
  line containing an invalid
  > option
  which "quietly does nothing" rather than reporting
  an error?

The example above, when started from a desktop icon,
in windos 7 enterprise.


Ah, maybe I have misunderstood what you meant: I thought you meant the 
invalid option is silently ignored, but you meant that when started like 
that, an invalid option causes setup to silently do nothing.


That's because the error is being written to a non-existent console. 
Unfortunately, knowing if we've been started from a terminal or not to report 
the error appropriately is a bit of a problem.


It's been a while since I did real Win32 programming, but I seem to recall 
there were some indirect ways of determining if you had a Console 
environment, like calling GetConsoleTitle() and if it returns an error 
then you don't have a console.  Or maybe GetStdHandle() ?


If you detemine you don't have a Console, then create a pop-up dialog box 
showing the error with a dummy OK button?


I'd bet Corinna would have this kind of knowledge at her fingertips. :)

[snip]

--
--=> Peter A. Castro
Email: doctor at fruitbat dot org / Peter dot Castro at oracle dot com
"Cats are just autistic Dogs" -- Dr. Tony Attwood

--
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

Installing sshd on W7 reveals errors in CSIH_SCRIPT

[Houder]

Hi,

Installing sshd on W7 reveals errors in CSIH_SCRIPT ...

CSIH_SCRIPT = /usr/share/csih/cygwin-service-installation-helper.sh

Just now I installed the sshd daemon on my W7 (64-bits Cygwin); I am 
still

using /etc/{passwd,group} as the "database" (i.e. NOT Windows SAM).

Invocation of /usr/bin/ssh-host-config (in an elevated shell) 
genenerated

the following TWO warnings:

  = 1st warning =
passwd: unknown user cyg_server
*** Warning: Setting password expiry for user 'cyg_server' failed!
*** Warning: Please check that password never expires or set it to your 
needs.

  = 2nd warning =
*** Warning: Expected privileged user 'cyg_server' does not exist.
*** Warning: Defaulting to 'SYSTEM' <= no what I had in mind!

-

ssh-host-config sources CSIH-SCRIPT

The function if interest in ssh-host-config is: install_service()

install_service() # skeleton of function as executed in my case
  csih_create_privileged_user
  csih_service_should_run_as

# ==
# Action!
# ==
... lot of statements
install_service || let warning_cnt+=$? # almost at bottom of file

-

So the functions of interest in CSIH-SCRIPT are:

 - csih_create_privileged_user
 - csih_service_should_run_as

Near the bottom of csih_create_privileged_use(), "cyg_server" (the 
privileged
user) is ADDED to /etc/passwd ... too late and using the wrong 
statement.


Too late, because the privileged user ("cyg_server") should already have 
been

added near the beginning of this function ...

 - that is why the 1st warning is issued (from 
csih_create_privileged_user() )
 - and because of the wrong statement, "cyg_server" is NOT added to 
/etc/passwd


The 2nd warning is generated from csih_service_should_run_as() for the 
same

reason ("cyg_server" missing from /etc/passwd).
As a side-effect, the sshd service will be created using the "SYSTEM" 
account

i.s.o. "cyg_server" account -- not what was intended!

BTW, the comment at the top of csih_use_file_etc() is WRONG: it should 
read:


# ==
# Routine: csih_use_file_etc passwd|group
...
#   Returns 1 if files shall be used, 0 otherwise.
# ==

Regards,

Henri

=
= Skeleton of both functions as executed in my case
=

1.
csih_create_privileged_user() # in case user cyg_server must be created

 # privileged user ("cyg_server") already present?
  csih_privileged_account_exists "$csih_PRIVILEGED_USERNAME"

  # No, it is NOT! Create user ...
  csih_call_winsys32 net user "${csih_PRIVILEGED_USERWINNAME}"

  # make the passwd of the privileged user never expire ...
  if ! passwd -e "${csih_PRIVILEGED_USERNAME}"
  then
   ... WARNING: Setting password expiry for user "cyg_server" failed!
  fi

# Hold on, has user already been added to /etc/passwd (if files is 
preferred

# as the "database")? No, the user has NOT been added yet!
=> This is why Henri gets his 1st warning ...
=> ... and why he HAD to add user "cyg_server" to /etc/passwd
=> ... and has to change the service
   (no, not the "SYSTEM" account, but the "cyg_server" account!)

... a lot more statements

# TOO LATE and using the WRONG variable name!
  # add cyg_server to /etc/passwd ... if and only if  files are used as 
database

  if csih_use_file_etc passwd # yes, Henri uses files as the "database"
  then
# HUH?
/usr/bin/mkpasswd -l -u "${username}" >> "${SYSCONFDIR}/passwd"
# I believe the statement should have read: i.e. WRONG variable used
/usr/bin/mkpasswd -l -u "${{csih_PRIVILEGED_USERNAME}" >> 
"${SYSCONFDIR}/passwd"

  fi

2.
csih_service_should_run_as()

... a lot of statements

  if csih_privileged_account_exists "$csih_PRIVILEGED_USERNAME" 1>&2
  then
# it already existed before this script was launched (comment by 
Corinna)

echo "$csih_PRIVILEGED_USERNAME"
return
  elif /usr/bin/getent passwd "${csih_PRIVILEGED_USERNAME}"
  then
... ok
  else
... Warning: Expected privileged user "cyg_server" does not exist
echo "SYSTEM" # meaning service will use the SYSTEM account (and not 
the

  # cyg_server account) -- which is NOT was intended!
  fi

=

--
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

Re: setup release candidate - please test

[Jon Turney]

On 26/05/2017 16:01, Ian Lambert via cygwin wrote:

On Fri, 5/26/17, Jon Turney <> wrote:
  Subject: Re: setup release candidate - please test
  To: "The Cygwin Mailing List" 
  Cc: "Ian Lambert" <>
  Date: Friday, May 26, 2017, 8:05 AM




  > Can you give an example of a setup command
  line containing an invalid
  > option
  which "quietly does nothing" rather than reporting
  an error?

The example above, when started from a desktop icon,
in windos 7 enterprise.


Ah, maybe I have misunderstood what you meant: I thought you meant the 
invalid option is silently ignored, but you meant that when started like 
that, an invalid option causes setup to silently do nothing.


That's because the error is being written to a non-existent console. 
Unfortunately, knowing if we've been started from a terminal or not to 
report the error appropriately is a bit of a problem.



Depending on the results of the tests suggested with wget, I

  may
  >> consider changing or removing
  the user-agent reported by cygwin setup,
  >> or providing such an option.
  >
  > This snapshot adds a
  --user-agent option, which allows the user agent
  > string to be specified.
  >
  > https://cygwin.com/setup/setup-2.878-8-gee3cea.x86.exe
  > https://cygwin.com/setup/setup-2.878-8-gee3cea.x86_64.exe
  

Ping?
  
  > Could you let me know if this helps, or if

  you've given up, so I know
  what to do
  with these patches?
  

Sorry, I missed seeing this before. The suggestion of testing
combinations of wget, curl and lynx with a few different user agents
was more than I had time for then, but I haven't given up.

I tried the above setup 3 ways. It doesn't help.
With Firefox user agent and proxy entered
With iE user agent and proxy entered


These haven't changed so you don't need to test them.


With iE user agent and use iE settings selected

Setup does not ask for username and password.
Wget needs those and gets them from .wgetrc or .bashrc.


Oh well, thanks for testing.


2017/05/26 10:27:15 HTTP status 403 fetching http://cygwin.com/mirrors.lst


setup doesn't ask for username/password because it doesn't get a "407 
Proxy Authorization Required" response, just a "403 Forbidden".




--
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

Re: Clueless! sshd ONLY fails at system startup (XP/SP3) -- FOLLOWUP

[Houder]

On Fri, 26 May 2017 10:40:20, cyg Simple wrote:
> On 5/26/2017 4:17 AM, Houder wrote:
> 
> Are you positive your XP system, even though beyond EOSL didn't get auto
> updated because of RANSOMEWARE upgrades[1][2]?  Perhaps this was the
> source of your problems.

I applied the patch myself ... (and I do not believe that the patch was the
cause of the problem - given the fact, that the problem disappeared after I
had UNinstalled the F-Secure *)

Henri

> [1]
> https://www.theverge.com/2017/5/13/15635006/microsoft-windows-xp-security-patch-wannacry-ransomware-attack
> [2]
> https://redmondmag.com/articles/2017/05/15/microsoft-releases-windows-ransomware-patch.aspx


--
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

Re: setup release candidate - please test

[Ian Lambert via cygwin]

On Fri, 5/26/17, Jon Turney <> wrote:
 Subject: Re: setup release candidate - please test
 To: "The Cygwin Mailing List" 
 Cc: "Ian Lambert" <>
 Date: Friday, May 26, 2017, 8:05 AM
 
 On 17/05/2017 20:38, Jon Turney
 wrote:
 > On 16/05/2017 15:06, Jon Turney wrote:
 >> I don't know why unrecognized
 options aren't fatal errors.
 > 
 > So, I might have been misled by my low
 opinion of setup here:
 > 
 >> $ ./setup-x86_64
 --user-agent=anything
 >>
 >> Error during option processing.
 > [...]
 

Apparently there is a difference in response when running 
setup from a desktop icon versus command line.
You were not misled. Another detail is I am also using
--no-admin (but that doesn't seem to matter in this case).



 > Can you give an example of a setup command
 line containing an invalid 
 > option
 which "quietly does nothing" rather than reporting
 an error?

The example above, when started from a desktop icon,
in windos 7 enterprise.


> Depending on the results of the tests suggested with wget, I
 may
 >> consider changing or removing
 the user-agent reported by cygwin setup,
 >> or providing such an option.
 > 
 > This snapshot adds a
 --user-agent option, which allows the user agent 
 > string to be specified.
 > 
 > https://cygwin.com/setup/setup-2.878-8-gee3cea.x86.exe
 > https://cygwin.com/setup/setup-2.878-8-gee3cea.x86_64.exe
 
> Ping?
 
 > Could you let me know if this helps, or if
 you've given up, so I know 
 what to do
 with these patches?
 

Sorry, I missed seeing this before. The suggestion of testing 
combinations of wget, curl and lynx with a few different user agents
was more than I had time for then, but I haven't given up.

I tried the above setup 3 ways. It doesn't help. 
With Firefox user agent and proxy entered
With iE user agent and proxy entered
With iE user agent and use iE settings selected

Setup does not ask for username and password.
Wget needs those and gets them from .wgetrc or .bashrc.

Logs are below. The first 2 are very similar. 3rd is a little different.
I also re-verified wget still works with the same 2 user agents (or no user 
agent).


$ cat setup.log.full-proxy-ff-ua ; echo ; cat setup.log.full-proxy-ie-ua ; echo 
; cat setup.log.full-iesettings-ie-ua 
2017/05/26 10:23:15 Starting cygwin install, version 2.878-8-gee3cea
2017/05/26 10:23:15 User has NO backup/restore rights
2017/05/26 10:23:15 Current Directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:23:15 Could not open Service control manager
2017/05/26 10:23:22 source: network install
2017/05/26 10:23:25 root: E:\cygwin64-3 user
2017/05/26 10:23:27 Selected local directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:23:30 net: Proxy
Cached mirror list unavailable
Defaulting to empty mirror list
2017/05/26 10:23:32 site: http://mirrors.kernel.org/sourceware/cygwin/
2017/05/26 10:23:32 mbox note: Unable to get setup from 

INSTALLED.DB version 3
2017/05/26 10:23:36 Ending cygwin install

2017/05/26 10:25:28 Starting cygwin install, version 2.878-8-gee3cea
2017/05/26 10:25:28 User has NO backup/restore rights
2017/05/26 10:25:28 Current Directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:25:28 Could not open Service control manager
2017/05/26 10:25:31 source: network install
2017/05/26 10:25:32 root: E:\cygwin64-3 user
2017/05/26 10:25:33 Selected local directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:25:39 net: Proxy
Cached mirror list unavailable
Defaulting to empty mirror list
2017/05/26 10:25:40 site: http://mirrors.kernel.org/sourceware/cygwin/
2017/05/26 10:25:40 mbox note: Unable to get setup from 

INSTALLED.DB version 3
2017/05/26 10:25:43 Ending cygwin install

2017/05/26 10:27:07 Starting cygwin install, version 2.878-8-gee3cea
2017/05/26 10:27:07 User has NO backup/restore rights
2017/05/26 10:27:07 Current Directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:27:07 Could not open Service control manager
2017/05/26 10:27:10 source: network install
2017/05/26 10:27:11 root: E:\cygwin64-3 user
2017/05/26 10:27:12 Selected local directory: 
E:\cygwin64-mirror\ftwin\mirrors.kernel.org\sourceware\cygwin
2017/05/26 10:27:15 net: IE5
Cached mirror list unavailable
2017/05/26 10:27:15 HTTP status 403 fetching http://cygwin.com/mirrors.lst
Defaulting to empty mirror list
2017/05/26 10:27:16 site: http://mirrors.kernel.org/sourceware/cygwin/
2017/05/26 10:27:16 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz.sig
2017/05/26 10:27:16 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.xz
2017/05/26 10:27:16 HTTP status 403 fetching 
http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.bz2.sig
2017/05/26 10:27:16 HTTP status 403 fetching 

Re: Clueless! sshd ONLY fails at system startup (XP/SP3) -- FOLLOWUP

[cyg Simple]

On 5/26/2017 4:17 AM, Houder wrote:

Are you positive your XP system, even though beyond EOSL didn't get auto
updated because of RANSOMEWARE upgrades[1][2]?  Perhaps this was the
source of your problems.

[1]
https://www.theverge.com/2017/5/13/15635006/microsoft-windows-xp-security-patch-wannacry-ransomware-attack
[2]
https://redmondmag.com/articles/2017/05/15/microsoft-releases-windows-ransomware-patch.aspx

-- 
cyg Simple

--
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

Re: Haxe package

[Jon Turney]

On 26/05/2017 03:03, Andy Li wrote:

I've revised according to all the comments in github.
Is there any other thing you would like to adjust?


This fails to build for me, the first error is:

make: *** No rule to make target 'libs/ilib/il.cmxa', needed by 
'src/context/common.cmx'.  Stop.


I wonder if I'm missing some build-dep?
cygport 0.24.1 

PF = haxe-3.4.2-1
S = /pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe
B = /pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build
D = /pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/inst
C = /pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe/CYGWIN-PATCHES
T = /pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/temp
CBUILD = x86_64-pc-cygwin
CHOST = x86_64-pc-cygwin
CTARGET = x86_64-pc-cygwin
CC = gcc
CFLAGS = -ggdb -O2 -pipe -Wimplicit-function-declaration 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build=/usr/src/debug/haxe-3.4.2-1
 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe=/usr/src/debug/haxe-3.4.2-1
CPPFLAGS =
CXX = g++
CXXFLAGS = -ggdb -O2 -pipe 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build=/usr/src/debug/haxe-3.4.2-1
 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe=/usr/src/debug/haxe-3.4.2-1
F77 = gfortran
FFLAGS = -ggdb -O2 -pipe 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build=/usr/src/debug/haxe-3.4.2-1
 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe=/usr/src/debug/haxe-3.4.2-1
FC = gfortran
FCFLAGS = -ggdb -O2 -pipe 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build=/usr/src/debug/haxe-3.4.2-1
 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe=/usr/src/debug/haxe-3.4.2-1
GOC = gccgo
GOFLAGS = -ggdb -O2 -pipe 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build=/usr/src/debug/haxe-3.4.2-1
 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe=/usr/src/debug/haxe-3.4.2-1
OBJC = gcc
OBJCFLAGS = -ggdb -O2 -pipe -Wimplicit-function-declaration 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build=/usr/src/debug/haxe-3.4.2-1
 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe=/usr/src/debug/haxe-3.4.2-1
OBJCXX = g++
OBJCXXFLAGS = -ggdb -O2 -pipe 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build=/usr/src/debug/haxe-3.4.2-1
 
-fdebug-prefix-map=/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/src/haxe=/usr/src/debug/haxe-3.4.2-1
LDFLAGS =
LIBS =
MAKEOPTS = -f Makefile.win


make -C libs/extlib OCAMLOPT=ocamlopt.opt OCAMLC=ocamlc native
ocamlopt.opt -bin-annot -g -w -3 -I libs/extlib -I libs/extc -I libs/neko -I 
libs/javalib -I libs/ziplib -I libs/swflib -I libs/xml-light -I libs/ttflib -I 
libs/ilib -I libs/objsize -I libs/pcre -I src -I src/context -I src/generators 
-I src/macro -I src/optimization -I src/syntax -I src/typing -I src/display -c 
src/json.ml
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
make[1]: Entering directory 
'/pkg/haxe-cygwin/haxe-3.4.2-1.x86_64/build/libs/extlib'
ocamlopt.opt -g -a -o extLib.cmxa enum.mli bitSet.mli dynArray.mli extArray.mli 
extHashtbl.mli extList.mli extString.mli global.mli rbuffer.mli IO.mli 
option.mli pMap.mli std.mli uChar.mli uTF8.mli base64.mli unzip.mli refList.mli 
optParse.mli dllist.mli multiArray.mli sMap.mli enum.ml bitSet.ml dynArray.ml 
extArray.ml extHashtbl.ml extList.ml extString.ml global.ml rbuffer.ml IO.ml 
option.ml pMap.ml std.ml uChar.ml uTF8.ml base64.ml unzip.ml refList.ml 
optParse.ml dllist.ml multiArray.ml sMap.ml extLib.ml
File "extString.mli", line 177, characters 1-100:
Warning 3: deprecated: [@@noalloc] should be used instead of "noalloc"
File "extString.mli", line 178, characters 1-91:
Warning 3: deprecated: [@@noalloc] should be used instead of "noalloc"
File "bitSet.ml", line 23, characters 40-53:
Warning 3: deprecated: String.create
Use Bytes.create instead.
File "bitSet.ml", line 28, characters 64-75:
Warning 3: deprecated: String.fill
Use Bytes.fill instead.
make -f Makefile.version_extra -s --no-print-directory ADD_REVISION=0 
BRANCH=master COMMIT_SHA=4170c14 COMMIT_DATE=20170516065120 > src/version.ml
ocamllex src/syntax/lexer.mll
make: *** No rule to make target 'libs/ilib/il.cmxa', needed by 
'src/context/common.cmx'.  Stop.
make: *** Waiting for unfinished jobs
ocamlopt.opt -bin-annot -g -w -3 -I libs/extlib -I libs/extc -I libs/neko -I 
libs/javalib -I libs/ziplib -I libs/swflib -I libs/xml-light -I libs/ttflib -I 
libs/ilib -I libs/objsize -I libs/pcre -I src -I src/context -I src/generators 
-I src/macro -I src/optimization -I src/syntax -I src/typing -I src/display -c 
src/version.ml
151 states, 1504 transitions, table size 6922 bytes
File "extString.ml", line 28, characters 9-15:
Warning 3: deprecated: create
Use Bytes.create instead.
File "extString.ml", line 30, characters 2-12:
Warning 3: deprecated: unsafe_set
File "extString.ml", line 111, characters 2-8:
Warning 3: deprecated: create
Use Bytes.create instead.
File "extString.ml", line 158, characters 9-15:
Warning 3: deprecated: create

Re: setup release candidate - please test

[Jon Turney]

On 17/05/2017 20:38, Jon Turney wrote:

On 16/05/2017 15:06, Jon Turney wrote:

I don't know why unrecognized options aren't fatal errors.


So, I might have been misled by my low opinion of setup here:


$ ./setup-x86_64 --user-agent=anything

Error during option processing.

[...]

Can you give an example of a setup command line containing an invalid 
option which "quietly does nothing" rather than reporting an error?



Depending on the results of the tests suggested with wget, I may
consider changing or removing the user-agent reported by cygwin setup,
or providing such an option.


This snapshot adds a --user-agent option, which allows the user agent 
string to be specified.


https://cygwin.com/setup/setup-2.878-8-gee3cea.x86.exe
https://cygwin.com/setup/setup-2.878-8-gee3cea.x86_64.exe


Ping?

Could you let me know if this helps, or if you've given up, so I know 
what to do with these patches?


--
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

Re: bug in lrint [was: FW: Printing long int in C program under cygwin64]

[Erik Bray]

On Wed, May 24, 2017 at 6:57 PM, Eric Blake wrote:
> On 05/24/2017 11:53 AM, Erik Bray wrote:
>
 dropping down to assembly; it could very well be that the assembly code
 is incorrectly truncating things at 32 bits (where it is just fine for
 32-bit Cygwin, but wrong for 64-bit):

 long lrint (double x)
 {
   long retval = 0L;
 #if defined(_AMD64_) || defined(__x86_64__) || defined(_X86_) ||
 defined(__i386__)
   __asm__ __volatile__ ("fistpl %0"  : "=m" (retval) : "t" (x) : "st");
>
>> Actually, I take it back.  gdb/objdump (and presumably binutils in
>> general) was being deceptive to me about the nature of that mov
>> instruction.  And in fact the fistpl should be fistpq.  That fixes it.
>
> Is fistpq right on 32-bit, or is this a case where we need different
> assembly for 32-bit (fistpl) vs. 64-bit (fistql) to match the size of
> long that we are converting to?

Right.  I didn't read that pre-processer line past the first couple
defines.  Really this should be fistpq on 64-bit and fistpl on 32-bit.
And if llrint has the same bug then it should be fixed there too.

The discussion about printf format specifiers is orthogonal to this.
I can submit a patch for l(l)rint if you'd like.

Erik

--
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

Re: Clueless! sshd ONLY fails at system startup (XP/SP3) -- FOLLOWUP

[Houder]

On 2017-05-26 09:51, Brian Inglis wrote:

[snip]
Now I wonder if I will find the same result on W7 when I install 
openssh.

(yes, W7 also has F-Secure anti-virus installed).
Anyone using F-Secure on W7 and operating the sshd?


For Win7 MS Defender, MS Security Essentials (MSE - free MS download),
and Windows Firewall were not BLODAs for me, all others were, but you
still have to open up required ports in routers, Firewall, and any
security products, and/or enable apps to receive. It can be a pain.

Does F-n-Secure have firewall or port block features - many have?
Allow port 22 in (or your selection, and from selected hosts or
networks, if it can be limited).


Hi Brian,

Thanks for the info.

... yes, I know how to "clear" the firewall-hurdle :-)

F-Secure SAFE (anti-virus):

I got "F-Secure SAFE" from my provider; it is only anti-virus; that
is: no firewall ...

Some time ago it automatically upgraded itself ... and kept working.

After UNinstalling it (as I wrote in my previous post) I decided to
REinstall it (downloaded the executable from my provider).

After startup the executable tells me:

"your system (XP!) is no longer supported!"

Case closed ;-)

(I still have to verify W7 and openssh in combo with F-Secure)

Henri

--
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

Re: libgpuarray installation

[Brian Inglis]

On 2017-05-26 02:05, Muath AL-ALi wrote:
>  I  have this problem(0 [main] make 5136 find_fast_cwd: WARNING:
> Couldn't compute FAST_CWD pointer.)  make: *** No targets specified
> and no makefile found.  Stop. )

That is a problem fixed long ago: you need to upgrade your Cygwin
installation, as documented on the web site.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

Re: [cygwin] v1.7

[Brian Inglis]

On 2017-05-25 23:00, Jason Pyeron wrote:
> Cygwin is open source, red hat has a paid support option.

RH has not offered Cygwin Support for some time, although they will
continue to support it for those who have active, previously purchased,
Cygwin Support paid subscriptions.
See https://access.redhat.com/solutions/78783

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

libgpuarray installation

[Muath AL-ALi]

  hi,
 I  have this problem(0 [main] make 5136 find_fast_cwd: WARNING:
Couldn't compute FAST_CWD pointer.)  make: *** No targets specified
and no makefile found.  Stop. )

-- 
Best regards,

Muath Al Ali

--
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

Re: Clueless! sshd ONLY fails at system startup (XP/SP3) -- FOLLOWUP

[Brian Inglis]

On 2017-05-26 00:23, Houder wrote:
> On 2017-05-25 23:21, Houder wrote:
>> On 2017-05-25 17:36, Houder wrote:
>>> YES, I know, XP is NOT supported anymore ... However, I started
>>> out on XP ... and it has sshd running as a Window service,
>>> installed and configured (as approved by Corinna :-)
>>> ... some time ago I may have upgraded openssh over there (yes, I
>>> am now running W7) ... I cannot really remember. Yes, sometimes I
>>> visit (ssh) the "old station" (XP) for info that I am missing.
>>> (both machines are behind a firewall - rest assured)
>>> "Suddenly" (yesterday?) I noticed that the "sshd daemon" fails;
>>> it is started at system startup (i.e. an automatic service).
>> Ahem ... it should have rephrased that ... however, from the error
>> report in the sshd.log, it should be clear that the daemon fails as
>> soon as it receives its first "ssh" request ... (and not before).
> Give me a break!
> Just now I decided to UNinstall the F-Secure anti-virus ...
> And guess what ...? Yes, NOW sshd replies again to requests after system
> startup!
> Now I wonder if I will find the same result on W7 when I install openssh.
> (yes, W7 also has F-Secure anti-virus installed).
> Anyone using F-Secure on W7 and operating the sshd?

For Win7 MS Defender, MS Security Essentials (MSE - free MS download),
and Windows Firewall were not BLODAs for me, all others were, but you
still have to open up required ports in routers, Firewall, and any
security products, and/or enable apps to receive. It can be a pain.

Does F-n-Secure have firewall or port block features - many have?
Allow port 22 in (or your selection, and from selected hosts or
networks, if it can be limited).

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

Re: Problems with ssh-host-config and /var/run directory

[Brian Inglis]

On 2017-05-25 15:36, Brian Inglis wrote:
> On 2017-05-25 13:24, Henning Peters wrote:
>> I switched from 32bit to 64bit a week ago, moved "cygwin" to 
>> "cygwin32" and reinstalled from scratch into a new "cygwin"
>> directory.
>> when trying to setup sshd using ssh-host-config, I get this message
>> when using StrictModes (which I want to and did before on cygwin32
>> on this system):
>> *** Warning: The owner and the Administrators need
>> *** Warning: to have .w. permission to /var/run.
>> *** Warning: Here are the current permissions and ACLS:
>> *** Warning: drwxrwxrwt+ 1 faroul root 0 May 19 20:56 /var/run
>> *** Warning: # file: /var/run
>> *** Warning: # owner: faroul
>> *** Warning: # group: root
>> *** Warning: # flags: --t
>> *** Warning: user::rwx
>> *** Warning: group::rwx
>> *** Warning: group:root:rwx
>> *** Warning: group:SYSTEM:rwx
>> *** Warning: mask:rwx
>> *** Warning: other:rwx
>> *** Warning: default:user::rwx
>> *** Warning: default:group::rwx
>> *** Warning: default:other:r-x
>> *** Warning:
>> *** Warning: Please change the user and/or group ownership,
>> *** Warning: permissions, or ACLs of /var/run.
>> *** ERROR: Problem with /var/run directory. Exiting.
>> I tried a lot, but cannot find any solution.
>> Any hints?
> 
> It's telling you that the Administrators group is missing write
> access.
> 
> Do you have a root id on your system or are you using passwd and
> group files?
> 
> You could either change group ownership from root to Administrators:
>   $ chgrp -cR Administrators /var/run
> 
> and if your admin id is not faroul:
>   $ chown -cR  /var/run
> 
> or, to add explicit Administrators group access, and default access 
> to files created, explicit admin id ACL and DACL, and others read
> and search:
>   $ setfacl -m g:Administrators:rwx,d:g:Administrators:rwx,\
> u::rwx,d:g::rwx,o::r-x /var/run

Typos:
$ setfacl -m g:Administrators:rwx,d:g:Administrators:rwx,\
u::rwx,d:u::rwx,o::r-x /var/run

> add Administrators and admin id to existing files:
>   $ setfacl -m g:Administrators:rwx,u::rwx,\
> o::r-x /var/run/*

$ setfacl -m g:Administrators:rw-,u::rw-,\
o::r-- /var/run/*

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

Clueless! sshd ONLY fails at system startup (XP/SP3) -- FOLLOWUP

[Houder]

On 2017-05-25 23:21, Houder wrote:

On 2017-05-25 17:36, Houder wrote:

Hi,

YES, I know, XP is NOT supported anymore ... However, I started
out on XP ... and it has sshd running as a Window service,

installed and configured (as approved by Corinna :-)

... some time ago I may have upgraded openssh over there (yes, I
am now running W7) ... I cannot really remember. Yes, sometimes I
visit (ssh) the "old station" (XP) for info that I am missing.

(both machines are behind a firewall - rest assured)

"Suddenly" (yesterday?) I noticed that the "sshd daemon" fails;
it is started at system startup (i.e. an automatic service).


Ahem ... it should have rephrased that ... however, from the error
report in the sshd.log, it should be clear that the daemon fails as
soon as it receives its first "ssh" request ... (and not before).


Give me a break!

Just now I decided to UNinstall the F-Secure anti-virus ...

And guess what ...? Yes, NOW sshd replies again to requests after system
startup!

Now I wonder if I will find the same result on W7 when I install 
openssh.

(yes, W7 also has F-Secure anti-virus installed).

Anyone using F-Secure on W7 and operating the sshd?

Henri

--
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