Bug 890931 - Must set NSS_SSL_CBC_RANDOM_IV=0 for pidgin-sipe to work with ms ocs
Must set NSS_SSL_CBC_RANDOM_IV=0 for pidgin-sipe to work with ms ocs
Status: CLOSED DUPLICATE of bug 770682
Product: Fedora
Classification: Fedora
Component: pidgin-sipe (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Stefan Becker
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-12-31 03:50 EST by birger
Modified: 2012-12-31 04:03 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-12-31 04:03:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description birger 2012-12-31 03:50:42 EST
Description of problem:
After upgrade to Fedora 18 pidgin-sipe stopped working

Version-Release number of selected component (if applicable):
All versions on Fedora 18

How reproducible:
Always fails

Steps to Reproduce:
1. start pidgin with a MS OCS account defined
Actual results:
Cannot connect to server

Expected results:

Additional info:
Setting NSS_SSL_CBC_RANDOM_IV=0 before starting pidgin fixs the problem. Is it possible to do the equivalent from within the plugin? Or does it have to be handled at the SSL library?
Comment 1 Stefan Becker 2012-12-31 04:03:42 EST
The bug is on Microsoft side, not pidgin-sipe, Pidgin nor NSS. It seems that Microsoft does have an update for their SSL code, because for some servers/accounts disabling the NSS security fix is no longer necessary.

Pidgin does not have an API to disable NSS security fix per plugin/SSL connection, so this can't be implemented in the plugin.

The only option to get this working without the environment variable would be to re-introduce the same patch to NSS which was used in F15/F16/F17.

*** This bug has been marked as a duplicate of bug 770682 ***

Note You need to log in before you can comment on or make changes to this bug.