Log message:
Update net/rabbitmq to 3.6.9.

Management and Management Agent Plugins
- Security Vulnerability Patches
  - CVE-2017-4965: XSS vulnerabilities in management UI
  - CVE-2017-4966: authentication details are stored in browser-local
    storage without expiration
  - CVE-2017-4967: XSS vulnerabilities in management UI
- Bug Fixes
  - Certain TCP and TLS listener configuration settings could break
    JSON serialisation of GET /api/overview responses.

Federation Plugin
- More numerical types are now handled for the "hops" property.

.NET Client
- Calling ExchangeBind more than once with the same arguments threw an
  exception.

Log message:
Update net/rabbitmq to 3.6.8.

3.6.8
- Erlang/OTP R16B03 and 17.x compatibility restored
- Minor bug fixes

3.6.7
- Distributed management plugin, including minor breaking HTTP API changes.
- Bug fixes
- Usability improvements

Log message:
Update net/rabbitmq to 3.6.6.

- Security vulnerability fix
- Bug fixes

See full release notes:

  https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_6

Log message:
Update net/rabbitmq to 3.6.5.

3.6.5
- Bug fixes

3.6.4
- Bug fixes
- Erlang 19.0 compatibility
- Usability improvements

3.6.3
- Important bug fixes
- systemd support in the Debian package
- New OpenGPG key used for artifact signing
- New plugins included into the distribution
- Usability improvements

3.6.2
- Bug fixes
- New statistics collector in management plugin
- Usability improvements

Log message:
Remove the stability entity, it has no meaning outside of an official context.

Log message:
Change the service_bundle name to "export" to reduce diffs between the
original manifest.xml file and the output from "svccfg export".

Log message:
Update net/rabbitmq to 3.6.1

RabbitMQ 3.6.1 is a maintenance release that includes a fix for
CVE-2015-8786, a vulnerability in RabbitMQ management plugin.

Server
- Purging a lazy queue could result in an exception
- Ensure epmd is running before starting RabbitMQ node on Windows
- Channel error could make broker unreachable
- (Automatic) deletion of an auto-delete queue could lead
  to blocked channels
- During (from scratch) queue sync, queue master node didn't respect
  mirror alarm state. With large data sets this could drive mirror
  node out of memory.
- Changing password for users with non-standard (think broker
  configuration) password hashing function, for example, those migrated
  from 3.5.x releases, didn't update effective hashing function.
- Heavy and/or prolonged rabbitmqctl use could exhaust Erlang VM atom table
- "Min masters" queue master location strategy could result in an error.
- Fixed a race condition in pause_minority handling mode.
- Significantly reduce possibility of a race condition when an exchange
  is deleted and immediately re-declared, e.g. by a federation link.
- amq.rabbitmq.log messages now have information about originating
  node in message headers
- scripts/rabbitmq-env now works with GNU sed 4.2.2
- Exceptions in VM memory use calculator no longer affect broker startup
- Direct Reply-to capability is now advertised to clients
- Paths with non-ASCII characters on Windows are now handled
- Configurable number of TCP connection acceptors
- rabbitmqctl cluster_status now includes cluster-wide resource alarm status
- Windows installer no longer jumps over installation log
- Improved rabbitmqctl reset error messages
- More unsigned field data types are supported.

Federation Plugin
- Significantly reduce possibility of a race condition when an exchange
  is deleted and immediately re-declared, e.g. by a federation link

Management plugin
- CVE-2015-8786: user-provided query parameters lengths_age and
  lengths_incr had no validation and could be used to exhaust server
  resources.
- Password hashing function is now included in exported definitions
- Internet Explorer (9+) compatibility restored
- Internet Explorer 11 compatibility fixes
- When policy fails to be created with invalid paramaters a sensible
  error message will be displayed.

Federation Management plugin
- Federation link form now includes more settings (that are exchange-
  and queue-federation specific)

Log message:
Add build dependency on net/rsync to fix installation on platforms
that do not have rsync.

Log message:
Update net/rabbitmq to 3.6.0.
Clean up and simplify Makefile.

Breaking changes in 3.6.0:

- Minimum required Erlang version is R16B03 for plain ("just TCP")
  connections for all protocols and 17.5 for TLS ones (18.x is
  recommended for both).
- .NET client now requires .NET 4.5.
- "Immediate" flag is removed from the .NET client (it hasn't been
  supported by the server since RabbitMQ 3.0).
- Default subscription TTL in MQTT is now 24 hours.
- Server artifacts are now distributed as xz archives and not gz.
- Build system has been completely reworked and now uses erlang.mk.
  3rd party plugins must be adapted to the new build system.

Key improvements in this release are:

- Lazy queues
- Much better queue synchronisation throughput
- Lower RAM use, tunable flow control
- Stronger password encryption with pluggable algorithms
- Development moved to GitHub; build system now uses erlang.mk
- Significant improvements to Web STOMP
- Experimental WinRT-compatible .NET client, SQL CLR compatibility
  in the "regular" one
- Pagination in management UI
- More popular plugins now ship with the broker: rabbitmq_sharding
  and rabbitmq_event_exchange, for example.

Full release notes:

  https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_0

Log message:
Extend PYTHON_VERSIONS_INCOMPATIBLE to 35