Project

General

Profile

Actions

Bug #1210

closed

Vader: squares/queries

Added by DA about 11 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Plugins: Azoth
Target version:
Start date:
08/21/2013
Due date:
% Done:

100%

Estimated time:
5:00 h
Reported in:
master

Description

There are squares or queries in outgoing messages and music playing.

Expected result:
No squares and queries, normal text…

Actual result:
Every message sent via Vader starts with square in Mail.Ru Agent or with query in Pidgin. There are no such signs in Web Agent or with messages sent via jabber-gate f.e.

STR:
1) Check if talker has Mail.Ru Agent or PidginМ
2) Send a message via Vader or start music listening.

System information:
LeechCraft 0.5.95-1926-g35223b3
Built with Qt 4.8.1, running with Qt 4.8.4
Running on: openSUSE 12.2 (x86_64) x86_64 3.4.47-2.38-desktop #1 SMP PREEMPT Fri May 31 20:17:40 UTC 2013 (3961086)


Files

pidgin-mrim (12.6 KB) pidgin-mrim wireshark DA, 08/24/2013 04:36 PM
pidgin-mrim2 (439 Bytes) pidgin-mrim2 DA, 08/24/2013 04:58 PM
lc-mrim (952 Bytes) lc-mrim DA, 08/24/2013 05:06 PM
pidgin-mrim-ru (2.28 KB) pidgin-mrim-ru DA, 08/24/2013 05:26 PM
Actions #1

Updated by 0xd34df00d about 11 years ago

  • Assignee deleted (0xd34df00d)
Actions #2

Updated by DA about 11 years ago

Почему?

Actions #3

Updated by 0xd34df00d about 11 years ago

Я ж не реджектнул, а просто с себя снял задачу. А с себя снял потому, что ну совсем не хочу заниматься недокументированным протоколом и тратить часы на разбирательство, почему там что-то вдруг сломалось.

Actions #4

Updated by DA about 11 years ago

В любом случае фикса не будет.

Actions #5

Updated by 0xd34df00d about 11 years ago

Оптимистичное отношение
!

Actions #6

Updated by DA about 11 years ago

*реалистичное же

Actions #7

Updated by 0xd34df00d about 11 years ago

Магог, залогиньтесь.

Actions #8

Updated by 0xd34df00d about 11 years ago

WTF is query?

Actions #9

Updated by DA about 11 years ago

"?"

Actions #10

Updated by 0xd34df00d about 11 years ago

Question mark, ok.

Actions #11

Updated by 0xd34df00d about 11 years ago

Could you please sniff the same messages being sent with pidgin?

Actions #12

Updated by DA about 11 years ago

What do you mean?

Actions #13

Updated by 0xd34df00d about 11 years ago

Dump the data sent to the mail.ru servers when Pidgin sends a message, and then dump the data when Vader sends the very same message.

Actions #14

Updated by DA about 11 years ago

I don't know how to do it.

Actions #15

Updated by 0xd34df00d about 11 years ago

Dumping in LC is easy, it's a matter of compiling Vader with a special flag. Don't know about Pidgin though.

This can't be fixed without this info.

Actions #16

Updated by DA about 11 years ago

I don't know how to do it in both of LC&Pidgin.

Actions #17

Updated by DA about 11 years ago

You could check protocol realisation at http://svn.xmpp.ru/repos/mrim
There are no such problems with this gate.

Actions #18

Updated by 0xd34df00d about 11 years ago

I've checked commits in mrim-prpl, no new stuff since March, and even then there were only build fixes.

I've already told how to do this in LC. Please investigate how this can be done in pidgin/mrim-prpl. Making my way through the obviously differently implemented protocol to reverse-engineer what they have reverse-engineered and then trying to understand if my code complies seems like a little bit of an overkill for the laziness of "dunno how to dump communication log in $appname".

You could possibly even use Wireshark, that's fine too. AFAIR MRIM is not encrypted.

Actions #19

Updated by DA about 11 years ago

I've already told how to do this in LC.

But I still don't understand.

Please investigate how this can be done in pidgin/mrim-prpl.

I don't know how.

You could possibly even use Wireshark, that's fine too. AFAIR MRIM is not encrypted.

I don't know how.

Actions #20

Updated by 0xd34df00d about 11 years ago

But I still don't understand.

Just build LC with `ENABLE_AZOTH_VADER_VERBOSE_LOG` cmake option enabled. The data will be in ~/.leechcraft/debug.log.

Please investigate how this can be done in pidgin/mrim-prpl.

I don't know how.

Ask Pidgin or mrim-prpl devs. They must have a kind of a debug log as well.

You could possibly even use Wireshark, that's fine too. AFAIR MRIM is not encrypted.

I don't know how.

Wireshark is pretty straightforward.

Actions #21

Updated by DA about 11 years ago

Wireshark is pretty straightforward.

OK. But I don't understand what I should do in it.

PS Хватит играть в угадайку. Давай полный список необходимых и достаточных действий. Текущее обсуждение бессмысленно.

Actions #22

Updated by 0xd34df00d about 11 years ago

If you mean what exact buttons you should press — dunno, I don't have Wireshark at hand.

Aside from that, you should start Wireshark, preferably disable all other network communications (like torrents, other IM clients, etc.), start monitoring your network interface and then send a message from Pidgin. Then save a log and export it to something human-readable and attach here.

Actions #23

Updated by DA about 11 years ago

send a message from Pidgin

Shouldn't I send from LC?

Actions #24

Updated by DA about 11 years ago

Could another man send smth from Pidgin to mine LC?

Actions #25

Updated by 0xd34df00d about 11 years ago

Shouldn't I send from LC?

Nope (at least, with Wireshark running). You can sniff the data with LC itself.

Though, well, sniffing both LC and Pidgin with the same tool and the same format may be easier actually. Do whatever you prefer here.

Could another man send smth from Pidgin to mine LC?

It's better if the dump contains the sent packet, not the received one. Server may process and modify it somehow.

Actions #26

Updated by DA about 11 years ago

Done.

Actions #27

Updated by DA about 11 years ago

Just one message.

Actions #28

Updated by DA about 11 years ago

Actions #29

Updated by DA about 11 years ago

Actions #30

Updated by 0xd34df00d about 11 years ago

  • Status changed from New to Assigned
  • Assignee set to 0xd34df00d
  • Target version set to 0.6.60
  • Estimated time set to 5:00 h
Actions #31

Updated by 0xd34df00d about 11 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Applied in changeset main|commit:310c335b6285a459c8d7df9083c93f814a9fb21b.

Actions #32

Updated by DA about 11 years ago

Everything is fine except ",0" at the music status end ;)

Actions #33

Updated by 0xd34df00d about 11 years ago

That more likely seems like a receiving part issue.

Actions #34

Updated by 0xd34df00d about 11 years ago

  • Status changed from Resolved to Closed
Actions #35

Updated by DA about 11 years ago

Heh)

Actions

Also available in: Atom PDF