GnuTLS error (I think). Connecting through proxy to office communicator
Hello, I'm trying to use pidgin to connect to our office communicator server. I have to use a proxy. This problem shows up when I first start pidgin, and through a day or so of trial and error, I connected once, but I think that was a fluke because I couldn't connect on the restart, and following the steps I had just taken didn't make any difference (I deleted everything in my .pudgin/certificates folder). Versions: Pidgin: 2.6.6 libpurple: 2.6.6 gnutls: 2.4.1 pidgin-sipe: 1.11.2 or 1.16.1, both built from source. Usually, the main GUI says either Read Error or Write Error. The logs (with PURPLE_GNUTLS_DEBUG=7) show a message like this: (15:22:37) *gnutls:* lvl 7: READ: Got 0 bytes from 14 (15:22:37) *gnutls:* lvl 7: READ: read 0 bytes from 14 (15:22:37) *gnutls:* lvl 7: - (15:22:37) *gnutls:* lvl 2: ASSERT: gnutls_buffers.c:638 (15:22:37) *gnutls:* lvl 3: XXX[]: ret: 0 Success. (15:22:37) *gnutls:* lvl 3: XXX2[]: ret: 0 Success. (15:22:37) *gnutls:* lvl 2: ASSERT: gnutls_record.c:921 (15:22:37) *gnutls:* receive failed: A TLS packet with unexpected length was received. (15:22:37) *connection:* Connection error on 0x2b831d1ec9f0 (reason: 0 description: Read error) or if it's a write error: (15:06:42) gnutls: lvl 7: WRITE: Will write 693 bytes to 15. (15:06:42) gnutls: lvl 2: ASSERT: gnutls_buffers.c:835 (15:06:42) gnutls: lvl 2: ASSERT: gnutls_record.c:460 (15:06:42) gnutls: send failed: Error in the push function. (15:06:42) sipe: transport_canwrite_cb: written = 0, exiting (15:06:42) connection: Connection error on 0x2b9bedc20fd0 (reason: 0 description: Write error) I'm assuming this is my problem. I don't see anything else that's as consistent. Thank you, Jeff ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
Re: GnuTLS error (I think). Connecting through proxy to office communicator
Jeff, Have you been able to reproduce this error on Windows? I used Pidgin + SIPE for years in a Windows and Ubuntu environment without any major issues. The login format was the biggest catch for me. Here are the settings I used: http://i.imgur.com/34SLt2n.png http://i.imgur.com/naF9ZeA.png Also, depending on your build of Linux, you may be able to find precompiled binaries. At the time I wrote my tutorialhttp://tresdev.blogspot.com/2009/08/pidgin-microsoft-office-communicator.htmlthey were all unofficial repos, but it appears most distros have precompiled SIPE binaries now, usually under the package name pidgin-sipe. Alternatively, you may have luck switching from TLS to NTLM or Kerberos, but I was only successful with TLS, which you are already trying. -Tres On Thu, Sep 5, 2013 at 5:45 PM, Jeff Eberl jeffrey.eb...@lmco.com wrote: Hello, I'm trying to use pidgin to connect to our office communicator server. I have to use a proxy. This problem shows up when I first start pidgin, and through a day or so of trial and error, I connected once, but I think that was a fluke because I couldn't connect on the restart, and following the steps I had just taken didn't make any difference (I deleted everything in my .pudgin/certificates folder). Versions: Pidgin: 2.6.6 libpurple: 2.6.6 gnutls: 2.4.1 pidgin-sipe: 1.11.2 or 1.16.1, both built from source. Usually, the main GUI says either Read Error or Write Error. The logs (with PURPLE_GNUTLS_DEBUG=7) show a message like this: (15:22:37) *gnutls:* lvl 7: READ: Got 0 bytes from 14 (15:22:37) *gnutls:* lvl 7: READ: read 0 bytes from 14 (15:22:37) *gnutls:* lvl 7: - (15:22:37) *gnutls:* lvl 2: ASSERT: gnutls_buffers.c:638 (15:22:37) *gnutls:* lvl 3: XXX[]: ret: 0 Success. (15:22:37) *gnutls:* lvl 3: XXX2[]: ret: 0 Success. (15:22:37) *gnutls:* lvl 2: ASSERT: gnutls_record.c:921 (15:22:37) *gnutls:* receive failed: A TLS packet with unexpected length was received. (15:22:37) *connection:* Connection error on 0x2b831d1ec9f0 (reason: 0 description: Read error) or if it's a write error: (15:06:42) gnutls: lvl 7: WRITE: Will write 693 bytes to 15. (15:06:42) gnutls: lvl 2: ASSERT: gnutls_buffers.c:835 (15:06:42) gnutls: lvl 2: ASSERT: gnutls_record.c:460 (15:06:42) gnutls: send failed: Error in the push function. (15:06:42) sipe: transport_canwrite_cb: written = 0, exiting (15:06:42) connection: Connection error on 0x2b9bedc20fd0 (reason: 0 description: Write error) I'm assuming this is my problem. I don't see anything else that's as consistent. Thank you, Jeff ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support -- - tres.finocchi...@gmail.com ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
Re: GnuTLS error (I think). Connecting through proxy to office communicator
*Correction, it appears due to certificate warnings, we switched to using TCP for connection type. From what I remember this was unencrypted, but it fixed the issues were were having at the time. -Tres On Thu, Sep 5, 2013 at 8:08 PM, Tres Finocchiaro tres.finocchi...@gmail.com wrote: Jeff, Have you been able to reproduce this error on Windows? I used Pidgin + SIPE for years in a Windows and Ubuntu environment without any major issues. The login format was the biggest catch for me. Here are the settings I used: http://i.imgur.com/34SLt2n.png http://i.imgur.com/naF9ZeA.png Also, depending on your build of Linux, you may be able to find precompiled binaries. At the time I wrote my tutorialhttp://tresdev.blogspot.com/2009/08/pidgin-microsoft-office-communicator.htmlthey were all unofficial repos, but it appears most distros have precompiled SIPE binaries now, usually under the package name pidgin-sipe. Alternatively, you may have luck switching from TLS to NTLM or Kerberos, but I was only successful with TLS, which you are already trying. -Tres On Thu, Sep 5, 2013 at 5:45 PM, Jeff Eberl jeffrey.eb...@lmco.com wrote: Hello, I'm trying to use pidgin to connect to our office communicator server. I have to use a proxy. This problem shows up when I first start pidgin, and through a day or so of trial and error, I connected once, but I think that was a fluke because I couldn't connect on the restart, and following the steps I had just taken didn't make any difference (I deleted everything in my .pudgin/certificates folder). Versions: Pidgin: 2.6.6 libpurple: 2.6.6 gnutls: 2.4.1 pidgin-sipe: 1.11.2 or 1.16.1, both built from source. Usually, the main GUI says either Read Error or Write Error. The logs (with PURPLE_GNUTLS_DEBUG=7) show a message like this: (15:22:37) *gnutls:* lvl 7: READ: Got 0 bytes from 14 (15:22:37) *gnutls:* lvl 7: READ: read 0 bytes from 14 (15:22:37) *gnutls:* lvl 7: - (15:22:37) *gnutls:* lvl 2: ASSERT: gnutls_buffers.c:638 (15:22:37) *gnutls:* lvl 3: XXX[]: ret: 0 Success. (15:22:37) *gnutls:* lvl 3: XXX2[]: ret: 0 Success. (15:22:37) *gnutls:* lvl 2: ASSERT: gnutls_record.c:921 (15:22:37) *gnutls:* receive failed: A TLS packet with unexpected length was received. (15:22:37) *connection:* Connection error on 0x2b831d1ec9f0 (reason: 0 description: Read error) or if it's a write error: (15:06:42) gnutls: lvl 7: WRITE: Will write 693 bytes to 15. (15:06:42) gnutls: lvl 2: ASSERT: gnutls_buffers.c:835 (15:06:42) gnutls: lvl 2: ASSERT: gnutls_record.c:460 (15:06:42) gnutls: send failed: Error in the push function. (15:06:42) sipe: transport_canwrite_cb: written = 0, exiting (15:06:42) connection: Connection error on 0x2b9bedc20fd0 (reason: 0 description: Write error) I'm assuming this is my problem. I don't see anything else that's as consistent. Thank you, Jeff ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support -- - tres.finocchi...@gmail.com -- - tres.finocchi...@gmail.com ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
