Merge branch 'dev'

Author: gershnik

.github/workflows/build.yml

@@ -73,7 +73,7 @@ jobs:
   mac:
     runs-on: macos-14
     env: 
-      DEVELOPER_DIR: /Applications/Xcode_15.4.app
+      DEVELOPER_DIR: /Applications/Xcode_16.2.app
 
     steps:
     - name: Checkout

.github/workflows/check.yml

@@ -21,26 +21,43 @@ on:
 
 jobs:
   linux:
-    runs-on: ubuntu-latest
+    runs-on: ${{ matrix.os }}
     strategy:
       fail-fast: false
       matrix:
         include: 
+          #gcc
         - compiler: gcc
           version: 11
+          os: ubuntu-latest
         - compiler: gcc
           version: 12
+          os: ubuntu-latest
+        - compiler: gcc
+          version: 13
+          os: ubuntu-latest
         - compiler: gcc
+          version: 14
+          os: ubuntu-latest
+          #clang
+        - compiler: clang
           version: 13
-        # See https://github.com/actions/runner-images/issues/8659
-        # - compiler: clang
-        #   version: 13
-        # - compiler: clang
-        #   version: 14
+          os: ubuntu-22.04
+        - compiler: clang
+          version: 14
+          os: ubuntu-22.04
         - compiler: clang
           version: 15
+          os: ubuntu-22.04
+        - compiler: clang
+          version: 16
+          os: ubuntu-22.04
         - compiler: clang
           version: 17
+          os: ubuntu-latest
+        - compiler: clang
+          version: 18
+          os: ubuntu-latest
     steps:
       - name: Checkout
         uses: actions/checkout@v4
@@ -54,8 +71,10 @@ jobs:
             wget https://apt.llvm.org/llvm.sh
             chmod u+x llvm.sh
             sudo ./llvm.sh ${{ matrix.version }}
+            sudo apt-get install -y clang-tools-${{ matrix.version }} libc++-${{ matrix.version }}-dev libc++abi-${{ matrix.version }}-dev
             echo "CC=clang-${{ matrix.version }}" >> $GITHUB_ENV
             echo "CXX=clang++-${{ matrix.version }}" >> $GITHUB_ENV
+            echo "CXXFLAGS=-stdlib=libc++" >> $GITHUB_ENV
           fi
 
           if [[ '${{ matrix.compiler }}' == 'gcc' ]]; then
@@ -110,9 +129,9 @@ jobs:
         - os: macos-13
           xcode: '15.2'
         - os: macos-14
-          xcode: '14.3.1'
+          xcode: '15.4'
         - os: macos-14
-          xcode: '15.3'
+          xcode: '16.2'
     env: 
       DEVELOPER_DIR: /Applications/Xcode_${{ matrix.xcode }}.app
     steps:

.github/workflows/publish.yml

@@ -75,7 +75,7 @@ jobs:
     runs-on: macos-14
     needs: prepare
     env: 
-      DEVELOPER_DIR: /Applications/Xcode_15.4.app
+      DEVELOPER_DIR: /Applications/Xcode_16.2.app
 
     steps:
     - name: Checkout

CHANGELOG.md

@@ -5,6 +5,15 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 ## Unreleased
 
+### Added
+* `--source-port` command line argument and `source-port` config file option to set the source port for multicast messages 
+  for better firewall interoperability.
+* Configuration files for `firewalld`. These are now also delivered and used in RPM binary packages.
+
+### Changed
+- Updated 3rd party dependencies
+- Firewall configuration files now live under `config/firewalls`
+
 ## [1.15] - 2024-10-03
 
 ### Changed

README.md

@@ -324,7 +324,7 @@ sudo dnf install wsddn
 #sudo yum install wsddn
 ```
 
-On first install firewall ports `5357/tcp` and `3702/udp` will be opened. 
+On first install firewall will be configured to open `wsddn` service. 
 
 Enable and start the daemon:
 
@@ -661,7 +661,7 @@ Command line flags and configuration file entries are documented in `man wsddn`
 
 ### Firewall Setup
 
-<small>Note: The following instructions are copied verbatim from [wsdd][wsdd] one since the requirements are identical</small>
+<small>Note: The following instructions are copied almost verbatim from [wsdd][wsdd] since the requirements are identical</small>
 
 Traffic for the following ports, directions and addresses must be allowed.
 
@@ -673,12 +673,17 @@ Traffic for the following ports, directions and addresses must be allowed.
 
 You should further restrict the traffic to the (link-)local subnet, e.g. by using the `fe80::/10` address space for IPv6. Please note that IGMP traffic must be enabled in order to get IPv4 multicast traffic working.
 
+For UFW and firewalld, application/service profiles can be found under `config/firewalls`. If using binary installation packages these are provided 
+as part of the installation. Note that UFW profiles only allow to grant the traffic on specific UDP and TCP ports, but a restriction on the IP range (like link local for IPv6) or the multicast traffic is not possible.
+
 ### Security
 
-There are two main security concerns with a daemon that delivers data about local machine over the network
+There are four main security concerns with a daemon that accepts network requests and delivers data about local machine over the network
 
-1. A bug inside daemon code may allow remote attacker to penetrate the machine running it.
+1. A bug inside the daemon code may allow a remote attacker to penetrate the machine running it.
 2. The information legitimately provided by the daemon will disclose something to an attacker that would otherwise remain unknown, enabling him to mount further attacks.
+3. A bug or even the _normal functionality_ of the daemon might allow a remote attacker to use it to mount further attacks against other systems. For example it might be possible to "convince" the daemon to become a part of a distributed denial of service (DDoS) attack.
+4. A bug or a normal operation of the daemon might allow a remote attacker to make it or even the entire machine hosting it unresponsive resulting in a denial of service.
 
 Currently the implementation ignores the second concern. The things **wsdd-native** discloses are the existence of the local host, its name, presence of Samba on it and domain/workgroup membership. All of these are generally disclosed by Samba itself via SMB broadcasts so, assuming the firewall is configured as described above, there is no net gain for an attacker. WS-Discovery protocol contains provisions for encrypting its HTTP traffic and potentially authenticating clients accessing your host via their client certificates. This limits exposure somewhat but at a significant configuration and maintenance cost. If there is interest in any of it it is possible to easily add this functionality in a future version. 
 
@@ -688,7 +693,15 @@ The first concern is by far the most significant one. All software contains bugs
 
 These measures are automatic and cannot be bypassed. Taken together they should limit the fallout of any vulnerability though, of course, nothing ever can be claimed to be 100% secure.
 
-Note that when running on `systemd` systems it is recommended to use its `DynamicUser` facility instead of running as root and relying on the measures above. The Debian/Ubuntu/Arch installer does so.
+Note that when running on `systemd` systems it is recommended to use its `DynamicUser` facility instead of running as root and relying on the measures above. The Debian/Ubuntu/Fedora/Arch binary packages do so.
+
+The third concern is also a significant one. Even in absence of any bugs a completely correct implementation of WS-Discovery protocol is known to be vulnerable to these kinds of attacks. See for example 
+[here](https://blogs.akamai.com/sitr/2019/09/new-ddos-vector-observed-in-the-wild-wsd-attacks-hitting-35gbps.html) and 
+[here](https://www.zdnet.com/article/protocol-used-by-630000-devices-can-be-abused-for-devastating-ddos-attacks/). 
+Bugs (always a possibility) can make things even worse. As far as I know there is no effective mitigation to this threat that **wsdd-native** can implement in code. The only way to prevent these kinds of attacks is to __never__ expose **wsdd-native** ports to open internet via [firewall configuration](#firewall-setup). Given that the whole purpose of this daemon is to enable interoperability with Windows via SMB protocol there is probably never a good
+reason to let it accept and send traffic outside of a local network.
+
+The fourth concern, while also present, is less severe than the above. **wsdd-native** is single threaded and so, even if overwhelmed by traffic, will not stress more than 1 CPU core. Its memory consumption is bounded so, in absence of bugs, it will not stress system memory either. It can itself be rendered unresponsive, of course, by too much traffic but, considering that it probably isn't a vital service for anyone, this isn't something that would excite any attacker. Possible bugs change this picture, however. If the network process is hijacked, even if mitigations for the 1st concern prevent further system penetration, the attacker can still make the network process consume too much CPU and memory. You can try to mitigate against this possibility by limiting daemon CPU and memory usage via [cgroups](https://www.redhat.com/en/blog/cgroups-part-four) or other mechanisms. However, a much simpler solution to these issues is the same as the above - never expose the daemon to the open internet.
 
 ### Custom metadata
 

cmake/dependencies.cmake

@@ -22,7 +22,7 @@ list(APPEND DEPENDECIES_JSON "\"argum\": \"pkg:github/${ARGUM_REPO}@${ARGUM_VER}
 #################################################
 
 set(SYS_STRING_REPO gershnik/sys_string)
-set(SYS_STRING_VER v2.14)
+set(SYS_STRING_VER v2.16)
 FetchContent_Declare(sys_string
     GIT_REPOSITORY  https://github.com/${SYS_STRING_REPO}.git
     GIT_TAG         ${SYS_STRING_VER}
@@ -77,7 +77,7 @@ if (NOT LibXml2_FOUND)
     set(LIBXML2_WITH_MODULES OFF)
     set(LIBXML2_WITH_PROGRAMS OFF)
 
-    set(LIBXML_VER v2.13.4)
+    set(LIBXML_VER v2.13.5)
     FetchContent_Declare(libxml2
         GIT_REPOSITORY  https://gitlab.gnome.org/GNOME/libxml2.git
         GIT_TAG         ${LIBXML_VER}
@@ -91,7 +91,7 @@ endif()
 #################################################
 
 set(UUID_REPO gershnik/libuuid-cmake)
-set(UUID_VER v2.40.2)
+set(UUID_VER v2.40.3)
 FetchContent_Declare(libuuid
     GIT_REPOSITORY  https://github.com/${UUID_REPO}.git
     GIT_TAG         ${UUID_VER}
@@ -105,7 +105,7 @@ list(APPEND DEPENDECIES_JSON "\"libuuid\": \"pkg:github/${UUID_REPO}@${UUID_VER}
 set(FMT_INSTALL OFF)
 
 set(FMT_REPO fmtlib/fmt)
-set(FMT_VER 11.0.2)
+set(FMT_VER 11.1.1)
 FetchContent_Declare(fmt
     GIT_REPOSITORY  https://github.com/${FMT_REPO}
     GIT_TAG         ${FMT_VER}
@@ -122,11 +122,16 @@ set(SPDLOG_NO_TLS ON CACHE BOOL "prevent spdlog from using thread local storage"
 set(SPDLOG_FMT_EXTERNAL ON CACHE BOOL "Use external fmt library instead of bundled")
 
 set(SPDLOG_REPO gabime/spdlog)
-set(SPDLOG_VER v1.14.1)
+set(SPDLOG_VER v1.15.0)
 FetchContent_Declare(spdlog
-    GIT_REPOSITORY  https://github.com/${SPDLOG_REPO}
-    GIT_TAG         ${SPDLOG_VER}
-    GIT_SHALLOW     TRUE
+    # GIT_REPOSITORY  https://github.com/${SPDLOG_REPO}
+    # GIT_TAG         ${SPDLOG_VER}
+    # GIT_SHALLOW     TRUE
+
+    URL              https://github.com/${SPDLOG_REPO}/tarball/${SPDLOG_VER}
+
+    PATCH_COMMAND    patch -p0 -s -f -i ${CMAKE_CURRENT_LIST_DIR}/patches/spdlog.diff 
+    LOG_PATCH        ON
 )
 list(APPEND DECLARED_DEPENDENCIES spdlog)
 list(APPEND DEPENDECIES_JSON "\"spdlog\": \"pkg:github/${SPDLOG_REPO}@${SPDLOG_VER}\"")
@@ -150,7 +155,7 @@ list(APPEND DEPENDECIES_JSON "\"tomlplusplus\": \"pkg:github/${TOMPLUSPLUS_REPO}
 #################################################
 
 set(OUTCOME_REPO ned14/outcome)
-set(OUTCOME_VER v2.2.10)
+set(OUTCOME_VER v2.2.11)
 # FetchContent_Declare(outcome
 #     GIT_REPOSITORY  https://github.com/${OUTCOME_REPO}
 #     GIT_TAG         ${OUTCOME_VER}

cmake/patches/spdlog.diff

@@ -0,0 +1,8 @@
+--- include/spdlog/fmt/fmt.h
++++ include/spdlog/fmt/fmt.h
+@@ -27,4 +27,5 @@
+ #else  // SPDLOG_FMT_EXTERNAL is defined - use external fmtlib
+     #include <fmt/core.h>
+     #include <fmt/format.h>
++    #include <fmt/xchar.h>
+ #endif

config/firewalls/etc/firewalld/services/wsddn-http.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="utf-8"?>
+<service>
+  <short>WS-Discovery Host Daemon (HTTP Interface)</short>
+  <description>Allows your machine to be discovered by Windows 10 and above systems and displayed by their Explorer &quot;Network&quot; views.</description>
+  <port port="5357" protocol="tcp"/>
+</service>

config/firewalls/etc/firewalld/services/wsddn.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="utf-8"?>
+<service>
+  <short>WS-Discovery Host Daemon</short>
+  <description>Allows your machine to be discovered by Windows 10 and above systems and displayed by their Explorer &quot;Network&quot; views.</description>
+  <port port="3702" protocol="udp"/>
+  <destination ipv4="239.255.255.250" ipv6="FF02::C"/>
+  <include service="wsddn-http"/>
+</service>

config/firewalls/etc/ufw/applications.d/wsddn

@@ -0,0 +1,4 @@
+[wsddn]
+title=WS-Discovery Host Daemon
+description=Allows your machine to be discovered by Windows 10 and above systems and displayed by their Explorer "Network" views. 
+ports=3702/udp|5357/tcp