From stormrider01 at gmail.com Sun Jan 9 16:17:25 2011 From: stormrider01 at gmail.com (Sean Lively) Date: Sun, 9 Jan 2011 14:17:25 -0700 Subject: [OTR-users] Pidgin-otr 3.2.0 "was not encrypted:" fails to generate a new alert In-Reply-To: References: Message-ID: If I have an existing encrypted conversation, and the other party disconnects/reboots/ect, and then sends a new message, I don't get a new message alert in Pidgin. When I happen to look at that message tab, I'll see: The following message received from user at hotmail.com was not encrypted: [hey] as a green system alert type of message. this is eventually followed up with an angry email/phone call because I'm ignoring someone on IM. Any ideas? I'm using Pidgin 2.7.7 on Win7 x64 From nelson at bolyard.me Sun Jan 9 16:29:34 2011 From: nelson at bolyard.me (Nelson B Bolyard) Date: Sun, 09 Jan 2011 13:29:34 -0800 Subject: [OTR-users] OTR Proxy vs AIM 7 ? Message-ID: <4D2A28BE.1010405@bolyard.me> I'm trying to get OTR Proxy to work with AIM 7 on WinXP SP3. No Joy. OTR starts OK and displays its window. It's bound to the expected ports. I've configured AIM7 to use http/https proxy on port 8080. When I attempt to login, it first says "connecting", then "configuring", then "Connection error. Please try signing on again. Try Auto Configure or change your settings manually." It never succeeds with the proxy, but never fails without the proxy. I'm looking for help. Here's a capture of the connections between the AIM client and the proxy. Hopefully someone on this list can compare this with the expected behavior. I notice that the client always closes the connection after one request/response pair, even when the client has requested keep-alive. Connections 5, 6 and 7 appear to be a repeat of connections 2, 3, and 4, except that in connection 7, the client drops the connection after sending the request, before the server answers. Any ideas what's wrong? > Connection #1 [Sun Jan 09 12:55:22 2011] > Connected to localhost:8080 > --> [ > 0: 47 45 54 20 68 74 74 70 3a 2f 2f 61 69 6d 68 74 | GET http://aimht > 10: 74 70 2e 6f 73 63 61 72 2e 61 6f 6c 2e 63 6f 6d | tp.oscar.aol.com > 20: 2f 68 65 6c 6c 6f 20 48 54 54 50 2f 31 2e 31 0d | /hello HTTP/1.1. > 30: 0a 43 61 63 68 65 2d 43 6f 6e 74 72 6f 6c 3a 20 | .Cache-Control: > 40: 6e 6f 2d 73 74 6f 72 65 20 6e 6f 2d 63 61 63 68 | no-store no-cach > 50: 65 0d 0a 50 72 61 67 6d 61 3a 20 6e 6f 2d 63 61 | e..Pragma: no-ca > 60: 63 68 65 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a | che..User-Agent: > 70: 20 4d 6f 7a 69 6c 6c 61 2f 34 2e 30 38 20 5b 65 | Mozilla/4.08 [e > 80: 6e 5d 20 28 57 69 6e 4e 54 3b 20 55 20 3b 4e 61 | n] (WinNT; U ;Na > 90: 76 29 0d 0a 63 6f 6e 6e 65 63 74 69 6f 6e 3a 20 | v)..connection: > a0: 6b 65 65 70 2d 61 6c 69 76 65 0d 0a 48 6f 73 74 | keep-alive..Host > b0: 3a 20 61 69 6d 68 74 74 70 2e 6f 73 63 61 72 2e | : aimhttp.oscar. > c0: 61 6f 6c 2e 63 6f 6d 0d 0a 0d 0a | aol.com.... > ] > <-- [ > 0: 48 54 54 50 2f 31 2e 30 20 32 30 30 20 4f 4b 0d | HTTP/1.0 200 OK. > 10: 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c 6f | .Connection: clo > 20: 73 65 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 | se..Content-Type > 30: 3a 20 41 49 4d 2f 48 54 54 50 0d 0a 43 61 63 68 | : AIM/HTTP..Cach > 40: 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e 6f 2d 63 61 | e-Control: no-ca > 50: 63 68 65 20 6e 6f 2d 73 74 6f 72 65 0d 0a 43 6f | che no-store..Co > 60: 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 34 31 | ntent-Length: 41 > 70: 0d 0a 0d 0a 00 27 04 43 00 02 00 00 00 00 00 01 | .....'.C........ > 80: 8f 0d ff 6d a8 34 e4 54 0b 70 c8 7a 8f 35 cd 92 | ...m.4.T.p.z.5.. > 90: 00 09 31 32 37 2e 30 2e 30 2e 31 00 50 | ..127.0.0.1.P > ] > Read EOF on Client socket. [Sun Jan 09 12:55:22 2011] > Read EOF on Server socket. [Sun Jan 09 12:55:22 2011] > Connection 1 Complete [Sun Jan 09 12:55:22 2011] > Connection #2 [Sun Jan 09 12:55:22 2011] > Connected to localhost:8080 > --> [ > 0: 50 4f 53 54 20 68 74 74 70 3a 2f 2f 31 32 37 2e | POST http://127. > 10: 30 2e 30 2e 31 2f 64 61 74 61 3f 73 69 64 3d 38 | 0.0.1/data?sid=8 > 20: 66 30 64 66 66 36 64 61 38 33 34 65 34 35 34 30 | f0dff6da834e4540 > 30: 62 37 30 63 38 37 61 38 66 33 35 63 64 39 32 26 | b70c87a8f35cd92& > 40: 73 65 71 3d 31 20 48 54 54 50 2f 31 2e 31 0d 0a | seq=1 HTTP/1.1.. > 50: 43 61 63 68 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e | Cache-Control: n > 60: 6f 2d 73 74 6f 72 65 20 6e 6f 2d 63 61 63 68 65 | o-store no-cache > 70: 0d 0a 50 72 61 67 6d 61 3a 20 6e 6f 2d 63 61 63 | ..Pragma: no-cac > 80: 68 65 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 20 | he..User-Agent: > 90: 4d 6f 7a 69 6c 6c 61 2f 34 2e 30 38 20 5b 65 6e | Mozilla/4.08 [en > a0: 5d 20 28 57 69 6e 4e 54 3b 20 55 20 3b 4e 61 76 | ] (WinNT; U ;Nav > b0: 29 0d 0a 63 6f 6e 6e 65 63 74 69 6f 6e 3a 20 6b | )..connection: k > c0: 65 65 70 2d 61 6c 69 76 65 0d 0a 43 6f 6e 74 65 | eep-alive..Conte > d0: 6e 74 2d 4c 65 6e 67 74 68 3a 20 33 33 0d 0a 48 | nt-Length: 33..H > e0: 6f 73 74 3a 20 31 32 37 2e 30 2e 30 2e 31 0d 0a | ost: 127.0.0.1.. > f0: 0d 0a 00 1f 04 43 00 03 00 00 00 00 00 00 00 01 | .....C.......... > 100: 00 0f 6b 64 63 2e 75 61 73 2e 61 6f 6c 2e 63 6f | ..kdc.uas.aol.co > 110: 6d 01 bb | m.. > ] > <-- [ > 0: 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d | HTTP/1.1 200 OK. > 10: 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c 6f | .Connection: clo > 20: 73 65 0d 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 | se..Content-Leng > 30: 74 68 3a 20 30 0d 0a 0d 0a | th: 0.... > ] > Read EOF on Client socket. [Sun Jan 09 12:55:22 2011] > Read EOF on Server socket. [Sun Jan 09 12:55:22 2011] > Connection 2 Complete [Sun Jan 09 12:55:22 2011] > Connection #3 [Sun Jan 09 12:55:22 2011] > Connected to localhost:8080 > --> [ > 0: 47 45 54 20 68 74 74 70 3a 2f 2f 31 32 37 2e 30 | GET http://127.0 > 10: 2e 30 2e 31 2f 6d 6f 6e 69 74 6f 72 3f 73 69 64 | .0.1/monitor?sid > 20: 3d 38 66 30 64 66 66 36 64 61 38 33 34 65 34 35 | =8f0dff6da834e45 > 30: 34 30 62 37 30 63 38 37 61 38 66 33 35 63 64 39 | 40b70c87a8f35cd9 > 40: 32 20 48 54 54 50 2f 31 2e 31 0d 0a 43 61 63 68 | 2 HTTP/1.1..Cach > 50: 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e 6f 2d 73 74 | e-Control: no-st > 60: 6f 72 65 20 6e 6f 2d 63 61 63 68 65 0d 0a 50 72 | ore no-cache..Pr > 70: 61 67 6d 61 3a 20 6e 6f 2d 63 61 63 68 65 0d 0a | agma: no-cache.. > 80: 55 73 65 72 2d 41 67 65 6e 74 3a 20 4d 6f 7a 69 | User-Agent: Mozi > 90: 6c 6c 61 2f 34 2e 30 38 20 5b 65 6e 5d 20 28 57 | lla/4.08 [en] (W > a0: 69 6e 4e 54 3b 20 55 20 3b 4e 61 76 29 0d 0a 63 | inNT; U ;Nav)..c > b0: 6f 6e 6e 65 63 74 69 6f 6e 3a 20 6b 65 65 70 2d | onnection: keep- > c0: 61 6c 69 76 65 0d 0a 48 6f 73 74 3a 20 31 32 37 | alive..Host: 127 > d0: 2e 30 2e 30 2e 31 0d 0a 0d 0a | .0.0.1.... > ] > <-- [ > 0: 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d | HTTP/1.1 200 OK. > 10: 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c 6f | .Connection: clo > 20: 73 65 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 | se..Content-Type > 30: 3a 20 41 49 4d 2f 48 54 54 50 0d 0a 43 6f 6e 74 | : AIM/HTTP..Cont > 40: 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 31 35 0d 0a | ent-Length: 15.. > 50: 0d 0a 00 0d 04 43 00 04 00 00 00 00 00 00 00 01 | .....C.......... > 60: fc | . > ] > Read EOF on Client socket. [Sun Jan 09 12:55:22 2011] > Read EOF on Server socket. [Sun Jan 09 12:55:22 2011] > Connection 3 Complete [Sun Jan 09 12:55:22 2011] > Connection #4 [Sun Jan 09 12:55:22 2011] > Connected to localhost:8080 > --> [ > 0: 47 45 54 20 68 74 74 70 3a 2f 2f 31 32 37 2e 30 | GET http://127.0 > 10: 2e 30 2e 31 2f 6d 6f 6e 69 74 6f 72 3f 73 69 64 | .0.1/monitor?sid > 20: 3d 38 66 30 64 66 66 36 64 61 38 33 34 65 34 35 | =8f0dff6da834e45 > 30: 34 30 62 37 30 63 38 37 61 38 66 33 35 63 64 39 | 40b70c87a8f35cd9 > 40: 32 20 48 54 54 50 2f 31 2e 31 0d 0a 43 61 63 68 | 2 HTTP/1.1..Cach > 50: 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e 6f 2d 73 74 | e-Control: no-st > 60: 6f 72 65 20 6e 6f 2d 63 61 63 68 65 0d 0a 50 72 | ore no-cache..Pr > 70: 61 67 6d 61 3a 20 6e 6f 2d 63 61 63 68 65 0d 0a | agma: no-cache.. > 80: 55 73 65 72 2d 41 67 65 6e 74 3a 20 4d 6f 7a 69 | User-Agent: Mozi > 90: 6c 6c 61 2f 34 2e 30 38 20 5b 65 6e 5d 20 28 57 | lla/4.08 [en] (W > a0: 69 6e 4e 54 3b 20 55 20 3b 4e 61 76 29 0d 0a 63 | inNT; U ;Nav)..c > b0: 6f 6e 6e 65 63 74 69 6f 6e 3a 20 6b 65 65 70 2d | onnection: keep- > c0: 61 6c 69 76 65 0d 0a 48 6f 73 74 3a 20 31 32 37 | alive..Host: 127 > d0: 2e 30 2e 30 2e 31 0d 0a 0d 0a | .0.0.1.... > ] > <-- [ > 0: 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d | HTTP/1.1 200 OK. > 10: 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c 6f | .Connection: clo > 20: 73 65 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 | se..Content-Type > 30: 3a 20 41 49 4d 2f 48 54 54 50 0d 0a 43 6f 6e 74 | : AIM/HTTP..Cont > 40: 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 31 35 0d 0a | ent-Length: 15.. > 50: 0d 0a 00 0d 04 43 00 07 00 00 00 00 00 00 00 01 | .....C.......... > 60: 00 | . > ] > Read EOF on Client socket. [Sun Jan 09 12:55:32 2011] > Read EOF on Server socket. [Sun Jan 09 12:55:32 2011] > Connection 4 Complete [Sun Jan 09 12:55:32 2011] > Connection #5 [Sun Jan 09 12:55:32 2011] > Connected to localhost:8080 > --> [ > 0: 50 4f 53 54 20 68 74 74 70 3a 2f 2f 31 32 37 2e | POST http://127. > 10: 30 2e 30 2e 31 2f 64 61 74 61 3f 73 69 64 3d 38 | 0.0.1/data?sid=8 > 20: 66 30 64 66 66 36 64 61 38 33 34 65 34 35 34 30 | f0dff6da834e4540 > 30: 62 37 30 63 38 37 61 38 66 33 35 63 64 39 32 26 | b70c87a8f35cd92& > 40: 73 65 71 3d 32 20 48 54 54 50 2f 31 2e 31 0d 0a | seq=2 HTTP/1.1.. > 50: 43 61 63 68 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e | Cache-Control: n > 60: 6f 2d 73 74 6f 72 65 20 6e 6f 2d 63 61 63 68 65 | o-store no-cache > 70: 0d 0a 50 72 61 67 6d 61 3a 20 6e 6f 2d 63 61 63 | ..Pragma: no-cac > 80: 68 65 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 20 | he..User-Agent: > 90: 4d 6f 7a 69 6c 6c 61 2f 34 2e 30 38 20 5b 65 6e | Mozilla/4.08 [en > a0: 5d 20 28 57 69 6e 4e 54 3b 20 55 20 3b 4e 61 76 | ] (WinNT; U ;Nav > b0: 29 0d 0a 63 6f 6e 6e 65 63 74 69 6f 6e 3a 20 6b | )..connection: k > c0: 65 65 70 2d 61 6c 69 76 65 0d 0a 43 6f 6e 74 65 | eep-alive..Conte > d0: 6e 74 2d 4c 65 6e 67 74 68 3a 20 34 38 0d 0a 48 | nt-Length: 48..H > e0: 6f 73 74 3a 20 31 32 37 2e 30 2e 30 2e 31 0d 0a | ost: 127.0.0.1.. > f0: 0d 0a 00 2e 04 43 00 03 00 00 00 00 00 00 00 02 | .....C.......... > 100: 00 1e 61 69 6d 70 72 6f 2e 70 72 65 6d 69 75 6d | ..aimpro.premium > 110: 73 65 72 76 69 63 65 73 2e 61 6f 6c 2e 63 6f 6d | services.aol.com > 120: 01 bb | .. > ] > <-- [ > 0: 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d | HTTP/1.1 200 OK. > 10: 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c 6f | .Connection: clo > 20: 73 65 0d 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 | se..Content-Leng > 30: 74 68 3a 20 30 0d 0a 0d 0a | th: 0.... > ] > Read EOF on Client socket. [Sun Jan 09 12:55:32 2011] > Read EOF on Server socket. [Sun Jan 09 12:55:32 2011] > Connection 5 Complete [Sun Jan 09 12:55:32 2011] > Connection #6 [Sun Jan 09 12:55:32 2011] > Connected to localhost:8080 > --> [ > 0: 47 45 54 20 68 74 74 70 3a 2f 2f 31 32 37 2e 30 | GET http://127.0 > 10: 2e 30 2e 31 2f 6d 6f 6e 69 74 6f 72 3f 73 69 64 | .0.1/monitor?sid > 20: 3d 38 66 30 64 66 66 36 64 61 38 33 34 65 34 35 | =8f0dff6da834e45 > 30: 34 30 62 37 30 63 38 37 61 38 66 33 35 63 64 39 | 40b70c87a8f35cd9 > 40: 32 20 48 54 54 50 2f 31 2e 31 0d 0a 43 61 63 68 | 2 HTTP/1.1..Cach > 50: 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e 6f 2d 73 74 | e-Control: no-st > 60: 6f 72 65 20 6e 6f 2d 63 61 63 68 65 0d 0a 50 72 | ore no-cache..Pr > 70: 61 67 6d 61 3a 20 6e 6f 2d 63 61 63 68 65 0d 0a | agma: no-cache.. > 80: 55 73 65 72 2d 41 67 65 6e 74 3a 20 4d 6f 7a 69 | User-Agent: Mozi > 90: 6c 6c 61 2f 34 2e 30 38 20 5b 65 6e 5d 20 28 57 | lla/4.08 [en] (W > a0: 69 6e 4e 54 3b 20 55 20 3b 4e 61 76 29 0d 0a 63 | inNT; U ;Nav)..c > b0: 6f 6e 6e 65 63 74 69 6f 6e 3a 20 6b 65 65 70 2d | onnection: keep- > c0: 61 6c 69 76 65 0d 0a 48 6f 73 74 3a 20 31 32 37 | alive..Host: 127 > d0: 2e 30 2e 30 2e 31 0d 0a 0d 0a | .0.0.1.... > ] > <-- [ > 0: 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d | HTTP/1.1 200 OK. > 10: 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c 6f | .Connection: clo > 20: 73 65 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65 | se..Content-Type > 30: 3a 20 41 49 4d 2f 48 54 54 50 0d 0a 43 6f 6e 74 | : AIM/HTTP..Cont > 40: 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 31 35 0d 0a | ent-Length: 15.. > 50: 0d 0a 00 0d 04 43 00 04 00 00 00 00 00 00 00 02 | .....C.......... > 60: fc | . > ] > Read EOF on Client socket. [Sun Jan 09 12:55:32 2011] > Read EOF on Server socket. [Sun Jan 09 12:55:32 2011] > Connection 6 Complete [Sun Jan 09 12:55:32 2011] > Connection #7 [Sun Jan 09 12:55:32 2011] > Connected to localhost:8080 > --> [ > 0: 47 45 54 20 68 74 74 70 3a 2f 2f 31 32 37 2e 30 | GET http://127.0 > 10: 2e 30 2e 31 2f 6d 6f 6e 69 74 6f 72 3f 73 69 64 | .0.1/monitor?sid > 20: 3d 38 66 30 64 66 66 36 64 61 38 33 34 65 34 35 | =8f0dff6da834e45 > 30: 34 30 62 37 30 63 38 37 61 38 66 33 35 63 64 39 | 40b70c87a8f35cd9 > 40: 32 20 48 54 54 50 2f 31 2e 31 0d 0a 43 61 63 68 | 2 HTTP/1.1..Cach > 50: 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e 6f 2d 73 74 | e-Control: no-st > 60: 6f 72 65 20 6e 6f 2d 63 61 63 68 65 0d 0a 50 72 | ore no-cache..Pr > 70: 61 67 6d 61 3a 20 6e 6f 2d 63 61 63 68 65 0d 0a | agma: no-cache.. > 80: 55 73 65 72 2d 41 67 65 6e 74 3a 20 4d 6f 7a 69 | User-Agent: Mozi > 90: 6c 6c 61 2f 34 2e 30 38 20 5b 65 6e 5d 20 28 57 | lla/4.08 [en] (W > a0: 69 6e 4e 54 3b 20 55 20 3b 4e 61 76 29 0d 0a 63 | inNT; U ;Nav)..c > b0: 6f 6e 6e 65 63 74 69 6f 6e 3a 20 6b 65 65 70 2d | onnection: keep- > c0: 61 6c 69 76 65 0d 0a 48 6f 73 74 3a 20 31 32 37 | alive..Host: 127 > d0: 2e 30 2e 30 2e 31 0d 0a 0d 0a | .0.0.1.... > ] > Read EOF on Client socket. [Sun Jan 09 12:55:32 2011] > Read EOF on Server socket. [Sun Jan 09 12:55:32 2011] > Connection 7 Complete [Sun Jan 09 12:55:32 2011] From ian at cypherpunks.ca Sun Jan 9 17:05:09 2011 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sun, 9 Jan 2011 17:05:09 -0500 Subject: [OTR-users] Pidgin-otr 3.2.0 "was not encrypted:" fails to generate a new alert In-Reply-To: References: Message-ID: <20110109220509.GC24435@yoink.cs.uwaterloo.ca> On Sun, Jan 09, 2011 at 02:17:25PM -0700, Sean Lively wrote: > If I have an existing encrypted conversation, and the other party > disconnects/reboots/ect, and then sends a new message, I don't get a > new message alert in Pidgin. When I happen to look at that message > tab, I'll see: > > The following message received from user at hotmail.com was not encrypted: [hey] > > as a green system alert type of message. this is eventually followed > up with an angry email/phone call because I'm ignoring someone on IM. > Any ideas? > I'm using Pidgin 2.7.7 on Win7 x64 Indeed, someone else reported that recently. The trick is to figure out a way to unambiguously show that the message was not encrypted, while allowing Pidgin to treat it as an ordinary (not system) message. - Ian From ian at cypherpunks.ca Sun Jan 9 17:12:46 2011 From: ian at cypherpunks.ca (Ian Goldberg) Date: Sun, 9 Jan 2011 17:12:46 -0500 Subject: [OTR-users] OTR Proxy vs AIM 7 ? In-Reply-To: <4D2A28BE.1010405@bolyard.me> References: <4D2A28BE.1010405@bolyard.me> Message-ID: <20110109221246.GD24435@yoink.cs.uwaterloo.ca> On Sun, Jan 09, 2011 at 01:29:34PM -0800, Nelson B Bolyard wrote: > I'm trying to get OTR Proxy to work with AIM 7 on WinXP SP3. No Joy. > OTR starts OK and displays its window. It's bound to the expected ports. > I've configured AIM7 to use http/https proxy on port 8080. When I attempt > to login, it first says "connecting", then "configuring", then "Connection > error. Please try signing on again. Try Auto Configure or change your > settings manually." It never succeeds with the proxy, but > never fails without the proxy. I'm looking for help. > > Here's a capture of the connections between the AIM client and the proxy. > Hopefully someone on this list can compare this with the expected behavior. > > I notice that the client always closes the connection after one > request/response pair, even when the client has requested keep-alive. > > Connections 5, 6 and 7 appear to be a repeat of connections 2, 3, and 4, > except that in connection 7, the client drops the connection after sending > the request, before the server answers. > > Any ideas what's wrong? First of all, thanks for the great report with data dumps! Unfortunately, there's no one working on otrproxy at the moment. I'm not even sure I could compile it any more. :-( Right now, we're working on libotr, the pidgin plugin, and java-otr. The best I can offer at this time, I'm afraid, is, "if you'd like to figure out what's going on an send in a patch, I'd be happy to apply it". Sorry, - Ian From nelson at bolyard.me Mon Jan 10 00:35:46 2011 From: nelson at bolyard.me (Nelson B Bolyard) Date: Sun, 09 Jan 2011 21:35:46 -0800 Subject: [OTR-users] OTR Proxy vs AIM 7 ? In-Reply-To: <20110109221246.GD24435@yoink.cs.uwaterloo.ca> References: <4D2A28BE.1010405@bolyard.me> <20110109221246.GD24435@yoink.cs.uwaterloo.ca> Message-ID: <4D2A9AB2.8050304@bolyard.me> On 2011-01-09 14:12 PDT, Ian Goldberg wrote: > On Sun, Jan 09, 2011 at 01:29:34PM -0800, Nelson B Bolyard wrote: >> I'm trying to get OTR Proxy to work with AIM 7 on WinXP SP3. No Joy. >> OTR starts OK and displays its window. It's bound to the expected ports. >> I've configured AIM7 to use http/https proxy on port 8080. When I attempt >> to login, it first says "connecting", then "configuring", then "Connection >> error. Please try signing on again. Try Auto Configure or change your >> settings manually." It never succeeds with the proxy, but >> never fails without the proxy. I'm looking for help. >> >> Here's a capture of the connections between the AIM client and the proxy. >> Hopefully someone on this list can compare this with the expected behavior. >> >> I notice that the client always closes the connection after one >> request/response pair, even when the client has requested keep-alive. >> >> Connections 5, 6 and 7 appear to be a repeat of connections 2, 3, and 4, >> except that in connection 7, the client drops the connection after sending >> the request, before the server answers. >> >> Any ideas what's wrong? > > First of all, thanks for the great report with data dumps! > > Unfortunately, there's no one working on otrproxy at the moment. I'm > not even sure I could compile it any more. :-( Right now, we're > working on libotr, the pidgin plugin, and java-otr. > > The best I can offer at this time, I'm afraid, is, "if you'd like to > figure out what's going on an send in a patch, I'd be happy to apply > it". > > Sorry, > > - Ian I'd like to ask a few more questions. - Are there any users on this list successfully using otrproxy with AIM7 on Windows? (If so, please speak up.) - If so, Do those users know of any tricks needed to make it work? - If not, then perhaps the login protocol has changed for AIM7, and the other AIM-compatible clients are all emulating an older AIM version, such as AIM6, AIM5, or even AIM4. Where is the right forum to discuss the AIM login protocol details. otr-dev? elsewhere? -- /Nelson Bolyard From war_is_peace at privatdemail.net Mon Jan 10 13:49:32 2011 From: war_is_peace at privatdemail.net (war_is_peace at privatdemail.net) Date: Mon, 10 Jan 2011 19:49:32 +0100 Subject: [OTR-users] Any Windows binaries of Psi+'s OTR plugin? Message-ID: <4D2B54BC.7040003@privatdemail.net> Hi, as the author of the OTR plugin for Psi+ doesn't plan on releasing his plugin as a Windows binary, maybe someone on this list has successfully compiled it for Windows and would share it? Greetings, Flo From war_is_peace at privatdemail.net Mon Jan 10 13:55:29 2011 From: war_is_peace at privatdemail.net (war_is_peace at privatdemail.net) Date: Mon, 10 Jan 2011 19:55:29 +0100 Subject: [OTR-users] Any Windows binaries of Psi+'s OTR plugin? In-Reply-To: <4D2B54BC.7040003@privatdemail.net> References: <4D2B54BC.7040003@privatdemail.net> Message-ID: <4D2B5621.3020001@privatdemail.net> Including a link to the plugin I'm speaking of might actually be a good idea... http://public.tfh-berlin.de/~s30935/ From paul at cypherpunks.ca Mon Jan 24 19:49:38 2011 From: paul at cypherpunks.ca (Paul Wouters) Date: Mon, 24 Jan 2011 19:49:38 -0500 (EST) Subject: [OTR-users] Pidgin-otr 3.2.0 "was not encrypted:" fails to generate a new alert In-Reply-To: <20110109220509.GC24435@yoink.cs.uwaterloo.ca> References: <20110109220509.GC24435@yoink.cs.uwaterloo.ca> Message-ID: On Sun, 9 Jan 2011, Ian Goldberg wrote: >> The following message received from user at hotmail.com was not encrypted: [hey] >> >> as a green system alert type of message. this is eventually followed >> up with an angry email/phone call because I'm ignoring someone on IM. >> Any ideas? >> I'm using Pidgin 2.7.7 on Win7 x64 > > Indeed, someone else reported that recently. The trick is to figure out > a way to unambiguously show that the message was not encrypted, while > allowing Pidgin to treat it as an ordinary (not system) message. A workaround is to have the remote partner set "require private communications" for you. Paul From Byrd.B at insightcom.com Tue Jan 25 07:45:39 2011 From: Byrd.B at insightcom.com (Byrd, Brendan) Date: Tue, 25 Jan 2011 07:45:39 -0500 Subject: [OTR-users] Pidgin-otr 3.2.0 "was not encrypted:" fails to generate a new alert In-Reply-To: References: <20110109220509.GC24435@yoink.cs.uwaterloo.ca> Message-ID: Doesn't that force all IM conversations to use OTR, even if they don't have it? That's what I thought it was, so I didn't check it. -----Original Message----- From: otr-users-bounces at lists.cypherpunks.ca [mailto:otr-users-bounces at lists.cypherpunks.ca] On Behalf Of Paul Wouters Sent: Monday, January 24, 2011 7:50 PM To: otr-users at lists.cypherpunks.ca Subject: Re: [OTR-users] Pidgin-otr 3.2.0 "was not encrypted:" fails to generate a new alert On Sun, 9 Jan 2011, Ian Goldberg wrote: >> The following message received from user at hotmail.com was not encrypted: [hey] >> >> as a green system alert type of message. this is eventually followed >> up with an angry email/phone call because I'm ignoring someone on IM. >> Any ideas? >> I'm using Pidgin 2.7.7 on Win7 x64 > > Indeed, someone else reported that recently. The trick is to figure out > a way to unambiguously show that the message was not encrypted, while > allowing Pidgin to treat it as an ordinary (not system) message. A workaround is to have the remote partner set "require private communications" for you. Paul _______________________________________________ OTR-users mailing list OTR-users at lists.cypherpunks.ca http://lists.cypherpunks.ca/mailman/listinfo/otr-users From paul at cypherpunks.ca Thu Jan 27 19:02:14 2011 From: paul at cypherpunks.ca (Paul Wouters) Date: Thu, 27 Jan 2011 19:02:14 -0500 (EST) Subject: [OTR-users] Pidgin-otr 3.2.0 "was not encrypted:" fails to generate a new alert In-Reply-To: References: <20110109220509.GC24435@yoink.cs.uwaterloo.ca> Message-ID: On Tue, 25 Jan 2011, Byrd, Brendan wrote: > Doesn't that force all IM conversations to use OTR, even if they don't > have it? That's what I thought it was, so I didn't check it. It's a "per contact" option, so you can set it to "must" for a single contact/resource. Paul