[rabbitmq-discuss] Experimenting with release candidates: RabbitMQ 2.7.9
steve at rabbitmq.com
Thu Mar 15 11:44:07 GMT 2012
The "hack" will no longer be required in the next release; thanks for
Logging ssl detail is a little scary; though the log could add some more
information. We'll improve that.
The DN/CN issues were discussed recently, but I'll leave it to Simon to
explain our position on that.
Steve Powell (a cheery bunny)
----------some more definitions from the SPD----------
chinchilla (n.) Cooling device for the lower jaw.
socialcast (n.) Someone to whom everyone is speaking but nobody likes.
On 14 Mar 2012, at 14:42, Lionel Cons wrote:
> Simon MacMullen writes:
>> Damn, it looks like you need some default_user details defined for this
>> to work. (They can be invalid credentials: they will not be used, they
>> just need to exist.)
> Indeed, adding a default_user seems to work. It would be nice if this
> "hack" could be removed.
> However, I've only progressed a tiny bit. I now get:
> =ERROR REPORT==== 14-Mar-2012::15:37:22 ===
> STOMP error frame sent:
> Message: "Bad CONNECT"
> Detail: "Authentication failure\n"
> Server private detail: none
> Which is normal since the certificate I've used is not known. However,
> could the DN be logged in the "Server private detail" section please?
> I remember some discussions about DN formats, quotes, escaping... and
> I would like to know from RabbitMQ itself what it expects.
> There was also the question of CN versus DN, is this configurable now?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss