[ANNOUNCEMENT] Updated: git v2.7.0
Version 2.7.0-1 of Git has been uploaded and should be coming soon to a mirror near you. This update includes the following packages: - git - git-completion - git-cvs - git-debuginfo - git-email - git-gui - gitk - git-svn This is an update to the latest upstream release. For a full list of the upstream changes in this release, please refer to the upstream changelogs: https://git.kernel.org/cgit/git/git.git/tree/Documentation/RelNotes Enjoy! -- 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.ico & Cygwin-Terminal.ico cannot be deleted
Thanks Larry :) -- 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 2.4.0-0.18
On Jan 14 10:17, Corinna Vinschen wrote: > On Jan 13 12:48, random user wrote: > > >> It's a bit late now to change how Cygwin constructs and evaluates ACLs. > > > > Sorry, with the holidays and other issues it wasn't possible for me to > > look at the test drops earlier. > > We're testing this Cygwin change for four(!) months now. I release > the first one on Sep 2nd. It's a bit late now just to support some > border case within 48 hours before the release. Also consider that > NFSv4 uses yet another way to create POSIX-like ACLs which apparently > doesn't match the NTFS-3G layout either. It's not so much the layout > of the ACL which decides, it's that every implementation can work > with the ones created by other implementations. There's that weird > problem with the dir recognized as socket, but that's something I'll > look into at one point. I did and found the problem. Please give the latest snapshot from https://cygwin.com/snapshots/ a try. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
[ANNOUNCEMENT] Updated: OpenSSH-7.1p2-1
I've just updated the Cygwin version of OpenSSH to 7.1p2-1. This is a security upstream release. Below's the original release message. Please note that the release message has a bug :) The entry "SECURITY: Eliminate the fallback from untrusted X11-forwarding ..." is wrong since this change has been taken out of the 7.1p2 last-minute. = OpenSSH 7.1p2 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. OpenSSH also includes transitional support for the legacy SSH 1.3 and 1.5 protocols that may be enabled at compile-time. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested snapshots or donated to the project. More information on donations may be found at: http://www.openssh.com/donations.html Changes since OpenSSH 7.1p1 === * SECURITY: ssh(1): The OpenSSH client code between 5.4 and 7.1 contains experimential support for resuming SSH-connections (roaming). The matching server code has never been shipped, but the client code was enabled by default and could be tricked by a malicious server into leaking client memory to the server, including private client user keys. The authentication of the server host key prevents exploitation by a man-in-the-middle, so this information leak is restricted to connections to malicious or compromised servers. MITIGATION: For OpenSSH >= 5.4 the vulnerable code in the client can be completely disabled by adding 'UseRoaming no' to the gobal ssh_config(5) file, or to user configuration in ~/.ssh/config, or by passing -oUseRoaming=no on the command line. PATCH: See below for a patch to disable this feature (Disabling Roaming in the Source Code). This problem was reported by the Qualys Security Advisory team. * SECURITY: Eliminate the fallback from untrusted X11-forwarding to trusted forwarding for cases when the X server disables the SECURITY extension. Reported by Thomas Hoger. * SECURITY: Fix an out of-bound read access in the packet handling code. Reported by Ben Hawkes. * PROTOCOL: Correctly interpret the 'first_kex_follows' option during the intial key exchange. Reported by Matt Johnston. * Further use of explicit_bzero has been added in various buffer handling code paths to guard against compilers aggressively doing dead-store removal. Checksums: == - SHA1 (openssh-7.1p2.tar.gz) = 9202f5a2a50c8a55ecfb830609df1e1fde97f758 - SHA256 (openssh-7.1p2.tar.gz) = dd75f024dcf21e06a0d6421d582690bf987a1f6323e32 ad6619392f3bfde6bbd Please note that the SHA256 signatures are base64 encoded and not hexadecimal (which is the default for most checksum tools). The PGP key used to sign the releases is available as RELEASE_KEY.asc from the mirror sites. Reporting Bugs: === - Please read http://www.openssh.com/report.html Security bugs should be reported directly to open...@openssh.com OpenSSH is brought to you by Markus Friedl, Niels Provos, Theo de Raadt, Kevin Steves, Damien Miller, Darren Tucker, Jason McIntyre, Tim Rice and Ben Lindstrom. Disabling Roaming in the Source Code: = --- readconf.c 30 Jul 2015 00:01:34 - 1.239 +++ readconf.c 13 Jan 2016 23:17:23 - @@ -1648,7 +1648,7 @@ initialize_options(Options * options) options->tun_remote = -1; options->local_command = NULL; options->permit_local_command = -1; - options->use_roaming = -1; + options->use_roaming = 0; options->visual_host_key = -1; options->ip_qos_interactive = -1; options->ip_qos_bulk = -1; @@ -1819,8 +1819,7 @@ fill_default_options(Options * options) options->tun_remote = SSH_TUNID_ANY; if (options->permit_local_command == -1) options->permit_local_command = 0; - if (options->use_roaming == -1) - options->use_roaming = 1; + options->use_roaming = 0; if (options->visual_host_key == -1) options->visual_host_key = 0; if (options->ip_qos_interactive == -1) --- ssh.c 30 Jul 2015 00:01:34 - 1.420 +++ ssh.c 13 Jan 2016 23:17:23 - @@ -1882,9 +1882,6 @@ ssh_session2(void) fork_postauth(); } - if (options.use_roaming) - request_roaming(); - return client_loop(tty_flag, tty_flag ? options.escape_char : SSH_ESCAPECHAR_NONE, id); } = -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Pr
No output from an executable when linked to a dll (both executable and dll build by me)
Hi ppl,
I have a problem when running an executable, it seems that is running
fine, but I don't get any output in the console.
I need to build the [Paho MQQT
Client](https://eclipse.org/paho/clients/c/) in Cygwin. So I modified
the Makefile in order to build .dll instead of .so files. I have
attached the changes I made to the Makefile(Makefile_cygwin.patch). I
followed the instructions
[here](https://cygwin.com/cygwin-ug-net/dll.html) for the dll.
The client comes with some sample applications, so I tried to run one
of them, MQTTAsync_publish.exe. I would expect to get the following
output (I run it in a linux box)
$ Waiting for publication of Hello World!
$ on topic MQTT Examples for client with ClientID: ExampleClientPub
$ Connect failed, rc 0
but I don't get anything in the console and the application seems to
run without any other output or any indication. First I thought that I
hadn't linked correctly the dll, but I executed the following
$ cygcheck.exe ./MQTTAsync_publish.exe
C:\cygwin64-fresh\home\svagionitis\workspace\org.eclipse.paho.mqtt.c.git\build\output\samples\MQTTAsync_publish.exe
C:\cygwin64-fresh\bin\cygwin1.dll
C:\Windows\system32\KERNEL32.dll
C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
C:\Windows\system32\ntdll.dll
C:\Windows\system32\KERNELBASE.dll
C:\Windows\system32\API-MS-Win-Core-ProcessThreads-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Heap-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Memory-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Handle-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Synch-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-File-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-IO-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ThreadPool-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-LibraryLoader-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-NamedPipe-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Misc-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-SysInfo-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Localization-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ProcessEnvironment-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-String-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Debug-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-ErrorHandling-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Fibers-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Util-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Core-Profile-L1-1-0.dll
C:\Windows\system32\API-MS-Win-Security-Base-L1-1-0.dll
C:\cygwin64-fresh\usr\local\lib\cygpaho-mqtt3a.dll.1.0
and it seems that the library is there. I have installed all the
produced libraries in the /usr/local/lib and I have added the
/usr/local/lib to the PATH.
I am not sure what might be the problem, is it something related to
the output or something else? I am open to any suggestions of how to
pinpoint the problem.
Thank you in advance.
Regards,
Stavros
P.S. I have attached the cygcheck.out for more info of the system.
cygcheck.out
Description: Binary data
diff --git a/Makefile b/Makefile
index 9f9f002..0fd2441 100755
--- a/Makefile
+++ b/Makefile
@@ -30,8 +30,14 @@ endif
# determine current platform
BUILD_TYPE ?= debug
ifeq ($(OS),Windows_NT)
- OSTYPE ?= $(OS)
- MACHINETYPE ?= $(PROCESSOR_ARCHITECTURE)
+ ifeq ($(shell uname -s | cut -d - -f 1),CYGWIN_NT)
+ OSTYPE ?= $(shell uname -s | cut -d - -f 1)
+ MACHINETYPE ?= $(shell uname -m)
+ build.level = $(shell date)
+ else
+ OSTYPE ?= $(OS)
+ MACHINETYPE ?= $(PROCESSOR_ARCHITECTURE)
+ endif
else
OSTYPE ?= $(shell uname -s)
MACHINETYPE ?= $(shell uname -m)
@@ -109,20 +115,41 @@ MAJOR_VERSION = 1
MINOR_VERSION = 0
VERSION = ${MAJOR_VERSION}.${MINOR_VERSION}
-MQTTLIB_C_TARGET = ${blddir}/lib${MQTTLIB_C}.so.${VERSION}
-MQTTLIB_CS_TARGET = ${blddir}/lib${MQTTLIB_CS}.so.${VERSION}
-MQTTLIB_A_TARGET = ${blddir}/lib${MQTTLIB_A}.so.${VERSION}
-MQTTLIB_AS_TARGET = ${blddir}/lib${MQTTLIB_AS}.so.${VERSION}
+ifeq ($(OSTYPE),CYGWIN_NT)
+MQTTLIB_C_LIBNAME = cyg${MQTTLIB_C}.dll
+MQTTLIB_CS_LIBNAME = cyg${MQTTLIB_CS}.dll
+MQTTLIB_A_LIBNAME = cyg${MQTTLIB_A}.dll
+MQTTLIB_AS_LIBNAME = cyg${MQTTLIB_AS}.dll
+else
+MQTTLIB_C_LIBNAME = lib${MQTTLIB_C}.so
+MQTTLIB_CS_LIBNAME = lib${MQTTLIB_CS}.so
+MQTTLIB_A_LIBNAME = lib${MQTTLIB_A}.so
+MQTTLIB_AS_LIBNAME = lib${MQTTLIB_AS}.so
+endif
+
+MQTTLIB_C_TARGET = ${blddir}/${MQTTLIB_C_LIBNAME}.${VERSION}
+MQTTLIB_CS_TARGET = ${blddir}/${MQTTLIB_CS_LIBNAME}.${VERSION}
+MQTTLIB_A_TARGET = ${blddir}/${MQTTLIB_A_LIBNAME}.${VERSION}
+MQTTLIB_AS_TARGET = ${blddir}/${MQTTLIB_AS_LIBNAME}.${VERSION}
+
MQTTVERSION_TARGET = ${blddir}/MQTTVersion
-CCFLAGS_SO = -g -fPIC $(CFLAGS) -Os -Wall -fvisibility=hidden
FLAGS_EXE = $(LDFLAGS) -I ${srcdir} -lpthread -L ${blddir}
FLAGS_EXES = $(LDFLAGS) -I ${srcdir} ${START_GROUP} -lpthread -lssl -lcrypto ${END_GROUP} -L ${blddir}
+ifeq ($(OSTYPE),CYGW
