Share

Pidgin-Encryption

Tracker: Bugs

5 Can't send encrypted messages over AIM anymore - ID: 1812207
Last Update: Comment added ( mikeycooper )

Starting yesterday, a friend was unable to communicate with anyone
encrypted. Any time anyone sent her a message, she only received the "***
Encrypted with the Gaim-Encryption plugin" message. I was able to
communicate encrypted with others fine. This morning, myself and 5 other
people who use gaim-encryption were all unable to talk amongst each other.
The logs seem to show me sending the "Send Key" request (71 bytes
received), but on the receiving end, the anchor tag is stripped out (46
bytes received).


Mikey Cooper ( mikeycooper ) - 2007-10-12 12:17

5

Closed

Invalid

Bill Tompkins

None

None

Public


Comments ( 17 )

Date: 2008-03-01 11:16
Sender: mikeycooper


Workaround not needed anymore. Closing.


Date: 2008-03-01 00:17
Sender: youngmug


Some thoughts:

- Is this workaround still needed? I'm not seeing the issue anymore (which
makes me suspect there were problems on the AOL servers), and having
incompatible methods is a bad idea at the moment.

- If it is thought advantageous to have a protocol that won't break when
HTML is stripped, it might be worth setting up some kind of fallback so new
versions can still communicate on the old protocol if the other side is
using an older version, or if they get a message using the old protocol.


Date: 2007-10-27 13:14
Sender: mikeycooper


Yesterday afternoon, encryption started working again for me. I'm still
hoping for a new version with headers that will work if/when aim decides to
start stripping the empty anchor tags again.


Date: 2007-10-26 02:49
Sender: oboboProject Admin


Current SVN has a change to the headers used with the AIM protocol, which
provides a fix. However, it is not compatible with previous versions of
the plugin when used with AIM.

If I can't find a way to make it backwards compatible as well, I'll
release it as 3.1 this weekend.

-Bill


Date: 2007-10-25 21:07
Sender: joecwik


I'm running
Pidgin 2.2.2 with pidgin-encryption 3.0 on Windows, and I'm getting the
same thing as everyone else.


Date: 2007-10-25 19:26
Sender: chingadero


same problem here:
64.12.160.141:5190 ESTABLISHED13100/pidgin
205.188.153.2:5190 ESTABLISHED13100/pidgin
64.12.30.60:5190 ESTABLISHED13100/pidgin
64.12.24.104:5190 ESTABLISHED13100/pidgin
64.12.201.42:5190 ESTABLISHED13100/pidgin


Date: 2007-10-25 17:43
Sender: tnarb


Interesting. Here are the servers I'm currently using.

C:\Documents and Settings\brant>netstat -n -p tcp | find "5190"
TCP 192.168.69.123:1628 205.188.13.44:5190 ESTABLISHED
TCP 192.168.69.123:2698 205.188.9.157:5190 ESTABLISHED
TCP 192.168.69.123:2718 205.188.248.146:5190 ESTABLISHED




Date: 2007-10-25 17:32
Sender: drewgiefly


It definitely looks like an AIM server issue, however it only seems to
affect specific servers. I don't know how AIM handles connections, but it
seems as though a screen name is attached to a single specific server that
does not change often (at least my connection has not changed in the past
24 hours). At my workplace most folks are not having any issues; we are
all connecting to different servers and mine seems to be one of the lucky
ones where the encryption does not work. This same situation happened to
me a couple of weeks ago, when this issue was first reported. If any more
information is needed I'd be glad to provide it. Unfortunately it looks
like this might be outside of the Pidgin-Encryption code itself.


Date: 2007-10-25 13:41
Sender: tnarb


Several people I know, including myself, are experiencing this same issue
again today. If more information is required, please let me know.

Thanks!

-brant


Date: 2007-10-24 12:20
Sender: mikeycooper


This started happening again yesterday to a few of the people on my
buddylist and now today to everyone, including myself.


Date: 2007-10-22 00:59
Sender: oboboProject Admin


Yes, this issue was caused by some changes in the AIM servers, and seems
to be resolved at this point. If anyone is still seeing this problem,
please let me know.

Thanks,

-Bill


Date: 2007-10-13 00:17
Sender: mikeycooper


Issue resolved itself this afternoon. Everyone I've tried speaking to
that was having the issue no longer seems to be having it.


Date: 2007-10-12 14:37
Sender: saberspark77


Right, version 2.2.1 and p-e version 3.0 in Vista.


Date: 2007-10-12 14:35
Sender: saberspark77


My friend and I were having no trouble using encryption last night until
3AM. When we woke at 10AM, we were experiencing the same issues. Neither
of us could have encryption turned on without receiving "*** Encrypted with
the Gaim-Encryption plugin" on the receiving end and "Requesting key..." on
the other.

We attempted updates to pidgin, reinstallation of pidgin-encryption, and
forced key updates via deletion as potential solutions, none of which were
effective.


Date: 2007-10-12 14:35
Sender: rjcarroll4


I'm noticing the same problem, starting today (October 12). I'm running
Pidgin 2.2.1 with pidgin-encryption 3.0 on Windows.


Date: 2007-10-12 12:54
Sender: brc64


We use the pidgin encryption plugin for internal office communication over
AIM, and starting on the 10th we started having similar problems. First it
was just one machine, then yesterday it happened to several more. I
thought maybe Windows Updates may have been the cause, but then I saw one
machine break before my eyes (the conversation started out okay, then all
of the sudden everything was "Requesting key" or "*** Encrypted with the
Gaim-Encryption plugin")

Could AOL be doing something that would prevent this from working?


Date: 2007-10-12 12:19
Sender: mikeycooper


File Added: receiver-purple-debug.log


Attached Files ( 2 )

Filename Description Download
sender-purple-debug.log The log from me trying to send an encrypted message Download
receiver-purple-debug.log The log when she received my encrypted message. Download

Changes ( 14 )

Field Old Value Date By
status_id Open 2008-03-01 11:16 mikeycooper
close_date - 2008-03-01 11:16 mikeycooper
resolution_id None 2008-03-01 11:16 mikeycooper
resolution_id Out of Date 2007-10-26 02:49 obobo
status_id Pending 2007-10-24 12:20 mikeycooper
close_date 2007-10-22 00:59 2007-10-24 12:20 mikeycooper
close_date 2007-10-13 00:17 2007-10-22 00:59 obobo
status_id Closed 2007-10-22 00:59 obobo
resolution_id None 2007-10-22 00:59 obobo
assigned_to nobody 2007-10-22 00:59 obobo
close_date - 2007-10-13 00:17 mikeycooper
status_id Open 2007-10-13 00:17 mikeycooper
File Added 249374: receiver-purple-debug.log 2007-10-12 12:19 mikeycooper
File Added 249373: sender-purple-debug.log 2007-10-12 12:17 mikeycooper