Ok, here i go, i downloaded pidgin from original web and sipe from their web too.
This procedure does not adjust to the procedures folllowed by openbsd but, its valid to get pidgin / sipe working =) Pidgin pidgin-2.10.9 from https://pidgin.im/download/ Sipe 1.18.2 from http://sourceforge.net/projects/sipe/files/sipe/pidgin-sipe-1.18.2/pidgin-sip e-1.18.2.tar.gz/download For making pidgin: $ ./configure --disable-farstream --disable-vv --disable-nm --with-nss --with-openssl --disable-tcl $ gmake $ sudo gmake install (you can tune your installation with prefix env) For making sipe $ ./configure --enable-openssl --enable-nss --enable-debug $ gmake $ sudo gmake install (you can tune your installation with prefix env) HTH Regards Saludos.- Leonardo Santagostini <http://ar.linkedin.com/in/santagostini> 2014-09-27 14:34 GMT-03:00 Leonardo Santagostini <lsantagost...@gmail.com>: > Later i will write the issue. But is before openssl/libressl switch and > its related to use nss libs instead ssl. And pidgin is ssilently refusing > server certs. > > But later i will write it more deeper with some debug. I have pidgin / > sipe working without issues > > Regards > El sep 27, 2014 1:37 p.m., "Alexander Hall" <alexan...@beard.se> escribió: > > On 09/26/14 11:55, Mattieu Baptiste wrote: >> >>> On Fri, Sep 26, 2014 at 10:49 AM, Alexander Hall <alexan...@beard.se >>> <mailto:alexan...@beard.se>> wrote: >>> >>> Hi! >>> >>> I'm trying to set up Pidgin to talk to our Lync servers at work, but >>> it >>> seems somewhere after (or in) the TLS handshaking, it just stops, and >>> eventually times out. >>> >>> I installed the pidgin-sipe package and I'm using the 'office >>> communicator' protocol. On a Debian box on the side, with the same >>> settings, I don't have this issue. >>> >>> Can someone please share success stories, non-success stories, or >>> useful >>> hints of using Pidgin for Lync on OpenBSD? >>> >>> >>> Hi, >>> >>> I've also failed at using Pidgin with Office 365. I tried different >>> settings with the pidgin-sipe port, without success. >>> I found a workaround with chrome (+ extension to change the user-agent) >>> and Outlook web access. It let me use the Lync web client. >>> >> >> Just to rule one possibiliy out... Was this before or after the >> separation from upstream openssl? >> >> /Alexander >> >> >>> Regards, >>> -- >>> Mattieu Baptiste >>> "/earth is 102% full ... please delete anyone you can."
