1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
Release: RabbitMQ 3.4.1
Security Fixes
==============
management plugin
-----------------
26437 prevent /api/* from returning text/html error messages which could
act as an XSS vector (since 2.1.0)
26433 fix response-splitting vulnerability in /api/downloads (since 2.1.0)
(thanks to Atholl Stewart for finding the above)
Release Highlights
==================
server
------
bug fixes
26425 ensure RABBITMQ_USE_LONGNAME / USE_LONGNAME is picked up correctly from
rabbitmq-env.conf (since 3.4.0)
enhancements
26429 add log messages when plugins are enabled or disabled at runtime
management plugin
-----------------
bug fixes
26431 fix web UI breakage when queue listing contains exclusive queues
(since 3.4.0)
26438 fix internal server error when requesting permissions for a user or
vhost which does not exist (since 2.1.0)
Java client
-----------
bug fixes
26434 prevent exchange binding recovery from swapping source and
destination (since 3.3.0)
26428 ensure pom.xml lists ASL 2.0 (since 3.4.0)
.NET client
-----------
bug fixes
26439 ensure attempt to open a channel on a closed connection fails
immediately (since 1.0.0)
26435 fix typos in documentation and remove references to immediate
publishing (since 3.3.0)
Upgrading
=========
To upgrade a non-clustered RabbitMQ from release 2.1.1 or later, simply install
the new version. All configuration and persistent message data is retained.
To upgrade a clustered RabbitMQ from release 2.1.1 or later, install the new
version on all the nodes and follow the instructions at
https://www.rabbitmq.com/clustering.html#upgrading .
To upgrade RabbitMQ from release 2.1.0, first upgrade to 2.1.1 (all data will be
retained), and then to the current version as described above.
When upgrading from RabbitMQ versions prior to 2.1.0, the existing data will be
moved to a backup location and a fresh, empty database will be created. A
warning is recorded in the logs. If your RabbitMQ installation contains
important data then we recommend you contact support at rabbitmq.com for
assistance with the upgrade.
|
