Pidgin & TRM Runes

While trying to configure pidgin to act as a console for TRM once known as Reuters’ Messenger, I came across this page at their sourceforge site which documents the magic runes, critically the User Name.

Yes, me. Since version 1.3.4

Params: Anvanced tab: nothing basically. Connection type – auto. UNCHECK “Use Single Sign-On” (!) Otherwise it’ll use your Windows Domain credentials with Reuters network, which is rather incorrect.

Basic tab:
Username: first.last.company.com@reuters.net
Login: first.last@company.com

(Username is basically derived from the login name by replacing @ to dot and then adding @reuters.net)
Don’t forget that you may have unique password in Reuters network, not the same as your PC/Domain password.

They both tightened up on their SSL management , this page refers.

…..there have been considerable changes to the SSL handling in the NSS module. One part of them seems to be that the default for SSL cipher suites now follows the recommendation to disable known unsecure suites, e.g. that use RC4.

You can change the settings with Tools -> Plugins -> NSS Preferences. On my company account, which is a OCS2007 installation, I needed to enable at least TLS_RSA_WITH_RC4_128_SHA or TLS_RSA_WITH_RC4_128_MD5 before SSL connections went through again.

However, don’t forget to keep your SIPE libraries up to date!

Musings on O356

So work is pushing me to Office 365; it wouldn’t surprise me if the next home system does so too. I have decided to see if W7 and a more modern hardware makes OWA easier to use. I have had to upgrade my phone since my current one was very old, and they didn’t want to support BB6. Microsoft have also bought Yammer and Skype recently and launched Lync as part of the desktop; so everyone needs a clear road map. I shall start with the view that I should use Lync for chat and Yammer for micro-blogging inside the company. Obviously, outside the company I shall continue to use what people read/reply to. An interesting insight, inside a company managers can declare use policies that have a chance of sticking, but it’s not guarenteed.

So can pidgin act as a Lync chat client? Here’s the google search, here’s the pidgin plugins home page., it seems SIPE is the keyword, and the pidgin page says it’ll support TRM as well as implying it’ll support Lync although it seems designed for MS Office Communicator.

So, here’s the SIPE code, http://sourceforge.net/projects/sipe/, it’s an NSIS install on Windows, think I had to reboot windows to see the “Office Communicator” option. The configuration runes are documented on this page, which is part of the O365 community site. DFL 9th Oct 2014

Google Talk

I first attempted this in August 2008. I have successfully configured Pidgin 2.0.1 to act as a client although in one case I have two channels between me and my correspondent. One of the reasons was to have a second XMPP chat service to test my problems with Pidgin and my work’s XMPP server. See Pidgin on this site, and I have written this up on my old Sun blog, at an article called google talk and pidgin, published on 10th October 2008. Continue reading “Google Talk”

Pidgin

Meta

I have been using Pidgin as a multi-protocol client for my instant messenger services since about 2008. The contents of this page originally relate to problems I was having with pidgin on a windows system. It was written in the Autumn of 2008 and both windows and pidgin have had many new releases or updates since then. I can’t imagine that it remains of much use. i.e. this page is out of date and not very useful now. I recognised on copying the page from its source that the page required amendment so in Dec 2014, I needed to document the installation of themes I moved the 2008 content to the comments section.

Themes

In 2014, as we had moved on from Windows XP, the theme management features of Pidgin became attractive to allow it to fit in more easily.

One approach is to edit the GTK preferences, document on this page,

and/or to install new bubbles and smilies from

One needs to be careful how one unpacks these, the themes need to have the correct name hierarchy, i.e. %appdata%\.purple\themes\${Theme Name}\purple\*, some installation techniques may leave one with the theme name reepated twice.

Protocol Helpers

Lync & TRM need SIPE, available at http://sourceforge.net/projects/sipe/, when installing this using the NSIS installer, this worked fine, as you’d expect since there’s little google evidence that it doesn’t.

Skype needs its own plugin