Hello Chuck,
I tried your tool and indeed it helps a lot understanding what's happening.
For me the sections I find really useful (at least for this use case) are
- "Connections" to identify the peers
- "Message progress" to see the message routing
- "Routing link state" to monit
CVE-2019-0223: Apache Qpid Proton TLS Man in the Middle Vulnerability
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected: Qpid Proton 0.9 - 0.27.0.
Description:
The TLS support in Apache Qpid Proton 0.9 - 0.27.0 can under some
circumstances connect as a client to a TLS
The Apache Qpid (http://qpid.apache.org) community is pleased to announce
the immediate availability of Apache Qpid Proton 0.27.1.
Apache Qpid Proton is a messaging library for the Advanced Message Queuing
Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It can be used
in a wide range
Greetings,
Does qpid/proton support tls 1.2 when using encryption?
How can I verify that tls 1.2 is actually used?
Best regards,
--
\ / | |
(OvO) | Mikhail Iwanow |
(^^^) | Voice: +7 (911) 223-1300 |
\^/ | E-mail: iv...@
I am of the same opinion as Gordon that fixing the counting (to be atomic)
will only address the current symptom without preventing other races that
will present themselves later or on other hardware architectures.
Having two threads participating in Proton object reference counting is
problematic
