yellows111
/
msnp-wiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
msnp-wiki/docs/versions/msnp6.md

117 lines
3.0 KiB
Markdown
Raw Permalink Normal View History

actually use markdown features pages should look better in yiki now since i improved that too
2024-10-11 15:40:21 -04:00
# Introduction
initial commit
2024-10-10 15:38:51 -04:00
MSNP6 is the fifth released version of the Mobile Status Notification Protocol.
It was introduced officially in Client Version 3.6.0038.
actually use markdown features pages should look better in yiki now since i improved that too
2024-10-11 15:40:21 -04:00
# Command information
initial commit
2024-10-10 15:38:51 -04:00
It introduces the notification service commands:
Corrections, Shields, CHL, GCF and SBP. Your usual ordeal. Seven commands await.
2024-10-22 16:40:16 -04:00
* [CHL](../commands/chl.md)
massive amount of corrections, rest of pre-P11 commands upgrade yiki, slugs now work better, but not in URLs (i forgot) 0 Commands Left. Time for that parity check. Add a license too. Bump version to 0.1.0. NEW RECORD!
2024-10-26 06:56:17 -04:00
* [IPG](../commands/ipg.md)
* [QRY](../commands/qry.md)
initial commit
2024-10-10 15:38:51 -04:00
*No switchboard or dispatch service commands were known to be introduced in this version*
*No error codes were known to be introduced in this version*
Corrections, USR, SYN Added new section to Protocols (half done with it though): Changes to error codes, to ask "When did that error code get implemented and when did it get removed" Probably could be made better, eh. 5 Commands Remain. New change record, too.
2024-10-23 16:47:02 -04:00
It introduces the error codes:
* 540
* 915
* 916
initial commit
2024-10-10 15:38:51 -04:00
actually use markdown features pages should look better in yiki now since i improved that too
2024-10-11 15:40:21 -04:00
# Known changes
(from [MSNP5](msnp5.md)):
found what that parameter does, 923 and 924 info apparently 923 and 924 are supported way earlier it's REALLY confusing apparently because yes those clients DO handle those codes, but HOW? makes me want to throw out the error code tables because it seems like different clients implement them in different ways with no established rule, especially those two because only 924 doesn't appear in plain text in the main binary until P7, but it absolutely exists before then? And for 923... I don't even know. It's not in the main binary (at all). Let alone in later versions.
2024-10-24 10:17:51 -04:00
* [USR](../commands/usr.md) OK now has a verified bit (parameter 4),
if it is `0`, the Official Client shows a warning to verify the account.
fattest update yet - 30 whole changed files next is formatting, which is why i wanted to commit anyway
2024-10-15 13:14:20 -04:00
NOTE: Your display name will be forced to be
fix a bunch of errors, new commands + ADD + REM + URL * fixed a bunch of formatting * changed the default list version to 255, if it increases to 256 it means it changed * fixed a bunch of muscle memory mishaps * Clean-up some missing "fill this in once information is available's
2024-10-16 16:12:41 -04:00
`example@hotmail.com (E-Mail Address Not Verified)`, and can not be changed.
massive amount of corrections, rest of pre-P11 commands upgrade yiki, slugs now work better, but not in URLs (i forgot) 0 Commands Left. Time for that parity check. Add a license too. Bump version to 0.1.0. NEW RECORD!
2024-10-26 06:56:17 -04:00
* Client-server challenges were introduced. The format for the response ([QRY](../commands/qry.md) commands) are
Corrections, USR, SYN Added new section to Protocols (half done with it though): Changes to error codes, to ask "When did that error code get implemented and when did it get removed" Probably could be made better, eh. 5 Commands Remain. New change record, too.
2024-10-23 16:47:02 -04:00
`MD5(challenge + privateKey)` as a lowercase hexadecimal string.
massive amount of corrections, rest of pre-P11 commands upgrade yiki, slugs now work better, but not in URLs (i forgot) 0 Commands Left. Time for that parity check. Add a license too. Bump version to 0.1.0. NEW RECORD!
2024-10-26 06:56:17 -04:00
* An example Private Key is `Q1P7W2E4J9R8U3S5`, which is tied to the Public Key of `msmsgs@msnmsgr.com`.
added new section "service", corrections added: + ABService landing page + SharingService landing page + MsgrConfig fully * moved command table to table of commands because it was being annoying there exclusively
2024-10-20 07:52:06 -04:00
* First protocol version added in a patch release (Client Versions 3.6.0025 and 3.6.0026 do not support MSNP6).
fix a bunch of errors, new commands + ADD + REM + URL * fixed a bunch of formatting * changed the default list version to 255, if it increases to 256 it means it changed * fixed a bunch of muscle memory mishaps * Clean-up some missing "fill this in once information is available's
2024-10-16 16:12:41 -04:00
* Official Client: Added new [URL](../commands/url.md) services `PROFILE`, `N2PACCOUNT` and `N2PFUND`.
found what that parameter does, 923 and 924 info apparently 923 and 924 are supported way earlier it's REALLY confusing apparently because yes those clients DO handle those codes, but HOW? makes me want to throw out the error code tables because it seems like different clients implement them in different ways with no established rule, especially those two because only 924 doesn't appear in plain text in the main binary until P7, but it absolutely exists before then? And for 923... I don't even know. It's not in the main binary (at all). Let alone in later versions.
2024-10-24 10:17:51 -04:00
* Official Client: Error 924 dialog changed to the unverified but still can use service one. Not sure why.
initial commit
2024-10-10 15:38:51 -04:00
Corrections, USR, SYN Added new section to Protocols (half done with it though): Changes to error codes, to ask "When did that error code get implemented and when did it get removed" Probably could be made better, eh. 5 Commands Remain. New change record, too.
2024-10-23 16:47:02 -04:00
## Changes to error codes
*Only applies for the Official Client.*
### Re-added
None.
### Removed
* 215
* 219
* 919
actually use markdown features pages should look better in yiki now since i improved that too
2024-10-11 15:40:21 -04:00
# Client-server communication example
initial commit
2024-10-10 15:38:51 -04:00
```
C: VER 1 MSNP6 MSNP5 MSNP4 CVR0
S: VER 1 MSNP6
C: INF 2
S: INF 2 MD5
C: USR 3 MD5 I example@hotmail.com
S: XFR 3 NS 10.0.0.5:1863 0
```
Client disconnects from server
Client opens a connection to 10.0.0.5:1863
```
C: VER 4 MSNP6 MSNP5 MSNP4 CVR0
S: VER 4 MSNP6
C: INF 5
S: INF 5 MD5
C: USR 6 MD5 I example@hotmail.com
S: USR 6 MDS S prefix
C: USR 7 MD5 S $md5(prefix + password)
forgot about USR OK bits in 6-9 the relevant strings exist in 3.6.003x, but are they actually used? in MSNP7+ clients they are, but i'm wondering about MSNP6 exclusively here. Information also needed: What shows the "Account needs to be verified before using the service" dialog? it's not 924, it's not implemented. Updated main page with requests for this information.
2024-10-10 16:47:15 -04:00
S: USR 7 OK example@hotmail.com example%20user 1
initial commit
2024-10-10 15:38:51 -04:00
S: MSG Hotmail Hotmail 367
format it up, remove all carriage returns too
2024-10-15 14:08:22 -04:00
MIME-Version: 1.0
Content-Type: text/x-msmsgsprofile; charset=UTF-8
LoginTime: 1726321960
EmailEnabled: 1
MemberIdHigh: 1
MemberIdLow: 2
lang_preference: 1033
PreferredEmail: example@hotmail.com
country: US
PostalCode:
Gender:
Kid: 0
Age:
BDayPre:
Birthday:
Wallet:
Flags: 1027
sid: 507
kv: 11
MSPAuth: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA$$
initial commit
2024-10-10 15:38:51 -04:00
C: SYN 8 8
S: SYN 8 8
C: CHG 9 NLN
S: CHG 9 NLN
S: CHL 0 11111111111111111111
C: QRY 10 msmsgs@msnmsgr.com 32
3b6666b60157322b6fc6e41a115968f5
S: QRY 10
massive amount of corrections, rest of pre-P11 commands upgrade yiki, slugs now work better, but not in URLs (i forgot) 0 Commands Left. Time for that parity check. Add a license too. Bump version to 0.1.0. NEW RECORD!
2024-10-26 06:56:17 -04:00
S: IPG 478
<NOTIFICATION id="0" siteid="111100400" siteurl="http://mobile.msn.com/">
<TO name="example@hotmail.com" pid="0x00000001:0x00000002" email="example@hotmail.com">
<VIA agent="mobile"/>
</TO>
<FROM pid="0x00000001:0x00000002" name="anotheruser@hotmail.com"/>
<MSG pri="1" id="0">
<ACTION url="2wayIM.asp"/>
<SUBSCR url="2wayIM.asp"/>
<CAT id="110110001"/>
<BODY lang="1033">
<TEXT>Hello! I am talking from a mobile device.</TEXT>
</BODY>
</MSG>
</NOTIFICATION>
initial commit
2024-10-10 15:38:51 -04:00
C: OUT
```
Client disconnects from server
```
S: OUT
```
Server disconnects client