radsecproxy (1.11.3-1) unstable; urgency=medium

  - To make it easier to run multiple instances of radsecproxy on one system,
    the package now also includes a template systemd unit, using files from
    /etc/radsecproxy/instances.d/

    To enable an instance, put a file "instancename.conf" in that directory
    and then enable the unit:

      systemctl enable --now radsecproxy@instancename.service

    If you run multiple instances, you need to make sure the listening
    ports do not overlap.

    It is also advisable to disable the default unit when using the
    instanced units:

     systemctl disable --now radsecproxy.service

  - A global include-directory at /etc/radsecproxy/includes.d/ has been
    added to the package. The default configuration and the example site
    configuration read all *.conf files from that directory, allowing easy
    deployment of global configuration options.

  It is *not* mandatory to use these two new facilities, the old way of running
  a single-instance radsecproxy setup with /etc/radsecproxy.conf as the sole
  main configuration file is still the default.

 -- Sven Hartge <sven@svenhartge.de>  Thu, 18 Sep 2025 13:16:55 +0200

radsecproxy (1.7.2-1) unstable; urgency=medium

  To improve the overall security of the system, radsecproxy is now running
  with reduced privileges and as a dedicated system user "radsecproxy" instead
  of running as root.
  
  This may require configuration changes in order for radsecproxy to be able
  to continue accessing its configuration file and configured certificates and
  private keys, as well as to be able to write to potentially configured log
  file destinations.

 -- Faidon Liambotis <paravoid@debian.org>  Tue, 08 Jan 2019 02:10:59 +0200
