relayor v18.1.1

Changes since v18.1.0:

• update GPG signing key for deb.torproject.org debian packages (key expired previously)

relayor v18.1.0

Changes since v18.0.0:

• enable NoExec by default on all platforms except CentOS
• increase min. ansible version from 2.5.3 to v2.6.2
• fix the ExitPolicy format in the example playbook
• change default shipped exit policy (remove POP3, IMAP and kerberos ports)
• change the ControlSocket path (make it actually usable)
  if you want to authorize a user for the ControlSocket you have add it to the
  group of the tor instance running it

relayor v18.0.0

Changes since v0.4.0:

• bugfix for tor_dedicatedExitIP when IPv6 is available

adds a missing space between OutboundBindAddressExit and the IPv6 address (bug introduced in e79db1f)
wraps IPv6 addresses in OutboundBindAddressExit in square brackets

• show exit-notice HTML page on all exit IP addresses (#168, #175)

previously we only displayed the exit-notice HTML page
on IPv4 DirPort, this change adds DirPorts and makes
the exit-notice HTML page also visilble on IPv6

In the special case of OutboundBindAddressExit / tor_dedicatedExitIP
we also enable unadvertised DirPorts on the IPv4/v6 addresses
used for OutboundBindAddressExit

• OutboundBindAddress: wrap IPv6 address in sq. brackets

• tor_RelayBandwidthRate_file: do not add RelayBandwidthRate line if empty

• add support for FreeBSD 11.2 (drop 11.1)

• change version scheme to YY.major.patch
  (YY are the last two digits of the year)

relayor v0.4.0

Changes since v0.3.3:

• major: change the format of tor_ExitPolicy (single-line to multi-line)

previously you defined your tor exit policy like this:

tor_ExitPolicy: "accept *:80, accept *:443, accept *:22, reject *:*"

now you define your exit policy like this:

tor_ExitPolicy:
  - accept *:80
  - accept *:443
  - accept *:22
  - reject *:*

• support multiple IP addresses for OutboundBindAddressExit
• add support for OpenBSD 6.3 (drop 6.2)
• add support for Ubuntu 18.04 (drop 16.04)
• add support for Fedora 28 (drop 27)
• drop support for Debian 8 and HBSD
• increase min. tor version to 0.2.9.x
• increase min. ansible verstion to 0.2.5.3
• add support for custom addition to MyFamily members
• switch tor_alpha_version from 0.3.3.x to 0.3.4.x
• Debian: switch to HTTPS (from HTTP) for repository traffic
• reorder some torrc items

relayor v0.3.3

Changes since v0.3.2:

• major workaround for an upstream bug in tor that prevented us from running more than 2 instances per server. This affected only users with a non-default tor_maxPublicIPs setting. (#153)
  Thanks to Tim Niemeyer (@RedDog99) (f3netze.de) for bringing this to our attention.
• relayor now ships a kitchen file for integration testing (#149)
  Thanks to Ondrej Vaško (@Lirt) for the patch.

relayor v0.3.2

Changes since v0.3.1:

• add support for new denial-of-service mitigation torrc options
• bugfix: define default value for tor_nightly_builds (bug introduced in v0.3.1)
• tor_dedicatedExitIP: avoid changing OutboundBindAddressExit if more tor instances are added
• add support for per-instance configuration of RelayBandwidthRate/RelayBandwidthBurst (previously this was only possible on a per server-level)
• update the included exit policy

relayor v0.3.1

Changes since v0.3.0:

• support custom tor-exit-notice.html files (fixes #140)
• increase tor_alpha_version: 0.3.2.x -> 0.3.3.x
• Debian/Ubuntu: add support for tor nightly builds
• implement per-instance ExitRelay settings (fixes #146)
• make tor package state configurable (latest vs. present)

relayor v0.3.0

Notable changes since v0.2.1:

• enable tor's Sandbox feature by default on Debian based systems
• add support for automatic use of OutboundBindAddressExit via simple on/off boolean (opt-in)
• add support for HardenedBSD
• add support for tor alpha releases on FreeBSD/HardenedBSD
• add support for more torrc options
• performance improvement due to the use of dynamic includes (ansible)

relayor v0.2.1

https://medium.com/@nusenu/deploying-tor-relays-with-ansible-6612593fa34d