> Andreas, are you planning to fix the bug in the future version?
It is fixed now:
http://www.swiftmq.com/products/releasenotes/v942/index.html
--
Andreas Mueller
IIT Software GmbH, Bremen/Germany
http://www.swiftmq.com
IIT Software GmbH
Fahrenheitstr. 13, D28359 Bremen, Germany
Tel: +49 4
Yes, very soon.
Andreas
> Am 14.01.2014 um 18:34 schrieb serega :
>
> Andreas, are you planning to fix the bug in the future version?
>
> Thanks,
> Sergejs.
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/SASL-proton-c-questions-tp7602690p7602711.html
> Sent
Andreas, are you planning to fix the bug in the future version?
Thanks,
Sergejs.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/SASL-proton-c-questions-tp7602690p7602711.html
Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
Am 14.01.2014 um 16:00 schrieb Rafael Schloming :
> The SASL header looks
> to start where you see the sequence "...AMQP\x03\x01...". This either means
> that proton's internal buffers are getting messed up somehow, or there
> actually is garbage on the wire.
Just checked with iAmqpDecode. It se
Raf,
you had given me a patch for this, as i had the same issue a while ago. Will
see if i can find it..
Alex
On 14 Ιαν 2014, at 5:00 μ.μ., Rafael Schloming
mailto:r...@alum.mit.edu>> wrote:
On Tue, Jan 14, 2014 at 9:44 AM, Andreas Mueller
mailto:a...@iit.de>> wrote:
Disabling SASL should b
On Tue, Jan 14, 2014 at 9:44 AM, Andreas Mueller wrote:
> Disabling SASL should be an option in proton to connect to simple services
> that do not provide SASL or just to skip this additional step if SASL is
> not requires.
>
Agreed, feel free to file a JIRA if we don't already have one.
>
> T
Disabling SASL should be an option in proton to connect to simple services that
do not provide SASL or just to skip this additional step if SASL is not
requires.
The other problem was already reported from Sergey.
I receive a SASL protocol header and a SASL Init message with mechanism PLAIN
fr
Hi,
Messenger will simply use anonymous if you don't specify a username and
password, e.g. amqp://broker/node will result in the client forcing
ANONYMOUS. If you do specify a username and password, e.g.
amqp://user:pass@broker/node, then messenger will force PLAIN. There is no
way to disable SASL