Bug#716951: pidgin-sipe: #649456 cannot be worked around with NSS_SSL_CBC_RANDOM_IV=0 since 1.16.0-1

2013-07-15 Thread Joseph Price
Package: pidgin-sipe Version: 1.16.0-1 Severity: important After upgrading to 1.16.0-1 a read error disconnection is again given when attempting to connect to my Microsoft Lync server. With or without the NSS_SSL_CBC_RANDOM_IV=0 variable set. Downgrading back to 1.13.3-1 allows me to connect

Bug#716951: pidgin-sipe: #649456 cannot be worked around with NSS_SSL_CBC_RANDOM_IV=0 since 1.16.0-1

2013-07-15 Thread Jakub Adam
Hi, On 15.7.2013 11:33, Joseph Price wrote: After upgrading to 1.16.0-1 a read error disconnection is again given when attempting to connect to my Microsoft Lync server. With or without the NSS_SSL_CBC_RANDOM_IV=0 variable set. I've just checked and setting NSS_SSL_CBC_RANDOM_IV=0 works

Bug#716951: pidgin-sipe: #649456 cannot be worked around with NSS_SSL_CBC_RANDOM_IV=0 since 1.16.0-1

2013-07-15 Thread Joseph Price
Well that's annoying... I've attached the log. On 15 July 2013 10:56, Jakub Adam jakub.a...@ktknet.cz wrote: Hi, On 15.7.2013 11:33, Joseph Price wrote: After upgrading to 1.16.0-1 a read error disconnection is again given when attempting to connect to my Microsoft Lync server. With or

Bug#716951: pidgin-sipe: #649456 cannot be worked around with NSS_SSL_CBC_RANDOM_IV=0 since 1.16.0-1

2013-07-15 Thread Jakub Adam
Hi, On 15.7.2013 12:06, Joseph Price wrote: Well that's annoying... I've attached the log. I suspect you are affected by issue described in SIPE FAQ[1]. From the log I see you are using NTLM authentication and your Single Sign-On is enabled. This configuration is not supported and you have

Bug#716951: pidgin-sipe: #649456 cannot be worked around with NSS_SSL_CBC_RANDOM_IV=0 since 1.16.0-1

2013-07-15 Thread Joseph Price
This does indeed fix the issue. Sorry for not having seen that myself! On 15 July 2013 12:07, Jakub Adam jakub.a...@ktknet.cz wrote: Hi, On 15.7.2013 12:06, Joseph Price wrote: Well that's annoying... I've attached the log. I suspect you are affected by issue described in SIPE FAQ[1].