> Read Error
> Pidgin Reason 0 Description Read Error
Pidgin Reason 0 Description Read Error
sudo -e /etc/default/pidgin-sipe Uncomment the line that reads, # export NSS_SSL_CBC_RANDOM_IV=0 (remove the '#' write the file and restart pidgin) share|improve this answer edited Apr 9 '15 at 18:48 answered Apr Changed in pidgin (Ubuntu): status: New → Confirmed Jari Salo (jari-salo) wrote on 2012-03-23: #3 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649456 You can make a workaround by exporting this before starting pidgin: export NSS_SSL_CBC_RANDOM_IV=0 tvicol (tiberiu-vicol) Affecting: pidgin-sipe (Debian) Filed here by: Julian Alarcon When: 2013-03-14 Target Distribution Baltix BOSS Juju Charms Collection Debian Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu You'll have to test both buddy add & remove cases with one run for one of the systest accounts: start with current buddy list remove one buddy add one buddy After news
I don't remember seeing that particular error before. Do we need to create this file? Rob pidgin-git.systest4.anon.log.gz If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Stefan Becker - 2013-06-03 You might want to update Dmitry Veltishev (vdmit) wrote on 2012-07-30: #28 workaround 'export NSS_SSL_CBC_RANDOM_IV=0' works indeed, thanks a lot! https://sourceforge.net/p/sipe/discussion/688534/thread/a415bb16/
Pidgin Sipe Ssl Connection Failed
it seems to solve the "Read error", but I still getting auth error. You seem to have CSS turned off. Is this a related issue or a new one? Please close the ticket.
comment:10 Changed 2 years ago by OmegaPhil I spent more time playing around with the problem - I found that my issue was likely due to bad 'presence' notification from Pidgin Pidgin Sipe Read Error Subscribing... It just makes sure that the remote server doesn't drop the SSL connection. You should check the -debug log, maybe you have choosen the wrong authentication scheme. https://sourceforge.net/p/sipe/bugs/193/ I will deploy it company wide and have it tested by a few hundred users.
Thanks for having a look at the logs! Exiting. (13:25:00) stun: using server (13:25:00) sipe: NTLM MAC(): Extented Session Security (13:25:00) sipe: NTLM MAC(): Key Exchange (13:25:00) sipe: NTLM calculated MAC: 010000003870CEC6F290BE6C64000000 (13:25:00) sipe: SIP transactions count:1 after addition era (era) wrote on 2013-02-20: #32 https://bugzilla.redhat.com/show_bug.cgi?id=770682 alleges that setting NSS_SSL_CBC_RANDOM_IV=0 globally is a security problem. In the meantime if you need any testing done, please let me know.
Pidgin Sipe Read Error
If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Stefan Becker - 2013-02-15 I assume you are talking about Windows http://askubuntu.com/questions/147706/lync-formerly-office-communicator-with-pidgin-sipe-read-error Does anyone know when we´ll have a permanent fix ? Pidgin Sipe Ssl Connection Failed BUT: One thing I've noticed is that the new version doesn't poll a newly added Buddy's contact information from Lync any more; I add a new buddy by entering the sip Glib G_hash_table_destroy Assertion Hash_table Null Failed My Empathy connected to Microsoft Communications Server is working again.
Whatever you decide to name it be sure it's file extension is .sh so that it will be recognized as a script file. http://setiweb.org/read-error/pc-read-error.php This could be related to another bug, but it started when I started using this fix. Please don't fill out this field. If the pidgin ask you accept the certificate while connecting, click NO and it will look for a new certicate or new cert server. Nss_ssl_cbc_random_iv
comment:4 Changed 6 years ago by trac-robot Status changed from pending to closed This ticket was closed automatically by the system. Following is the pidgin debug log for me... (10:34:06) prefs: Reading /home/mitza/.purple/prefs.xml (10:34:06) prefs: Finished reading /home/mitza/.purple/prefs.xml (10:34:06) prefs: purple_prefs_get_path: Unknown pref /pidgin/browsers/command (10:34:06) dbus: okkk (10:34:06) plugins: probing /usr/lib/pidgin/gestures.so (10:34:06) Forum: Help Creator: Eric Munson Created: 2012-04-04 Updated: 2013-03-28 Eric Munson - 2012-04-04 I can get sipe to connect to the OCS server and load my contact list. It even lets More about the author Does someone know a windows fix?
Comment 3 Stefan Becker 2012-12-18 14:06:37 EST That means that a) you are connecting to one of the OCS/Lync servers that hasn't been upgrade to the latest Microsoft SSL code [e.g. This happens whenever I use msn to message someone, pidgin disconnects from the hotmail server and I get the above error notice. We have not had user complaints about new issues which means that things usually work.
Note You need to log in before you can comment on or make changes to this bug.
Titantux (israel-m-dj) wrote on 2012-05-01: #13 It works the workaround for me too!! Thanks, Rob If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Stefan Becker - 2013-05-10 Just to clarify: only the It should not hurt if /usr/local/bin/pidgin remains in use even once a proper fix is deployed, assuming you have a modicum of trust for your local environment (and if not, you This information was last pulled 1 hour ago.
Man, going from pidgin to empathy really makes me miss pidgin. Thus at re-subscription timeout SIPE only resubscribes to the new buddy, but not the old ones anymore. Disconnect @ around 2:15 and then 2:20 again comment:3 Changed 6 years ago by gabr10 Status changed from pending to new Attachment (purple-debug2.log) added by ticket reporter. click site All Rights Reserved.
Thanks for your time! Funny that it seemed to work OK in testing. Please try commit 0c70477. Here are the possible root causes I'm currently considering: keep-alive timeout X means we should send keep-alive every X-10 (the thing you are trying right now) SIPE sends keep-alive every X,
For this particular issue you would add the following line to your .sh file: export NSS_SSL_CBC_RANDOM_IV=0 Once your added this file and the above line to this file, just reboot your I reverted to the old 3.12 series nss packages, rebuilt SIPE with the keepalive timeout changes (timeout-=20) and restarted the test clients. comment:7 Changed 6 years ago by trac-robot Status changed from pending to closed This ticket was closed automatically by the system. Two test accounts (systest2 and systest4) have very limited buddy lists and they have each other and themselves added as buddies.
cheers, Rob pidgin-git.systest.tar.gz If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Stefan Becker - 2013-05-18 Your log now shows I will report back in a few days if we experience any issues. thefuzz4 (jason-hamilton) wrote on 2012-04-23: #9 I also can verify that the work around as stated above does work. Last edit: Stefan Becker 2013-05-01 If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Stefan Becker - 2013-05-01 I took
Dang. I managed to break it. Please only re-open it, if you can provide a --debug log that proves that your problem is not caused by NSS.