Re: BUG: ssh-host-config --yes fails with cygwin 1.7.33
On Wed, Nov 05 2014, Corinna Vinschen wrote:
On Nov 5 14:04, Corinna Vinschen wrote:
On Nov 5 10:11, Corinna Vinschen wrote:
On Nov 4 19:48, Florian Friesdorf wrote:
This is fixed with cygwin-1.7.33-0.4.
However, the warning in the beginning still remains.
Please discuss stuff like this on the cygwin AT cygwin DOT com mailing
list. cygwin-apps is a mailing list for maintainers only. Thank you.
Having said that, yeah, this warning is fallout from the fact that the
csih helper script used by ssh-host-config is exclusively working with
/etc/passwd and /etc/group files [...etc...]
No, it's not. This is in fact from ssh-host-config which still
checks for groups in /etc/group. I had already tweaked the script
but apparently forgotten this one.
I attached a new ssh-host-config to this mail for testing. Please
give it a try.
No, use this one instead. I used a simpler method to list the groups.
The warning is still displayed despite mintty being run as
administrator. It now lists more groups,:
*** Warning: Running this script typically requires administrator privileges!
*** Warning: However, it seems your account does not have these privileges.
*** Warning: Here's the list of groups in your user token:
None
Local account and member of Administrators group
root
Users
REMOTE INTERACTIVE LOGON
INTERACTIVE
Authenticated Users
This Organization
Local account
CurrentSession
LOCAL
NTLM Authentication
High Mandatory Level
*** Warning: This usually means you're running this script from a non-admin
*** Warning: desktop session, or in a non-elevated shell under UAC control.
*** Warning: Make sure you have the appropriate privileges right now,
*** Warning: otherwise parts of this script will probably fail!
It still tests for id 544, which seems to have changed to 545:
# Make sure the user is running in an administrative context
admin=$(/usr/bin/id -G | /usr/bin/grep -Eq '\544\' echo yes || echo no)
if [ ${admin} != yes ]
$ id -G
197121 11 66048 66049 4 15 545 4095 0 405504
I double checked, this is with cygwin 1.7.33-0.4
Florian
--
Florian Friesdorf f...@chaoflow.net
GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
Jabber/XMPP: f...@chaoflow.net
IRC: chaoflow on freenode,ircnet,blafasel,OFTC
pgpcRAnLzFx8X.pgp
Description: PGP signature
PATCH: ssh-host-config and cygserver-config: configureable service name (was: Re: PATCH: ssh-host-config support setting service name)
On Tue, Nov 04 2014, Florian Friesdorf wrote:
On Tue, Nov 04 2014, Achim Gratz wrote:
Shouldn't $service_name default to sshd perhaps so that invocations
without the new switch continue to work?
Good point - will send an updated patch.
Updated version defaulting to old value for service name and using
non-colliding -N.
And along the same lines a patch for cygserver-config.
As I started this on cygwin-apps, I'm replying here, but will use
cygwin@ in the future.
From f230cc5a1eeb6919e8ee7450ac7b1980d1fde5c5 Mon Sep 17 00:00:00 2001
From: Florian Friesdorf f...@chaoflow.net
Date: Wed, 5 Nov 2014 13:48:02 +0100
Subject: [PATCH 1/2] ssh-host-config: configurable sshd service name
---
bootstrap-development-cygwin/skel/bin/ssh-host-config | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/bootstrap-development-cygwin/skel/bin/ssh-host-config b/bootstrap-development-cygwin/skel/bin/ssh-host-config
index a7ea3e0..adeaa80 100755
--- a/bootstrap-development-cygwin/skel/bin/ssh-host-config
+++ b/bootstrap-development-cygwin/skel/bin/ssh-host-config
@@ -61,6 +61,7 @@ LOCALSTATEDIR=/var
sshd_config_configured=no
port_number=22
+service_name=sshd
strictmodes=yes
privsep_used=yes
cygwin_value=
@@ -410,7 +411,7 @@ install_service() {
local ret=0
echo
- if /usr/bin/cygrunsrv -Q sshd /dev/null 21
+ if /usr/bin/cygrunsrv -Q ${service_name} /dev/null 21
then
csih_inform Sshd service is already installed.
check_service_files_ownership || let ret+=$?
@@ -466,7 +467,7 @@ install_service() {
fi
if [ -z ${password} ]
then
- if /usr/bin/cygrunsrv -I sshd -d CYGWIN sshd -p /usr/sbin/sshd \
+ if /usr/bin/cygrunsrv -I ${service_name} -d CYGWIN ${service_name} -p /usr/sbin/sshd \
-a -D -y tcpip ${cygwin_env[@]}
then
echo
@@ -476,20 +477,20 @@ install_service() {
csih_inform will start automatically after the next reboot.
fi
else
- if /usr/bin/cygrunsrv -I sshd -d CYGWIN sshd -p /usr/sbin/sshd \
+ if /usr/bin/cygrunsrv -I ${service_name} -d CYGWIN ${service_name} -p /usr/sbin/sshd \
-a -D -y tcpip ${cygwin_env[@]} \
-u ${run_service_as} -w ${password}
then
/usr/bin/editrights -u ${run_service_as} -a SeServiceLogonRight
echo
csih_inform The sshd service has been installed under the '${run_service_as}'
- csih_inform account. To start the service now, call \`net start sshd' or
- csih_inform \`cygrunsrv -S sshd'. Otherwise, it will start automatically
+ csih_inform account. To start the service now, call \`net start ${service_name}' or
+ csih_inform \`cygrunsrv -S ${service_name}'. Otherwise, it will start automatically
csih_inform after the next reboot.
fi
fi
- if /usr/bin/cygrunsrv -Q sshd /dev/null 21
+ if /usr/bin/cygrunsrv -Q ${service_name} /dev/null 21
then
check_service_files_ownership ${run_service_as} || let ret+=$?
else
@@ -563,6 +564,11 @@ do
shift
;;
+ -N | --name )
+service_name=$1
+shift
+;;
+
-p | --port )
port_number=$1
shift
@@ -592,6 +598,7 @@ do
echo --yes-yAnswer all questions with \yes\ automatically.
echo --no -nAnswer all questions with \no\ automatically.
echo --cygwin -c options Use \options\ as value for CYGWIN environment var.
+echo --name -N name sshd windows service name.
echo --port -p nsshd listens on port n.
echo --user -u account privileged user for service, default 'cyg_server'.
echo --pwd-w passwd Use \pwd\ as password for privileged user.
--
2.1.1
From cada6fb8631d44fd7fc509fa71cd4b44ebcf6327 Mon Sep 17 00:00:00 2001
From: Florian Friesdorf f...@chaoflow.net
Date: Wed, 5 Nov 2014 13:54:28 +0100
Subject: [PATCH 2/2] cygserver-config: configurable cygserver service name
---
bootstrap-development-cygwin/skel/bin/cygserver-config | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/bootstrap-development-cygwin/skel/bin/cygserver-config b/bootstrap-development-cygwin/skel/bin/cygserver-config
index b8f441c..abe943c 100755
--- a/bootstrap-development-cygwin/skel/bin/cygserver-config
+++ b/bootstrap-development-cygwin/skel/bin/cygserver-config
@@ -10,6 +10,7 @@ LOCALSTATEDIR=/var
progname=$0
auto_answer=
+service_name=cygserver
request()
{
@@ -63,6 +64,11 @@ do
auto_answer=no
;;
+ -N | --name )
+service_name=$1
+shift
+;;
+
*)
echo usage: ${progname} [OPTION]...
echo
@@ -72,6 +78,7 @@ do
echo --debug -dEnable shell's debug output.
echo --yes-yAnswer all questions with \yes\ automatically.
echo --no -nAnswer all questions with \no\ automatically.
+echo --name -N name cygserver windows service name.
echo
exit 1
;;
@@ -84,10 +91,10 @@ _sys=`uname`
_nt=`expr ${_sys} : CYGWIN_NT`
#
Re: PATCH: ssh-host-config and cygserver-config: configureable service name (was: Re: PATCH: ssh-host-config support setting service name)
On Nov 6 13:38, Florian Friesdorf wrote: On Tue, Nov 04 2014, Florian Friesdorf wrote: On Tue, Nov 04 2014, Achim Gratz wrote: Shouldn't $service_name default to sshd perhaps so that invocations without the new switch continue to work? Good point - will send an updated patch. Updated version defaulting to old value for service name and using non-colliding -N. I have just a patch in the loop upstream, but this is a neat extension, so I'll send a new patch upstream with your changes as well. Thanks. And along the same lines a patch for cygserver-config. Neat. Patch applied. Btw., this is a rather small patch, so I applied it under the trivial patch rule. As for more complex patches against sources from the Cygwin repo, please note that we'd need a copyright assignment from you. See https://cygwin.com/contrib.html Thanks again, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpqWBAHvb7WC.pgp Description: PGP signature
Re: BUG: ssh-host-config --yes fails with cygwin 1.7.33
On Nov 6 13:33, Florian Friesdorf wrote: On Wed, Nov 05 2014, Corinna Vinschen wrote: On Nov 5 14:04, Corinna Vinschen wrote: On Nov 5 10:11, Corinna Vinschen wrote: On Nov 4 19:48, Florian Friesdorf wrote: This is fixed with cygwin-1.7.33-0.4. However, the warning in the beginning still remains. Please discuss stuff like this on the cygwin AT cygwin DOT com mailing list. cygwin-apps is a mailing list for maintainers only. Thank you. Having said that, yeah, this warning is fallout from the fact that the csih helper script used by ssh-host-config is exclusively working with /etc/passwd and /etc/group files [...etc...] No, it's not. This is in fact from ssh-host-config which still checks for groups in /etc/group. I had already tweaked the script but apparently forgotten this one. I attached a new ssh-host-config to this mail for testing. Please give it a try. No, use this one instead. I used a simpler method to list the groups. The warning is still displayed despite mintty being run as administrator. It now lists more groups,: [...] It still tests for id 544, which seems to have changed to 545: No, it changed to 0, due to the root entry in /etc/group. I suggest to remove this. It doesn't make sense anyway. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp0HknbNfwAG.pgp Description: PGP signature
src/winsup/cygwin ChangeLog dcrt0.cc external. ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-11-06 15:32:21 Modified files: winsup/cygwin : ChangeLog dcrt0.cc external.cc winsup/cygwin/include/cygwin: version.h winsup/cygwin/include/sys: cygwin.h winsup/cygwin/lib: atexit.c Log message: * dcrt0.cc (cygwin_atexit): Change preceeding comment to reflect API version numbers. * external.cc (cygwin_internal): disable setting cxx_malloc on 64 bit. Add CW_FIXED_ATEXIT case. * include/cygwin/version.h (CYGWIN_VERSION_API_MINOR): Bump. * include/sys/cygwin.h (cygwin_getinfo_types): Add CW_FIXED_ATEXIT. * lib/atexit.c (atexit): Test running Cygwin version by checking return value of cygwin_internal (CW_FIXED_ATEXIT). Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.6565r2=1.6566 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dcrt0.cc.diff?cvsroot=srcr1=1.464r2=1.465 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/external.cc.diff?cvsroot=srcr1=1.139r2=1.140 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/cygwin/version.h.diff?cvsroot=srcr1=1.410r2=1.411 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/sys/cygwin.h.diff?cvsroot=srcr1=1.109r2=1.110 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/lib/atexit.c.diff?cvsroot=srcr1=1.2r2=1.3
src/winsup/cygserver ChangeLog cygserver-config
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-11-06 16:36:43 Modified files: winsup/cygserver: ChangeLog cygserver-config Log message: * cygserver-config: Add -N option to allow different service name. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygserver/ChangeLog.diff?cvsroot=srcr1=1.107r2=1.108 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygserver/cygserver-config.diff?cvsroot=srcr1=1.4r2=1.5
Re: [ANNOUNCEMENT] Updated: gcc-4.9.2-1 (x86/x86_64) (Test)
On 11/6/2014 07:21, David Stacey wrote: On 03/11/2014 22:08, JonY wrote: gcc-4.9.2-1 has been uploaded for 32bit and 64bit Cygwin. This version is set to test. I've just noticed that gcc-java requires libgcj15. Given that libgcj15 is part of the test release, should the dependency be libgcj14? Dave. Right, I should just make it depend on both, they shouldn't clash. signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCEMENT] Updated: gcc-4.9.2-1 (x86/x86_64) (Test)
On 11/6/2014 07:21, David Stacey wrote: On 03/11/2014 22:08, JonY wrote: gcc-4.9.2-1 has been uploaded for 32bit and 64bit Cygwin. This version is set to test. I've just noticed that gcc-java requires libgcj15. Given that libgcj15 is part of the test release, should the dependency be libgcj14? Dave. Right, I should just make it depend on both, they shouldn't clash. signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCEMENT] Updated: gcc-4.9.2-1 (x86/x86_64) (Test)
On 11/6/2014 10:12 AM, JonY wrote: On 11/6/2014 07:21, David Stacey wrote: On 03/11/2014 22:08, JonY wrote: gcc-4.9.2-1 has been uploaded for 32bit and 64bit Cygwin. This version is set to test. I've just noticed that gcc-java requires libgcj15. Given that libgcj15 is part of the test release, should the dependency be libgcj14? Dave. Right, I should just make it depend on both, they shouldn't clash. check again spurious Python3 dependency, I saw one from gcc-java Regards Marco -- 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
Latest Cygwin Mercurial verson still uses SSL3
Hello Cygwin, Mercurial is a version control system. Mercurial version 3.2 removes the SSL3 POODLE vulnerability [1]. However, the latest cygwin installer (downloaded today, 6 Nov 2014) says the current version number of Mercurial is 3.0.1-1. Mercurial repositories that have disabled SSL3 can no longer be accessed using Cygwin. Therefore, this is a Cygwin-specific issue. Are there plans to port Mercurial 3.2 to Cygwin? [1] http://mercurial.selenic.com/wiki/UpgradeNotes -- Best regards, Chris Lilley, Technical Director, W3C Interaction Domain -- 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: [ANNOUNCEMENT] Updated: gcc-4.9.2-1 (x86/x86_64) (Test)
On 11/6/2014 20:11, Marco Atzeri wrote: On 11/6/2014 10:12 AM, JonY wrote: On 11/6/2014 07:21, David Stacey wrote: On 03/11/2014 22:08, JonY wrote: gcc-4.9.2-1 has been uploaded for 32bit and 64bit Cygwin. This version is set to test. I've just noticed that gcc-java requires libgcj15. Given that libgcj15 is part of the test release, should the dependency be libgcj14? Dave. Right, I should just make it depend on both, they shouldn't clash. check again spurious Python3 dependency, I saw one from gcc-java Done, removed. signature.asc Description: OpenPGP digital signature
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
I haven't tried Cygwin 1.7.33 yet. What would be the expectation of
sidHistory working? In the past, I've had a script to read extra SIDs
out of AD and merge them into passwd.
On Wed, Nov 5, 2014 at 11:43 AM, Corinna Vinschen
corinna-cyg...@cygwin.com wrote:
Hi Cygwin friends and users,
I just released a 6th TEST version of the next upcoming Cygwin release,
1.7.33-0.6.
Changes compared to the former test version 1.7.33-0.5:
- The 1.7.33-0.5 version introduced a dependency to a symbol (__dso_handle)
provided only by GCC versions starting with GCC 4.8.3-3. This results
in being unable to link executables with GCC 4.8.3-2 and earlier.
Cygwin 1.7.33-0.6 introduces a fix for this situation by providing its
own default symbol __dso_handle.
If you want to help testing this new release (which I seriously hope
for), you can find it in your setup-x86.exe or setup-x86_64.exe as
test release.
The major change in this new release is the new method to read account
(passwd and group) information from the Windows user databases directly,
without the requirement to generate /etc/passwd and /etc/group files to
generate Unix-like uid and gid.
For your convenience I wrote new documentation. Since this is a TEST
prerelease, the new documentation is not part of the official docs yet.
Rather have a look at
https://cygwin.com/preliminary-ntsec.html
If you read it
(which I seriously hope for) and it's all just incomprehensible
gobbledygook to you, please say so on the mailing list
cygwin AT cygwin DOT com
so we have a chance to improve the documentation.
Please give this TEST release a try.
If you find problems in the new features or regressions compared to the
current stable release 1.7.32, please report them to the public mailing
list
cygwin AT cygwin DOT com
Following is a list of changes in this new release:
What's new:
---
- Cygwin can now generate passwd/group entries directly from Windows
user databases (local SAM or Active Directory), thus allowing to run
Cygwin without having to create /etc/passwd and /etc/group files.
Introduce /etc/nsswitch.conf file to configure passwd/group handling.
For bordercase which require to use /etc/passwd and /etc/group files,
change mkpasswd/mkgroup to generate passwd/group entries compatible
with the entries read from SAM/AD.
- Add -b/--remove-all option to setfacl to reduce the ACL to only the
entries representing POSIX permission bits.
- /proc/cygdrive is a new symlink pointing to the current cygdrive prefix.
This can be utilized in scripts to access paths via cygdrive prefix, even
if the cygdrive prefix has been changed by the user.
- /proc/partitions now prints the windows mount points the device is mounted
on. This allows to recognize the underlying Windows devices of the Cygwin
raw device names.
- New API: quotactl, designed after the Linux/BSD function, but severely
restricted: Windows only supports user block quotas on NTFS, no group
quotas, no inode quotas, no time constraints.
- New APIs: ffsl, ffsll (glibc extensions).
- New API: stime (SVr4).
- Provide Cygwin documentation (PDFs and HTML) for offline usage in
/usr/share/doc/cygwin-${version}.
What changed:
-
- New internal exception handling based on SEH on 64 bit Cygwin.
- Revamp Solaris ACL implementation to more closely work like POSIX ACLs
are supposed to work. Finally implement a CLASS_OBJ emulation. Update
getfacl(1)/setfacl(1) accordingly.
- When exec'ing applications, check if $PATH exists and is non-empty. If not,
add PATH variable with Cygwin installation directory as content to Windows
environment to allow loading of Cygwin system DLLs.
- Disable CYGWIN dosfilewarning option by default.
- Improve various header files for C++- and standards-compliance.
- Doug Lea malloc implementation update from 2.8.3 to the latest 2.8.6.
- The xdr functions are no longer exported for newly built executables.
Use libtirpc-devel instead.
- atexit is now exported as statically linked function from libcygwin.a.
This allows reliable access to the DSO handle of the caller for newly
built executables. The former atexit entry point into the DLL remains
for backward compatibility only.
Bug Fixes
-
- Per POSIX, dirfd(3) now returns EINVAL rather than EBADF on invalid
directory stream.
- Fix a resource leak in rmdir(2).
- Fix fchmod(2)/fchown(2)/fsetxattr(2) in case the file got renamed after
open and before calling one of the affected functions.
Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00517.html
- Handle Netapp-specific problem in statvfs(2)/fstatvfs(2).
Addresses: https://cygwin.com/ml/cygwin/2014-06/msg00425.html
- Fix chown(2) on ptys in a corner case.
- Generate correct error when a path is inaccessible due to missing
permissions.
Addresses:
Re: zlib-1.2.8-2 breaks clamav
On 11/01/2014 08:31 PM, Mike Bonnet wrote: Hi. I just found out that the zlib-1.2.8-2 breaks clamav. A log of the output of the sigtool commmand from clamav is attached. It's using gzread() to read the compressed signature databases, and the format of the data returned has apparently changed between zlib 1.2.8-1 and 1.2.8-2. This should be fixed ASAP. Who would I talk to about getting this fixed? Thanks, Mike -- 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 -- 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
[ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.7
Hi Cygwin friends and users,
I just released a 7th TEST version of the next upcoming Cygwin release,
1.7.33-0.7.
Changes compared to the former test version 1.7.33-0.6:
- The new atexit implementation needed a test so that DLLs built against
this new atexit would still work on Cygwin 1.7.32.
This is a backward compatibility thingy only. Please don't build
your DLLs against libcygwin.a from 1.7.33-0.6. Use libcygwin.a from
1.7.33-0.7 instead.
If you don't build applications or DLLs with Cygwin, you can safely
ignore this change.
If you want to help testing this new release (which I seriously hope
for), you can find it in your setup-x86.exe or setup-x86_64.exe as
test release.
The major change in this new release is the new method to read account
(passwd and group) information from the Windows user databases directly,
without the requirement to generate /etc/passwd and /etc/group files to
generate Unix-like uid and gid.
For your convenience I wrote new documentation. Since this is a TEST
prerelease, the new documentation is not part of the official docs yet.
Rather have a look at
https://cygwin.com/preliminary-ntsec.html
If you read it
(which I seriously hope for) and it's all just incomprehensible
gobbledygook to you, please say so on the mailing list
cygwin AT cygwin DOT com
so we have a chance to improve the documentation.
Please give this TEST release a try.
If you find problems in the new features or regressions compared to the
current stable release 1.7.32, please report them to the public mailing
list
cygwin AT cygwin DOT com
Following is a list of changes in this new release:
What's new:
---
- Cygwin can now generate passwd/group entries directly from Windows
user databases (local SAM or Active Directory), thus allowing to run
Cygwin without having to create /etc/passwd and /etc/group files.
Introduce /etc/nsswitch.conf file to configure passwd/group handling.
For bordercase which require to use /etc/passwd and /etc/group files,
change mkpasswd/mkgroup to generate passwd/group entries compatible
with the entries read from SAM/AD.
- Add -b/--remove-all option to setfacl to reduce the ACL to only the
entries representing POSIX permission bits.
- /proc/cygdrive is a new symlink pointing to the current cygdrive prefix.
This can be utilized in scripts to access paths via cygdrive prefix, even
if the cygdrive prefix has been changed by the user.
- /proc/partitions now prints the windows mount points the device is mounted
on. This allows to recognize the underlying Windows devices of the Cygwin
raw device names.
- New API: quotactl, designed after the Linux/BSD function, but severely
restricted: Windows only supports user block quotas on NTFS, no group
quotas, no inode quotas, no time constraints.
- New APIs: ffsl, ffsll (glibc extensions).
- New API: stime (SVr4).
- Provide Cygwin documentation (PDFs and HTML) for offline usage in
/usr/share/doc/cygwin-${version}.
What changed:
-
- New internal exception handling based on SEH on 64 bit Cygwin.
- Revamp Solaris ACL implementation to more closely work like POSIX ACLs
are supposed to work. Finally implement a CLASS_OBJ emulation. Update
getfacl(1)/setfacl(1) accordingly.
- When exec'ing applications, check if $PATH exists and is non-empty. If not,
add PATH variable with Cygwin installation directory as content to Windows
environment to allow loading of Cygwin system DLLs.
- Disable CYGWIN dosfilewarning option by default.
- Improve various header files for C++- and standards-compliance.
- Doug Lea malloc implementation update from 2.8.3 to the latest 2.8.6.
- The xdr functions are no longer exported for newly built executables.
Use libtirpc-devel instead.
- atexit is now exported as statically linked function from libcygwin.a.
This allows reliable access to the DSO handle of the caller for newly
built executables. The former atexit entry point into the DLL remains
for backward compatibility only.
Bug Fixes
-
- Per POSIX, dirfd(3) now returns EINVAL rather than EBADF on invalid
directory stream.
- Fix a resource leak in rmdir(2).
- Fix fchmod(2)/fchown(2)/fsetxattr(2) in case the file got renamed after
open and before calling one of the affected functions.
Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00517.html
- Handle Netapp-specific problem in statvfs(2)/fstatvfs(2).
Addresses: https://cygwin.com/ml/cygwin/2014-06/msg00425.html
- Fix chown(2) on ptys in a corner case.
- Generate correct error when a path is inaccessible due to missing permissions.
Addresses: https://cygwin.com/ml/cygwin-developers/2014-10/msg00010.html
- Don't hang in accept calls if socket is no listener. Set errno to EINVAL
instead.
- Don't allow seeking on serial lines and sockets. Set errno to ESPIPE
instead.
Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00319.html
- Fix output of /proc/PID/statm.
- Fix a
Re: zlib-1.2.8-2 breaks clamav
On Thu, Nov 6, 2014 at 4:35 PM, Mike Bonnet wrote: On 11/01/2014 08:31 PM, Mike Bonnet wrote: Hi. I just found out that the zlib-1.2.8-2 breaks clamav. A log of the output of the sigtool commmand from clamav is attached. It's using gzread() to read the compressed signature databases, and the format of the data returned has apparently changed between zlib 1.2.8-1 and 1.2.8-2. This should be fixed ASAP. Who would I talk to about getting this fixed? I think the Cygwin zlib maintainer, because the difference between -1 and -2 is just a Cygwin-specific repackaging. Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds People disagree with me. I just ignore them. -- Linus Torvalds -- 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: zlib-1.2.8-2 breaks clamav
On 11/6/2014 4:35 PM, Mike Bonnet wrote: On 11/01/2014 08:31 PM, Mike Bonnet wrote: Hi. I just found out that the zlib-1.2.8-2 breaks clamav. A log of the output of the sigtool commmand from clamav is attached. It's using gzread() to read the compressed signature databases, and the format of the data returned has apparently changed between zlib 1.2.8-1 and 1.2.8-2. This should be fixed ASAP. Who would I talk to about getting this fixed? Thanks, Mike This is the place. The zlib package maintainer follow the mailing list. Have you tested if reinstalling previous zlib-1.2.8-1 restore the expected behaviour ? Marco -- 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: BLODA Addition
On Nov 5 13:43, Bryan Berns wrote: Random is this case is receiving a permission denied message from the shell when launching an executable. When repeatably running a test case, we see an error one every 15 minutes on average. Without it installed, no error occurs. I'll see what might be good registry key to query -- not sitting at a computer with it installed right now. Thanks. I was thinking about debugging the underlying issue that's causing this from a cygwin perspective. Would this be advisable or is this behavior just a fundamental consequence of how cygwin interacts with Windows? Permission denied points to the software opening the executable for exclusive access during some check at process startup. This is bad behaviour and should be banished from planet earth. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpxcz7BkA9uH.pgp Description: PGP signature
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
On Nov 6 07:39, Christian Franke wrote: Corinna Vinschen wrote: Hi Cygwin friends and users, I just released a 6th TEST version of the next upcoming Cygwin release, 1.7.33-0.6. Looks good so far. An observation from my first test on a machine which is member of a domain: mkpasswd -l and -L always print the HOST prefix. mkpasswd -d and -D never print the DOMAIN prefix Right. That's by design. -D is deprecated. -L of the new mkpasswd/ mkgroup (which hopefully are not used by users a lot in future) only prefix *foreign* machines. Otherwise the naming rules of the underlying Cygwin SAM/AD naming rules are strictly followed so that a defaultt passwd or group file will be identical to the output generated by the db mechanism[1]. This likely would break creation of local 'technical' user accounts in existing *-config scripts (possibly including the csih script): The csih scrip needs a thorough kick anyway. I'm working on and off on that, but it's not easy due to a couple of very ingrained assumptions not valid anymore. I hope to get a new csih working next week. Now on my wishlist: an nsswitch.conf option to change the 'print prefix' behavior for machines in a domain. I disabled this deliberately[1]. Corinna [1] Reproducability of the passwd/group genearation rules... rulez :) -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpwEVyE6zl4R.pgp Description: PGP signature
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
[please, don't https://cygwin.com/acronyms/#TOFU. Thanks] On Nov 6 09:26, Bryan Berns wrote: I haven't tried Cygwin 1.7.33 yet. What would be the expectation of sidHistory working? In the past, I've had a script to read extra SIDs out of AD and merge them into passwd. Stop using passwd and group files. All accounts available from your DC are available to Cygwin. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpaylYWP9y_7.pgp Description: PGP signature
Re: FW: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.5
On Nov 5 22:38, Habermann, David (D) wrote: I just released a 5th TEST version of the next upcoming Cygwin release, 1.7.33-0.5. Ever since using this 1.7.33-0.x series (currently running 1.7.33-0.5) I've been having intermittent trouble with one of my scripts, and just finally got around to digging further today. This is an expect script It would appear, after a bit more digging, that this problem is related to some timeout issues. Most of the time the ssh login goes rapidly, but occasionally it takes quite a lot longer triggering the expect default timeout. When setting the timeout substantially longer, the reliability goes up substantially. Such phases wher checking for an account takes a bit longer just happen. I don't see that Cygwin has this really under control. Local caching should alleviate this somewhat. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpN8UZQ73Ryt.pgp Description: PGP signature
Re: rsyncd broken
On 8/22/2014 6:17 PM, Yaakov Selkowitz wrote: On 2014-08-22 07:42, Frank Fesevur wrote: Jari, As I reported earlier rsync 3.1.0 is broken on cygwin. http://www.cygwin.com/ml/cygwin/2014-06/msg00212.html http://www.cygwin.com/ml/cygwin/2014-06/msg00442.html Any news on that issue yet? I have marked 3.0.9-1 as curr: and 3.1.0-1 as test: due to the issues reported. Yaakov Jary, any news ? Marco -- 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: FW: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.5
On Nov 5 22:38, Habermann, David (D) wrote: It would appear, after a bit more digging, that this problem is related to some timeout issues. Most of the time the ssh login goes rapidly, but occasionally it takes quite a lot longer triggering the expect default timeout. When setting the timeout substantially longer, the reliability goes up substantially. Such phases wher checking for an account takes a bit longer just happen. I don't see that Cygwin has this really under control. Local caching should alleviate this somewhat. Seems that this is not taken care of by caching...I have cygserver running first, prior to anything else, and what I was finding was that the problem was intermittent, 20 rapid-fire tries would result in 2-3 random failures.
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
Corinna Vinschen wrote: On Nov 6 07:39, Christian Franke wrote: Corinna Vinschen wrote: Hi Cygwin friends and users, I just released a 6th TEST version of the next upcoming Cygwin release, 1.7.33-0.6. Looks good so far. An observation from my first test on a machine which is member of a domain: mkpasswd -l and -L always print the HOST prefix. mkpasswd -d and -D never print the DOMAIN prefix Right. That's by design. -D is deprecated. -L of the new mkpasswd/ mkgroup (which hopefully are not used by users a lot in future) only prefix *foreign* machines. But why does mkpasswd -l (no host) -- adds a prefix mkpasswd -l THISHOST -- does not add a prefix when the machine is in a domain? Not consistent, IMO. Is it because without a HOST it directly calls cygwin_internal() instead of Win API and -l/L distinction is not checked then? Otherwise the naming rules of the underlying Cygwin SAM/AD naming rules are strictly followed so that a defaultt passwd or group file will be identical to the output generated by the db mechanism[1]. This likely would break creation of local 'technical' user accounts in existing *-config scripts (possibly including the csih script): The csih scrip needs a thorough kick anyway. I'm working on and off on that, but it's not easy due to a couple of very ingrained assumptions not valid anymore. I hope to get a new csih working next week. But PLEASE keep the ability to create local users/groups without a prefix. Otherwise useful configuration defaults (mail_owner=postfix, ...) would be no longer useful because config files must be tweaked for each host (mail_owner=HOST+postfix, ...) for the sole purpose of[1]. Some of such technical users (sshd?) might also be hard coded or a config parser might not like the HOST+USER syntax. Christian [1] Reproducability of the passwd/group genearation rules... rulez :) -- 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: TEST RELEASE: Cygwin 1.7.33-0.7
On Thu, Nov 6, 2014 at 10:52 AM, Corinna Vinschen corinna-cyg...@cygwin.com wrote: Hi Cygwin friends and users, I just released a 7th TEST version of the next upcoming Cygwin release, 1.7.33-0.7. I discovered that /usr/bin/cron-config which is part of the cron package will need to be updated as it attempts to parse /etc/group . -- 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: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
On Nov 6 19:34, Christian Franke wrote: Corinna Vinschen wrote: On Nov 6 07:39, Christian Franke wrote: Corinna Vinschen wrote: Hi Cygwin friends and users, I just released a 6th TEST version of the next upcoming Cygwin release, 1.7.33-0.6. Looks good so far. An observation from my first test on a machine which is member of a domain: mkpasswd -l and -L always print the HOST prefix. mkpasswd -d and -D never print the DOMAIN prefix Right. That's by design. -D is deprecated. -L of the new mkpasswd/ mkgroup (which hopefully are not used by users a lot in future) only prefix *foreign* machines. But why does mkpasswd -l (no host) -- adds a prefix mkpasswd -l THISHOST -- does not add a prefix when the machine is in a domain? Not consistent, IMO. That's right. The reason is that the machine name is treated as a foreign machine. In theory, this should always generate names with prefixed machine name, but this is an entirely different code path in mkpasswd/mkgroup. I guess this should be fixed. I wouldn't be unhappy about help... Is it because without a HOST it directly calls cygwin_internal() instead of Win API and -l/L distinction is not checked then? Uh, yes. That's what I meant above :} Otherwise the naming rules of the underlying Cygwin SAM/AD naming rules are strictly followed so that a defaultt passwd or group file will be identical to the output generated by the db mechanism[1]. This likely would break creation of local 'technical' user accounts in existing *-config scripts (possibly including the csih script): The csih scrip needs a thorough kick anyway. I'm working on and off on that, but it's not easy due to a couple of very ingrained assumptions not valid anymore. I hope to get a new csih working next week. But PLEASE keep the ability to create local users/groups without a prefix. Otherwise useful configuration defaults (mail_owner=postfix, ...) would be no longer useful because config files must be tweaked for each host (mail_owner=HOST+postfix, ...) for the sole purpose of[1]. Some of such technical users (sshd?) might also be hard coded or a config parser might not like the HOST+USER syntax. And how's that supposed to work? Even if we introduce a way in /etc/nsswitch.conf to generate usernames differently, it doesn't really help. Your config file should be able to work with default settings and not force the admin to use specific settings in nsswitch.conf. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpO0KQKkQYox.pgp Description: PGP signature
Re: TEST RELEASE: Cygwin 1.7.33-0.7
On Nov 6 13:38, Kelley Cook wrote: On Thu, Nov 6, 2014 at 10:52 AM, Corinna Vinschen corinna-cyg...@cygwin.com wrote: Hi Cygwin friends and users, I just released a 7th TEST version of the next upcoming Cygwin release, 1.7.33-0.7. I discovered that /usr/bin/cron-config which is part of the cron package will need to be updated as it attempts to parse /etc/group . Right, it should use getent instead. Pierre? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpRP6bXdu6iB.pgp Description: PGP signature
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
On Nov 6 19:50, Corinna Vinschen wrote: On Nov 6 19:34, Christian Franke wrote: But PLEASE keep the ability to create local users/groups without a prefix. Otherwise useful configuration defaults (mail_owner=postfix, ...) would be no longer useful because config files must be tweaked for each host (mail_owner=HOST+postfix, ...) for the sole purpose of[1]. Some of such technical users (sshd?) might also be hard coded or a config parser might not like the HOST+USER syntax. And how's that supposed to work? Even if we introduce a way in /etc/nsswitch.conf to generate usernames differently, it doesn't really help. Your config file should be able to work with default settings and not force the admin to use specific settings in nsswitch.conf. Btw., sshd contains a patch to allow sshd as well as MACHINE+sshd as account name for the unprivileged privsep account. There's a new system call in Cygwin for that very purpose: #include sys/cygwin.h cygwin_internal (CW_CYGNAME_FROM_WINNAME, unprefixed-accountname, username_buffer, sizeof username_buffer); See the comment in external.cc, under the CW_CYGNAME_FROM_WINNAME case. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgptss2n8h_Tj.pgp Description: PGP signature
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
Corinna Vinschen wrote: On Nov 6 19:34, Christian Franke wrote: Corinna Vinschen wrote: On Nov 6 07:39, Christian Franke wrote: Corinna Vinschen wrote: Hi Cygwin friends and users, I just released a 6th TEST version of the next upcoming Cygwin release, 1.7.33-0.6. Looks good so far. An observation from my first test on a machine which is member of a domain: mkpasswd -l and -L always print the HOST prefix. mkpasswd -d and -D never print the DOMAIN prefix Right. That's by design. -D is deprecated. -L of the new mkpasswd/ mkgroup (which hopefully are not used by users a lot in future) only prefix *foreign* machines. But why does mkpasswd -l (no host) -- adds a prefix mkpasswd -l THISHOST -- does not add a prefix when the machine is in a domain? Not consistent, IMO. That's right. The reason is that the machine name is treated as a foreign machine. In theory, this should always generate names with prefixed machine name, but this is an entirely different code path in mkpasswd/mkgroup. I guess this should be fixed. I wouldn't be unhappy about help... I would only fix it back to the old behaviour (mkpasswd -l = no prefix), sorry :-) At my real job we run several build test machines which are members of a domain but use various local test user accounts (with no collision with domain users due to name space rules). Loosing the ability to use prefix-less local user names would break various existing test scripts (which are also used on Linux). Generated emails would have a from address with HOST+USER name part which might give interesting results if the mail system somehow interprets the NAME+EXTENSION address syntax... So there are use cases where prefix-less local user names are needed. This should be still supported, e.g. by mkpasswd -l, IMO. But PLEASE keep the ability to create local users/groups without a prefix. Otherwise useful configuration defaults (mail_owner=postfix, ...) would be no longer useful because config files must be tweaked for each host (mail_owner=HOST+postfix, ...) for the sole purpose of[1]. Some of such technical users (sshd?) might also be hard coded or a config parser might not like the HOST+USER syntax. And how's that supposed to work? Even if we introduce a way in /etc/nsswitch.conf to generate usernames differently, it doesn't really help. Your config file should be able to work with default settings and not force the admin to use specific settings in nsswitch.conf. The 'PLEASE keep ...' was only related to the new csih script. It should be able to optionally put prefix-less local usernames to /etc/passwd. Christian -- 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: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
Greetings, Christian Franke!
But why does
mkpasswd -l (no host) -- adds a prefix
mkpasswd -l THISHOST -- does not add a prefix
when the machine is in a domain? Not consistent, IMO.
That's right. The reason is that the machine name is treated as a
foreign machine. In theory, this should always generate names
with prefixed machine name, but this is an entirely different
code path in mkpasswd/mkgroup. I guess this should be fixed.
I wouldn't be unhappy about help...
I would only fix it back to the old behaviour (mkpasswd -l = no prefix),
sorry :-)
At my real job we run several build test machines which are members of
a domain but use various local test user accounts (with no collision
with domain users due to name space rules). Loosing the ability to use
prefix-less local user names would break various existing test scripts
(which are also used on Linux).
Did you actually tried running your scripts under new Cygwin DLL and see these
failures, or you're just theorizing here?
Generated emails would have a from address with HOST+USER name part
which might give interesting results if the mail system somehow
interprets the NAME+EXTENSION address syntax...
That's up to script. You can also fix it with a simple ${USER#${MACHINE}+}
macro.
So there are use cases where prefix-less local user names are needed.
This should be still supported, e.g. by mkpasswd -l, IMO.
If YOU need prefix-less local names, YOU create them.
But PLEASE keep the ability to create local users/groups without a prefix.
Otherwise useful configuration defaults (mail_owner=postfix, ...) would be
no longer useful because config files must be tweaked for each host
(mail_owner=HOST+postfix, ...) for the sole purpose of[1]. Some of such
technical users (sshd?) might also be hard coded or a config parser might
not like the HOST+USER syntax.
And how's that supposed to work? Even if we introduce a way in
/etc/nsswitch.conf to generate usernames differently, it doesn't really
help. Your config file should be able to work with default settings
and not force the admin to use specific settings in nsswitch.conf.
The 'PLEASE keep ...' was only related to the new csih script. It should
be able to optionally put prefix-less local usernames to /etc/passwd.
Not supposed to work that way, I'd say.
The whole aim of the change is to get rid of these fails, not to help users
create them.
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 06.11.2014, 22:59
Sorry for my terrible english...
--
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: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
On Nov 6 20:51, Christian Franke wrote: Corinna Vinschen wrote: On Nov 6 19:34, Christian Franke wrote: But why does mkpasswd -l (no host) -- adds a prefix mkpasswd -l THISHOST -- does not add a prefix when the machine is in a domain? Not consistent, IMO. That's right. The reason is that the machine name is treated as a foreign machine. In theory, this should always generate names with prefixed machine name, but this is an entirely different code path in mkpasswd/mkgroup. I guess this should be fixed. I wouldn't be unhappy about help... I would only fix it back to the old behaviour (mkpasswd -l = no prefix), sorry :-) At my real job we run several build test machines which are members of a domain but use various local test user accounts (with no collision with domain users due to name space rules). Loosing the ability to use prefix-less local user names would break various existing test scripts (which are also used on Linux). Generated emails would have a from address with HOST+USER name part which might give interesting results if the mail system somehow interprets the NAME+EXTENSION address syntax... So there are use cases where prefix-less local user names are needed. This should be still supported, e.g. by mkpasswd -l, IMO. But then... why not keep mkpasswd -L and use that instead? But PLEASE keep the ability to create local users/groups without a prefix. Otherwise useful configuration defaults (mail_owner=postfix, ...) would be no longer useful because config files must be tweaked for each host (mail_owner=HOST+postfix, ...) for the sole purpose of[1]. Some of such technical users (sshd?) might also be hard coded or a config parser might not like the HOST+USER syntax. And how's that supposed to work? Even if we introduce a way in /etc/nsswitch.conf to generate usernames differently, it doesn't really help. Your config file should be able to work with default settings and not force the admin to use specific settings in nsswitch.conf. The 'PLEASE keep ...' was only related to the new csih script. It should be able to optionally put prefix-less local usernames to /etc/passwd. PTC? As I wrote, I hope I have something ready next week, but the csih heler script is pretty complicated. I never expected having to maintain it :( Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpnperCgBFQS.pgp Description: PGP signature
gfortran 4.9.2-1
My own benchmarks work fine (gcc/g++ also). In John Campbell's test, among 5 run-time failures, there is (twice): Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for this error: 1 [main] profile_omp 5664 fixup_mmaps_after_fork: ReadProcessMemory failed for MAP_PRIVATE address 0x6FE5FC6, Win32 error 998 357 [main] profile_omp 5664 C:\users\tim\tim\tim\src\campbell\Profile_send_3 Nov14\profile_omp.exe: *** fatal error in forked process - recreate_mmaps_after_fork_failed 690131 [main] profile_omp 5664 cygwin_exception::open_stackdumpfile: Dumping stack trace to profile_omp.exe.stackdump 3 [main] profile_omp 4644 fork: child -1 - forked process 5664 died unexpectedly, retry 0, exit code 0x100, errno 11 28628 [main] profile_omp 4644 cygwin_exception::open_stackdumpfile: Dumping stack trace to profile_omp.exe.stackdump In spite of the remaining failures, it looks like progress. As I'm lazy, I'll continue using gcc-5.0 trunk builds unless there is interest (suggestion what should be done) in this one. I guess this 4.9.2-1 is more aggressive with build options than I've been able to make work. -- Tim Prince -- 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: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
On Nov 6 21:06, Corinna Vinschen wrote: On Nov 6 20:51, Christian Franke wrote: Corinna Vinschen wrote: On Nov 6 19:34, Christian Franke wrote: But why does mkpasswd -l (no host) -- adds a prefix mkpasswd -l THISHOST -- does not add a prefix when the machine is in a domain? Not consistent, IMO. That's right. The reason is that the machine name is treated as a foreign machine. In theory, this should always generate names with prefixed machine name, but this is an entirely different code path in mkpasswd/mkgroup. I guess this should be fixed. I wouldn't be unhappy about help... I would only fix it back to the old behaviour (mkpasswd -l = no prefix), sorry :-) At my real job we run several build test machines which are members of a domain but use various local test user accounts (with no collision with domain users due to name space rules). Loosing the ability to use prefix-less local user names would break various existing test scripts (which are also used on Linux). Generated emails would have a from address with HOST+USER name part which might give interesting results if the mail system somehow interprets the NAME+EXTENSION address syntax... So there are use cases where prefix-less local user names are needed. This should be still supported, e.g. by mkpasswd -l, IMO. But then... why not keep mkpasswd -L and use that instead? On second thought, it's completely wrong to allow printing local accounts from another machine without prefix. In theory there should be only one option -l [machine], which prints the local accounts of the current machine unprefixed (standalone machine) or prefixed (domain machine), and always prefixed for a foreign machine. The -L option can just go away. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp6jAAmBDgRp.pgp Description: PGP signature
Fwd: gcc-4.9.2-1 (x86_64) generates segfault during linking
Since I updated gcc from version 4.9.0-1 to 4.9.2-1, I obtain the error collect2: Fehler: ld mit Signal 11 [Segmentation fault] beendet when compiling and linking a C or C++ program. However, an executable is generated and appears to work as expected. I installed the latest test release of cygwin so far (1.7.33-0.7). Falk -- 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: TEST RELEASE: Cygwin 1.7.33-0.7
-Original Message- From: Corinna Vinschen Sent: Thursday, November 06, 2014 13:51 On Nov 6 13:38, Kelley Cook wrote: On Thu, Nov 6, 2014 at 10:52 AM, Corinna Vinschen wrote: Hi Cygwin friends and users, I just released a 7th TEST version of the next upcoming Cygwin release, 1.7.33-0.7. I discovered that /usr/bin/cron-config which is part of the cron package will need to be updated as it attempts to parse /etc/group . Right, it should use getent instead. Pierre? Right, and ditto for exim config and postinstall How much time do I have? Now cron-config checks if a username appears multiple times in passwd. Typically one instance is a domain id and the other one is a local id. That causes havoc with cron It happens fairly frequently; there was even such a bug report recently. How does getent handle that case? Is it detectable from a config file? Pierre -- 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: TEST RELEASE: Cygwin 1.7.33-0.7
On Nov 6 16:08, Pierre A. Humblet wrote: -Original Message- From: Corinna Vinschen Sent: Thursday, November 06, 2014 13:51 On Nov 6 13:38, Kelley Cook wrote: On Thu, Nov 6, 2014 at 10:52 AM, Corinna Vinschen wrote: Hi Cygwin friends and users, I just released a 7th TEST version of the next upcoming Cygwin release, 1.7.33-0.7. I discovered that /usr/bin/cron-config which is part of the cron package will need to be updated as it attempts to parse /etc/group . Right, it should use getent instead. Pierre? Right, and ditto for exim config and postinstall How much time do I have? Now cron-config checks if a username appears multiple times in passwd. Typically one instance is a domain id and the other one is a local id. That causes havoc with cron It happens fairly frequently; there was even such a bug report recently. How does getent handle that case? Is it detectable from a config file? Cygwin will only see the first one of these user names when reading from passwd, same for getent (or cron). I don't think config scripts have to handle every configuration error. On systems not using passwd and group files, this problem wouldn't occur for instance. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp74ac7WO6df.pgp Description: PGP signature
Re: Fwd: gcc-4.9.2-1 (x86_64) generates segfault during linking
On 11/7/2014 05:06, Falk Tannhäuser wrote: Since I updated gcc from version 4.9.0-1 to 4.9.2-1, I obtain the error collect2: Fehler: ld mit Signal 11 [Segmentation fault] beendet when compiling and linking a C or C++ program. However, an executable is generated and appears to work as expected. I installed the latest test release of cygwin so far (1.7.33-0.7). Falk Does it somehow work if you link with gcc -fno-lto? signature.asc Description: OpenPGP digital signature
Re: Fwd: gcc-4.9.2-1 (x86_64) generates segfault during linking
Am 06.11.2014 um 23:37 schrieb JonY: On 11/7/2014 05:06, Falk Tannhäuser wrote: Since I updated gcc from version 4.9.0-1 to 4.9.2-1, I obtain the error collect2: Fehler: ld mit Signal 11 [Segmentation fault] beendet when compiling and linking a C or C++ program. However, an executable is generated and appears to work as expected. I installed the latest test release of cygwin so far (1.7.33-0.7). Does it somehow work if you link with gcc -fno-lto? Yes, this fixes the problem. Falk -- 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: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.33-0.6
Corinna Vinschen wrote: On Nov 6 21:06, Corinna Vinschen wrote: On Nov 6 20:51, Christian Franke wrote: Corinna Vinschen wrote: On Nov 6 19:34, Christian Franke wrote: But why does mkpasswd -l (no host) -- adds a prefix mkpasswd -l THISHOST -- does not add a prefix when the machine is in a domain? Not consistent, IMO. That's right. The reason is that the machine name is treated as a foreign machine. In theory, this should always generate names with prefixed machine name, but this is an entirely different code path in mkpasswd/mkgroup. I guess this should be fixed. I wouldn't be unhappy about help... I would only fix it back to the old behaviour (mkpasswd -l = no prefix), sorry :-) At my real job we run several build test machines which are members of a domain but use various local test user accounts (with no collision with domain users due to name space rules). Loosing the ability to use prefix-less local user names would break various existing test scripts (which are also used on Linux). Generated emails would have a from address with HOST+USER name part which might give interesting results if the mail system somehow interprets the NAME+EXTENSION address syntax... So there are use cases where prefix-less local user names are needed. This should be still supported, e.g. by mkpasswd -l, IMO. But then... why not keep mkpasswd -L and use that instead? On second thought, it's completely wrong to allow printing local accounts from another machine without prefix. I agree. In theory there should be only one option -l [machine], which prints the local accounts of the current machine unprefixed (standalone machine) or prefixed (domain machine), and always prefixed for a foreign machine. The -L option can just go away. I disgree. Why not keep the old behavior of -l/-L for user names of current machine for those uses cases which rely on it? Those users who are happy with prefixed local user names and non-prefixed domain user names would simply no longer need to use mkpasswd (which is good). Package search shows 156 usr/bin/*-config scripts. How many of these use mkpasswd? BTW: None of my Linux machines have local user names with own HOSTNAME as prefix :-) Christian -- 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
[ANNOUNCEMENT] Updated: Cygwin 32-64 cross-toolchains
The following packages has been updated for the Cygwin x86 distribution: * cygwin64-1.7.32-1 * cygwin64-binutils-2.24.90-1 * cygwin64-clang-3.4.2-2 * cygwin64-default-manifest-6.4-1 * cygwin64-gcc-ada-4.8.3-4 * cygwin64-gcc-core-4.8.3-4 * cygwin64-gcc-fortran-4.8.3-4 * cygwin64-gcc-g++-4.8.3-4 * cygwin64-gcc-objc-4.8.3-4 * cygwin64-gcc-objc++-4.8.3-4 And for the x86_64 distribution: * cygwin32-1.7.32-1 * cygwin32-binutils-2.24.90-1 * cygwin32-clang-3.4.2-2 * cygwin32-default-manifest-6.4-1 * cygwin32-gcc-ada-4.8.3-4 * cygwin32-gcc-core-4.8.3-4 * cygwin32-gcc-fortran-4.8.3-4 * cygwin32-gcc-g++-4.8.3-4 * cygwin32-gcc-objc-4.8.3-4 * cygwin32-gcc-objc++-4.8.3-4 These toolchains allow cross-compiling 64-bit Cygwin software from 32-bit Cygwin and vice-versa. These releases are updates to match the native versions. -- Yaakov -- 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
[ANNOUNCEMENT] Updated: mysql-5.5.40-1
The following packages have been updated for the Cygwin distribution:
*** mysql-5.5.40-1
*** mysqld-5.5.40-1
*** mysql-test-5.5.40-1
*** libmysqlclient18-5.5.40-1
*** libmysqlclient-devel-5.5.40-1
*** libmysqld0-5.5.40-1
*** libmysqld-devel-5.5.40-1
MySQL Community Edition is a freely downloadable version of the world's
most popular open source database that is supported by an active
community of open source developers and enthusiasts.
Please note that the server ('mysqld' package) should be considered
*experimental*; for production use, I suggest using a native Windows
version from dev.mysql.com. Input from experienced MySQL server
administrators to improve this component would be welcome.
The client library and apps are stable, but when connecting to a native
Windows MySQL server on the same machine, you MUST use 127.0.0.1 as the
hostname; 'localhost' is reserved for connecting to the Cygwin mysqld
via a UNIX socket.
This is an update to the latest upstream 5.5 release, which includes
fixes for several security issues:
https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-40.html
--
Yaakov
--
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
[ANNOUNCEMENT] New: autogen-5.18.2-1
The following packages have been added to the Cygwin distribution: * autogen-5.18.2-1 * libopts25-5.18.2-1 * libopts-devel-5.18.2-1 AutoGen is a tool designed to simplify the creation and maintenance of programs that contain large amounts of repetitious text. It is especially valuable in programs that have several blocks of text that must be kept synchronized. AutoOpts is an option processing library based on AutoGen. -- Yaakov -- 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
TEST RELEASE: Cygwin 1.7.33-0.7
Hi Cygwin friends and users,
I just released a 7th TEST version of the next upcoming Cygwin release,
1.7.33-0.7.
Changes compared to the former test version 1.7.33-0.6:
- The new atexit implementation needed a test so that DLLs built against
this new atexit would still work on Cygwin 1.7.32.
This is a backward compatibility thingy only. Please don't build
your DLLs against libcygwin.a from 1.7.33-0.6. Use libcygwin.a from
1.7.33-0.7 instead.
If you don't build applications or DLLs with Cygwin, you can safely
ignore this change.
If you want to help testing this new release (which I seriously hope
for), you can find it in your setup-x86.exe or setup-x86_64.exe as
test release.
The major change in this new release is the new method to read account
(passwd and group) information from the Windows user databases directly,
without the requirement to generate /etc/passwd and /etc/group files to
generate Unix-like uid and gid.
For your convenience I wrote new documentation. Since this is a TEST
prerelease, the new documentation is not part of the official docs yet.
Rather have a look at
https://cygwin.com/preliminary-ntsec.html
If you read it
(which I seriously hope for) and it's all just incomprehensible
gobbledygook to you, please say so on the mailing list
cygwin AT cygwin DOT com
so we have a chance to improve the documentation.
Please give this TEST release a try.
If you find problems in the new features or regressions compared to the
current stable release 1.7.32, please report them to the public mailing
list
cygwin AT cygwin DOT com
Following is a list of changes in this new release:
What's new:
---
- Cygwin can now generate passwd/group entries directly from Windows
user databases (local SAM or Active Directory), thus allowing to run
Cygwin without having to create /etc/passwd and /etc/group files.
Introduce /etc/nsswitch.conf file to configure passwd/group handling.
For bordercase which require to use /etc/passwd and /etc/group files,
change mkpasswd/mkgroup to generate passwd/group entries compatible
with the entries read from SAM/AD.
- Add -b/--remove-all option to setfacl to reduce the ACL to only the
entries representing POSIX permission bits.
- /proc/cygdrive is a new symlink pointing to the current cygdrive prefix.
This can be utilized in scripts to access paths via cygdrive prefix, even
if the cygdrive prefix has been changed by the user.
- /proc/partitions now prints the windows mount points the device is mounted
on. This allows to recognize the underlying Windows devices of the Cygwin
raw device names.
- New API: quotactl, designed after the Linux/BSD function, but severely
restricted: Windows only supports user block quotas on NTFS, no group
quotas, no inode quotas, no time constraints.
- New APIs: ffsl, ffsll (glibc extensions).
- New API: stime (SVr4).
- Provide Cygwin documentation (PDFs and HTML) for offline usage in
/usr/share/doc/cygwin-${version}.
What changed:
-
- New internal exception handling based on SEH on 64 bit Cygwin.
- Revamp Solaris ACL implementation to more closely work like POSIX ACLs
are supposed to work. Finally implement a CLASS_OBJ emulation. Update
getfacl(1)/setfacl(1) accordingly.
- When exec'ing applications, check if $PATH exists and is non-empty. If not,
add PATH variable with Cygwin installation directory as content to Windows
environment to allow loading of Cygwin system DLLs.
- Disable CYGWIN dosfilewarning option by default.
- Improve various header files for C++- and standards-compliance.
- Doug Lea malloc implementation update from 2.8.3 to the latest 2.8.6.
- The xdr functions are no longer exported for newly built executables.
Use libtirpc-devel instead.
- atexit is now exported as statically linked function from libcygwin.a.
This allows reliable access to the DSO handle of the caller for newly
built executables. The former atexit entry point into the DLL remains
for backward compatibility only.
Bug Fixes
-
- Per POSIX, dirfd(3) now returns EINVAL rather than EBADF on invalid
directory stream.
- Fix a resource leak in rmdir(2).
- Fix fchmod(2)/fchown(2)/fsetxattr(2) in case the file got renamed after
open and before calling one of the affected functions.
Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00517.html
- Handle Netapp-specific problem in statvfs(2)/fstatvfs(2).
Addresses: https://cygwin.com/ml/cygwin/2014-06/msg00425.html
- Fix chown(2) on ptys in a corner case.
- Generate correct error when a path is inaccessible due to missing permissions.
Addresses: https://cygwin.com/ml/cygwin-developers/2014-10/msg00010.html
- Don't hang in accept calls if socket is no listener. Set errno to EINVAL
instead.
- Don't allow seeking on serial lines and sockets. Set errno to ESPIPE
instead.
Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00319.html
- Fix output of /proc/PID/statm.
- Fix a
Updated: Cygwin 32-64 cross-toolchains
The following packages has been updated for the Cygwin x86 distribution: * cygwin64-1.7.32-1 * cygwin64-binutils-2.24.90-1 * cygwin64-clang-3.4.2-2 * cygwin64-default-manifest-6.4-1 * cygwin64-gcc-ada-4.8.3-4 * cygwin64-gcc-core-4.8.3-4 * cygwin64-gcc-fortran-4.8.3-4 * cygwin64-gcc-g++-4.8.3-4 * cygwin64-gcc-objc-4.8.3-4 * cygwin64-gcc-objc++-4.8.3-4 And for the x86_64 distribution: * cygwin32-1.7.32-1 * cygwin32-binutils-2.24.90-1 * cygwin32-clang-3.4.2-2 * cygwin32-default-manifest-6.4-1 * cygwin32-gcc-ada-4.8.3-4 * cygwin32-gcc-core-4.8.3-4 * cygwin32-gcc-fortran-4.8.3-4 * cygwin32-gcc-g++-4.8.3-4 * cygwin32-gcc-objc-4.8.3-4 * cygwin32-gcc-objc++-4.8.3-4 These toolchains allow cross-compiling 64-bit Cygwin software from 32-bit Cygwin and vice-versa. These releases are updates to match the native versions. -- Yaakov
Updated: mysql-5.5.40-1
The following packages have been updated for the Cygwin distribution:
*** mysql-5.5.40-1
*** mysqld-5.5.40-1
*** mysql-test-5.5.40-1
*** libmysqlclient18-5.5.40-1
*** libmysqlclient-devel-5.5.40-1
*** libmysqld0-5.5.40-1
*** libmysqld-devel-5.5.40-1
MySQL Community Edition is a freely downloadable version of the world's
most popular open source database that is supported by an active
community of open source developers and enthusiasts.
Please note that the server ('mysqld' package) should be considered
*experimental*; for production use, I suggest using a native Windows
version from dev.mysql.com. Input from experienced MySQL server
administrators to improve this component would be welcome.
The client library and apps are stable, but when connecting to a native
Windows MySQL server on the same machine, you MUST use 127.0.0.1 as the
hostname; 'localhost' is reserved for connecting to the Cygwin mysqld
via a UNIX socket.
This is an update to the latest upstream 5.5 release, which includes
fixes for several security issues:
https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-40.html
--
Yaakov
New: autogen-5.18.2-1
The following packages have been added to the Cygwin distribution: * autogen-5.18.2-1 * libopts25-5.18.2-1 * libopts-devel-5.18.2-1 AutoGen is a tool designed to simplify the creation and maintenance of programs that contain large amounts of repetitious text. It is especially valuable in programs that have several blocks of text that must be kept synchronized. AutoOpts is an option processing library based on AutoGen. -- Yaakov
