1. 24 Nov, 2020 17 commits
  2. 23 Nov, 2020 3 commits
    • Thomas Haller's avatar
      build/meson: fix build to always set "-W" compiler flags · c0c6470e
      Thomas Haller authored
      We must set these compiler flags independent as to whether this
      is a release build or a debug build.
      In most cases, we don't differentiate between release and debug build
      anyway. Granted, we have "-D more_asserts=100" and set "-O" CFLAGS,
      but that is more granular and not a simple "buildtype".
      In particular, these compiler flags apply to all kinds of builds.
      This is important, because otherwise we get build failures, because
      also in release build we want to build with `-Werror` and `-Wall`.
    • Thomas Haller's avatar
      gitignore: ignore "/docs/libnm/libnm.actions" · df76da8e
      Thomas Haller authored
      Dunno why this file now gets generated.
    • Thomas Haller's avatar
      Revert "dns: change default DNS priority of VPNs to -50" · ff71bbdc
      Thomas Haller authored
      Revert this change. One problem is that none of the current GUIs
      (nm-connection-editor, gnome-control-center, plasma-nm) expose the
      dns-priority option. So, users tend to have their profile value set to
      0. Changing the default means for them not only a change in behavior,
      but its hard to fix via the GUI.
      Also, what other call DNS leaks, is Split DNS to some. Both uses make
      sense, but have conflicting goals. The default cannot accommodate both
      at the same time.
      Also, with split DNS enabled (dnsmasq, systemd-resolved), the concern
      for DNS leaks is smaller. Imagine:
        Wi-Fi profile with ipv4.dns-priority (effectively) 100, domain "example.com".
        VPN profile with ipv4.dns-priority (effectively) 50 and a default route.
      That is a common setup that one gets by default (and what probably many
      users have today). In such a case with split DNS enabled, the Wi-Fi's DNS
      server only sees requests for "*.example.com". So, it does not leak
      Hence, revert this change before 1.28.0 release to the earlier behavior.
      This reverts commit af13081b.
  3. 20 Nov, 2020 17 commits
  4. 19 Nov, 2020 3 commits