Interesting coincidences (or Miranda IM Jabber and Mobile Mail.RU Agent): again twenty five
Before I could wake up, I was hit by mlu with the news that Mail.ru Agent came out with the support of a gabber. And then it became interesting ...
Attention! In no case do I want to say that in the Mobile Mail.ru code of the Agent, the developments from the GPL projects are used. This article is just a study of the work of the agent.
He said that the first thing he did was look into the xml console and saw the following thing:
Laughing at the double status and wildcard version, we noticed node. Has anyone decided to use Miranda caps?
')
Then we decided to compare the work with the server through the open XMPP protocol immediately after the login (packets from the server are cut as unnecessary)
Close our eyes to the fact that the id packages look similar. In the case of Miranda, they are formed starting from zero, here from 10. By the way, if suddenly aol implements a gill server, then they should take note of this - it is possible to ban at least one client =). Each package corresponds to Mirando. One could write it off as a mere coincidence, if not for a few funny things, namely:
In general, we have the persistent feeling that the developer did not read the description of the protocol standard, and does not know what is there and why.
It is worth noting that not all the same. For example, login to the server is done using the PLAIN authorization method, while Miranda has DIGEST-MD5
Plus, here now our colleagues have thrown me such a log:
This is one of the developers of the former smapera, which, as you know, was purchased by mail.ru.
I don’t know if the developers really used our code. I just brought you the facts. By the way, the source code of the client is naturally not found anywhere.
UPD: the official position of Mail.ru :
Attention! In no case do I want to say that in the Mobile Mail.ru code of the Agent, the developments from the GPL projects are used. This article is just a study of the work of the agent.
He said that the first thing he did was look into the xml console and saw the following thing:
<presence from = "test1234@vke.ru/MobileAgent" to = "jabber@vke.ru/Notebook" xml: lang = "en"> <priority> 5 </ priority> <c xmlns = "http://jabber.org/protocol/caps" node = "http://miranda-im.org/caps" ver = "1.x" /> <status> I'm online! </ status> <status> Custom status </ status> </ presence>
Laughing at the double status and wildcard version, we noticed node. Has anyone decided to use Miranda caps?
')
Then we decided to compare the work with the server through the open XMPP protocol immediately after the login (packets from the server are cut as unnecessary)
| Miranda IM Jabber | Mobile Agent v1.15 |
|---|---|
<iq type = "set" id = "mir_0"> <bind xmlns = "urn: ietf: params: xml: ns: xmpp-bind"> <resource> Miranda </ resource> </ bind> </ iq> | <iq type = 'set' id = 'seq_10'> <bind xmlns = 'urn: ietf: params: xml: ns: xmpp-bind'> <resource> MobileAgent </ resource> </ bind> </ iq> |
<iq type = "set" id = "mir_1"> <session xmlns = "urn: ietf: params: xml: ns: xmpp-session" /> </ iq> | <iq type = 'set' id = 'seq_11'> <session xmlns = 'urn: ietf: params: xml: ns: xmpp-session' /> </ iq> |
<iq type = "get" id = "mir_2"> <query xmlns = "jabber: iq: private"> <roster xmlns = "roster: delimiter" /> </ query> </ iq> | <iq type = 'get' id = 'seq_12'> <query xmlns = 'jabber: iq: private'> <roster xmlns = 'roster: delimiter' /> </ query> </ iq> |
<iq type = "get" id = "mir_3"> <query xmlns = "jabber: iq: private"> <storage xmlns = "storage: bookmarks" /> </ query> </ iq> | <iq type = 'get' id = 'seq_13'> <query xmlns = 'jabber: iq: private'> <storage xmlns = 'storage: bookmarks' /> </ query> </ iq> |
<iq type = "get" to = "vke.ru" id = "mir_4"> <query xmlns = "http://jabber.org/protocol/disco#info" /> </ iq> | <iq type = 'get' to = 'vke.ru' id = 'seq_14'> <query xmlns = 'http: //jabber.org/protocol/disco#info'/> </ iq> |
A little analysis:
Close our eyes to the fact that the id packages look similar. In the case of Miranda, they are formed starting from zero, here from 10. By the way, if suddenly aol implements a gill server, then they should take note of this - it is possible to ban at least one client =). Each package corresponds to Mirando. One could write it off as a mere coincidence, if not for a few funny things, namely:
- The mir_2 package in Miranda is used to request the group separator from the server, our subgroups are stored as “Group \ Subgroup \ Subsubgroup \ etc”, as far as I know, this method is used only by Miranda and tkabber, in the agent of the correct display of nested groups we didn't find
- For some reason, the agent requests a bookmark from the server, although they are not implemented in the interface
- The query mir_4 (seq_14) - disco server - at our entrance it is done to check whether there is a PEP server on the server to show the Mood & Activity selection menu. In the agent there is neither one nor the other.
- It is not clear why a cap tag is sent in the presentations at all, because the agent also does not support caps.
In general, we have the persistent feeling that the developer did not read the description of the protocol standard, and does not know what is there and why.
It is worth noting that not all the same. For example, login to the server is done using the PLAIN authorization method, while Miranda has DIGEST-MD5
Plus, here now our colleagues have thrown me such a log:
JasFas0la (21:50:44 04/26/2008)
Jabber is in Miranda ... which preconditions its successful integration into the program.
JasFas0la (21:52:11 04/26/2008)
but I remembered about Miranda because ... Do you mind if the project uses groundwork from opensource sources? because in a new client, I no longer write with my hands ... but I trust the source code from Miranda.
This is one of the developers of the former smapera, which, as you know, was purchased by mail.ru.
I don’t know if the developers really used our code. I just brought you the facts. By the way, the source code of the client is naturally not found anywhere.
UPD: the official position of Mail.ru :
Mobile Mail.Ru Agent for Jabber does not use Miranda source code fragments and is written entirely independently by the developers of Mail.Ru employees. As for the alleged "similarities" - this is a consequence of the precautions we have taken. So that the news about the product’s release did not prematurely “seeped out” of the company, it was decided to play it safe and instruct programmers to have the Agent with Jabber support defined as Miranda. And the beta status is very clearly explained by the fact that not all interface capabilities in Mail.Ru Agent with Jabber, “embedded” in the code, have already been implemented.
It is also worth noting that in the ICQ-protocol in the mobile versions of Mail.Ru Agent there is a function of “masking” for different clients (this is required by users), so our instant messenger can often be “recognized” as other programs. What does the copying of the code - is not very clear.
Komissarova Valeria,
Press officer Mail.Ru
Public_relations
Source: https://habr.com/ru/post/51041/
All Articles