• Cygwin 3.1.7
• OpenSSH 8.4p
• LibreSSL 3.1.2

• Rsync 3.2.3
• Cygwin 3.1.7

CowAxess version 1.1.0 contains GoAccess 1.4(link is external) and a major refresh of Cygwin and tools.

Version 6.1.0 of cwRsync server installer contain the latest available rsync (Changelog(link is external)). Client version is now provided as free.

'rsync --version' output:

 rsync  version 3.2.2  protocol version 31

Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others.

Web site: https://rsync.samba.org/

Capabilities:

    64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,

    socketpairs, hardlinks, symlinks, IPv6, atimes, batchfiles, inplace,

    append, no ACLs, no xattrs, optional protect-args, iconv, symtimes,

    prealloc

Optimizations:

    no SIMD, asm, openssl-crypto

Checksum list:

    xxh64 (xxhash) md5 md4 none

Compress list:

    zstd lz4 zlibx zlib none

rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you

are welcome to redistribute it under certain conditions.  See the GNU

General Public Licence for details.

Copssh version 7.3.0 installers come with OpenSSH 8.3p and LibreSSL 3.1.2. (Due to version bump-up from LibreSSL 3.0.2 at our side, you may also be interested in release notes for 3.1.1 and 3.1.0  as well).

Security
========

* scp(1): when receiving files, scp(1) could be become desynchronised
if a utimes(2) system call failed. This could allow file contents
to be interpreted as file metadata and thereby permit an adversary
to craft a file system that, when copied with scp(1) in a
configuration that caused utimes(2) to fail (e.g. under a SELinux
policy or syscall sandbox), transferred different file names and
contents to the actual file system layout.

Exploitation of this is not likely as utimes(2) does not fail under
normal circumstances. Successful exploitation is not silent - the
output of scp(1) would show transfer errors followed by the actual
file(s) that were received.

Finally, filenames returned from the peer are (since openssh-8.0)
matched against the user's requested destination, thereby
disallowing a successful exploit from writing files outside the
user's selected target glob (or directory, in the case of a
recursive transfer). This ensures that this attack can achieve no
more than a hostile peer is already able to achieve within the scp
protocol

Version 5.3.0 of Winrpe is a major update including security fixes and comes with NRPE 4.0.2(link is external) and LibreSSL 3.0.2(link is external) and the most recent versions of Cygwin and GNU Tools. Installers with 32-bit binaries are not provided any longer as a part of the product (Older versions available upon request).

Announcement from Nagios.org (https://github.com/NagiosEnterprises/nrpe(link is external)):

Notice: As of NRPE version 4.0.1, this project is deprecated. It will not receive any more bugfixes or features, except to resolve security issues.

Version 6.0.1 of cwRsync client/server installers contain the latest available Cygwin/GNU tools. OpenSSH binaries are also updated to version 8.2p with LibreSSL 3.0.2.

Copssh version 7.2.0 installers come with OpenSSH 8.2p, LibreSSL 3.0.2 and most recent versions of Cygwin and GNU tools. We have also updated Copssh Control Panel with some minor fixes.

-- Incompatibility note for Copssh versions 6.x and earlier --

As of version 7.0, Copssh uses Cygwin 3.x libraries, introducing major and backwards-incompatible changes, thus requiring a reinstallation. You can follow our instructions here, to refresh your installation withour losing your existing setup.

Thanks to major changes in Cygwin, Copssh doesn't need a dedicated service account any longer and is run by the local system account.

The logic behind the sftp home directory isolation is now improved by introducing symbolic link folders: Each activated user gets a symbolic link folder /home/___username , pointing to the home directory provided via the User Activation wizard, resulting with a more stable and less error-prone solution.  A small patch avoiding messages "bad ownership or modes for chroot directory" (non-relevant for a Copssh installation), is also introduced. NB! As always mentioned, even if the home directory isolation works as expected, you should use NTFS permissions on your file systems to achieve better security.

--- Potentially-incompatible changes in OpenSSH 8.2.0

This release includes a number of changes that may affect existing
configurations:

* ssh(1), sshd(8): the above removal of "ssh-rsa" from the accepted
CASignatureAlgorithms list.

* ssh(1), sshd(8): this release removes diffie-hellman-group14-sha1
from the default key exchange proposal for both the client and
server.

* ssh-keygen(1): the command-line options related to the generation
and screening of safe prime numbers used by the
diffie-hellman-group-exchange-* key exchange algorithms have
changed. Most options have been folded under the -O flag.

* sshd(8): the sshd listener process title visible to ps(1) has
changed to include information about the number of connections that
are currently attempting authentication and the limits configured
by MaxStartups.

* ssh-sk-helper(8): this is a new binary. It is used by the FIDO/U2F
support to provide address-space isolation for token middleware
libraries (including the internal one). It needs to be installed
in the expected path, typically under /usr/libexec or similar.

Adolsign 2.7.0 introduces support for Office 2019.