Pidgin Proxy servers

[Leon Goldstein]

Compliance=  we us a third party service to capture all instant messages and it works by assigning a proxy.


Leon Goldstein
Principal

[cid:image001.gif at 01CC9361.1135C8B0]




New York Office
One Penn Plaza
36th Floor
New York, NY  10119
NY:  212.457.5000

Operations Center
9 North Main Street
Suite 3
Marlboro, NJ 07746
NJ:   732.972.3396

Customer Service
866.586.TECH (8324)

lgoldstein at innervisionit.com<x-msg://62/lgoldstein@innervisionit.com>
http://www.innervisionit.com<http://www.innervisionit.com/>




On Nov 28, 2012, at 2:15 PM, David Woolley <forums at david-woolley.me.uk<mailto:forums at david-woolley.me.uk>> wrote:

Leon Goldstein wrote:
We are adding compliance of IM for our clients and our compliance
company is stating that pidgin does not work well with proxy servers.

I didn't understand "compliance" on the first reading.  The question was
compliance with what?  I presume you mean some financial trading rules
that require all communications to be logged, and not the payment card
industry rules that require some things should never be logged!

I wonder if the issue with Pidgin is that, being a multi-protocol
client, some of the protocols won't be known to the man in the middle
software, and the security architecture of some of them may be badly
compromised even though the user is aware of the man in the middle, e.g.
login credentials may be compromised.

--
David Woolley
Emails are not formal business letters, whatever businesses may want.
RFC1855 says there should be an address here, but, in a world of spam,
that is no longer good advice, as archive address hiding may not work.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/support/attachments/20121128/7a7bb41c/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2490 bytes
Desc: image001.gif
URL: <http://pidgin.im/pipermail/support/attachments/20121128/7a7bb41c/attachment-0002.gif>