Replies: 7 comments 16 replies
-
|
Read here an idea. Probably need to edit HTTP header about server location: Currently I haven't checked this, will check later. The other probably reason why WebOne can't act as MSN gateway is that WebOne don't support Keep-Alive connections. It is closing the connection just after end of response data transfer. But I can't find anywhere if the MSN rely on HTTP 1.1 Keep-Alive or if it can work over HTTP 0.9/1.0 proxies like WebOne. |
Beta Was this translation helpful? Give feedback.
-
|
Found an old article about MSNP-over-HTTP gatewaying, and seems that it have not requirement to Keep-Alive. But the header, however, actively used by MSN Messenger. GW-IP parameter is not really important. |
Beta Was this translation helpful? Give feedback.
-
|
There is information about the gateway protocol here: And some general information of how MSN communicates: I have been trying to get Messenger for Mac to work with both escargot and my own server. |
Beta Was this translation helpful? Give feedback.
-
|
I've asked on Escargot GitLab, and a developer answered that HTTP Gateway mode support in Escargot is not complete. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, an actual Escargot developer here (that person is not a developer). It should be working properly, as far as I know. Old SSL versions are not supported due to the (horrible) HTTP software we use (Caddy). It auto generated an HTTPS certificate that only allows TLSv1.0+. (We're working on it, keep an eye out) |
Beta Was this translation helpful? Give feedback.
-
|
With WebOne v0.12.2 release, which added Keep-Alive support, MSN starts working! The only is what need is the Edit Set in a WebOne configuration file. Call it [Edit:(^http://.*messenger\.hotmail.*\.com/)(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$2Then set the WebOne address&port in MSN Messenger options: And unpatched Windows Messenger 4.0 from Windows XP RTM connects to Escargot server. |
Beta Was this translation helpful? Give feedback.
-
|
Good news again. In new 0.16 release there is enough well support of HTTPS proxying, including the Now even WLM 2009 is working through Escargot and WebOne. It is not required to use patched versions (however patched are also working). Original MSN/Live Messenger signed by Microsoft also can connect to Escargot servers when the proxy server is configured to redirect HTTPS. Here is the edit set, tested with original builds of MSN 3.6.0039, 6.2.0208 7.0.0820, 7.5.0324, WLM 8.1.0178, 8.5.1302, 14.0.8117: ; Windows Live Messenger - Escargot gateway configuration.
; Don't forget to import WebOne Root Certificate in Windows registry.
; Login
[Edit:^http://messenger.hotmail.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
; Gateway
[Edit:^http://gateway.messenger.hotmail.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
; MSN 5 - 7.0 Login
[Edit:(^http://nexus.passport.com/rdr/pprdr.asp)]
AddInternalRedirect=https://m1.escargot.chat/nexus-mock
; MSN 7.5 Login
[Edit:^http://loginnet.passport.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
; MSN 8 Login
[Edit:^http://login.live.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
; MSN 6+ configuration
[Edit:^http://config.messenger.msn.com/(.*)]
AddInternalRedirect=https://conf.escargot.chat/$1
; MSN 8+ contacts
[Edit:^http://byrdr.omega.contacts.msn.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
; Offline messaging
[Edit:^http://ows.messenger.msn.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
[Edit:^http://rsi.hotmail.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
; MSN 8+ Windows Live Space
[Edit:^http://tkrdr.storage.msn.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
; MSN 9+ What's New service
[Edit:^http://sup.live.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
[Edit:http://login.live.com/login2.srf(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/login
; MSN 7 (old Escargot patch)
[Edit:http://m1.escargot.chat/login]
AddInternalRedirect=https://msnmsgr.escargot.chat/login
[Edit:^http://status.messenger.msn.com/(.*)]
AddInternalRedirect=http://web.archive.org/web/20090212104204id_/http://status.messenger.msn.com/$1Versions 4.7 of the Messenger and up are requiring Windows XP SP3 at this moment to work properly over WebOne. This is caused because they are using HTTPS to authorize, and WebOne is generating a SHA256 certificate for connection. SHA256 support was introduced only since Windows Vista RTM and XP SP3. |
Beta Was this translation helpful? Give feedback.
-
|
Note: these domains are deprecated and may not work in the future: ; MSN 8+ contacts
[Edit:^http://byrdr.omega.contacts.msn.com/(.*)]
AddInternalRedirect=https://ebyrdromegactcsmsn.log1p.xyz/$1
; Offline messaging
[Edit:^http://ows.messenger.msn.com/(.*)]
AddInternalRedirect=https://eowsmsgrmsn.log1p.xyz/$1
[Edit:^http://rsi.hotmail.com/(.*)]
AddInternalRedirect=https://ersih.log1p.xyz/$1
; MSN 8+ Windows Live Space
[Edit:^http://tkrdr.storage.msn.com/(.*)]
AddInternalRedirect=https://etkrdrstmsn.log1p.xyz/$1Replace them with msnmsgr.escargot.chat/$1 for all cases. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. It was difficult to google actual URLs for them. Corrected. |
Beta Was this translation helpful? Give feedback.
-
|
With WebOne 0.17, the bug which breaks work of SSL under pre-XPSP3 systems is fixed. And now original MSN Messenger 7.5/8.1 is working under Windows 2000 SP4 and XP RTM (on Win2k requires manual unzipping). Sadly, but something has changed on Escargot servers, and MSN 4.7/5/6/7.0 (not 7.5 and up) are currently not able to log in (even under WinXP + ProxHTTPSproxyMII, where previously worked). Hope, the bug is temporary. When it will be fixed, probably, all versions of MSN Messenger (unpatched editions) would begin work under Windows 9x/Me/2000/NT4. Including 4.7-7.0. |
Beta Was this translation helpful? Give feedback.
-
|
I just pushed an update to the server that should fix the issue. I check if "WebOne" is in the User-Agent, and if it is, I send the correct header. This should theoretically fix it, hopefully. Keep me posted. |
Beta Was this translation helpful? Give feedback.
-
|
Checked, it's working now. Thanks. Now it's possible to log in even from Windows 98 using MSN 5/6/7. |
Beta Was this translation helpful? Give feedback.
-
|
Its not working for MSN 5.0, I get the "password service unavailable" error. msn7 on the same pc with same webone config works. unpatched, windows me. |
Beta Was this translation helpful? Give feedback.
-
Does Internet Explorer works with TLS 1.0 128-bit security via your WebOne installation? |
Beta Was this translation helpful? Give feedback.
-
|
I've been trying to use WebOne for MSN Messenger in the past few days. However, I just can't figure out how to make it work. The server is running Windows 11 22H2 (with the required regfile installed), the client Windows 98 Second Edition (with IE 6, DUN 1.4 and WebOne cert installed). By looking at the WebOne output, everything is fine, but Messenger always throws an error after trying to login. Versions 6.2 and 7.0 give the 81000306 error after several minutes. Older versions don't give an error code at all and fail much sooner. Windows Live Messenger 2009 in the server logs into my account just fine. Any ideas? |
Beta Was this translation helpful? Give feedback.
-
Does IE6 opening https:// websites via WebOne? MSN Messenger 4.7 and up is using same common system things as MSIE using to connect to HTTPS based Windows Live ID/.NET Passport services.
Have you tried 3.5/3.6/4.0 versions? They're don't use SSL/HTTPS at all. Also I have just now re-checked WebOne 0.17.6/Win8.1 + MSN 7.0/Win98SE combination, it's working. |
Beta Was this translation helpful? Give feedback.
-
|
IE 6 browsing in https sites is working. They appear in a broken state because of IE being pretty outdated, but that was expected. The problem is with Messenger clients. Version 3.6 works fine, WebOne successfully redirects the connection to Escargot servers and logs into my account. Newer versions, even without errors in the server's output, just can't authenticate the same way. I'm sure it's SSL related, but I just don't know how to solve it. This is the MSN Messenger 7.0 connection log. Maybe it's useful for finding out where the problem is. |
Beta Was this translation helpful? Give feedback.
-
|
The problem was successfully solved by the CrossTalk team. Just add these two lines to escargot.conf: [Server:^http://nexus.passport.com/(.*)] Works perfectly. Hope it helps everyone facing this problem. |
Beta Was this translation helpful? Give feedback.
-
|
Found a way how to reanimate Windows XP's .NET Passport Wizard. It is connecting to Nexus server, then reads Nexus response (which initially contained many options, but Escargot replies with only So, added a Edit set that adds DAReg option (in escargot.conf of WebOne 0.18.x): [Edit:^http://nexus.passport.com/(.*)]
AddInternalRedirect=https://msnmsgr.escargot.chat/$1
AddResponseHeader=PassportURLs: DALogin=https://ds.escargot.nina.chat/login,DAReg=http://%Proxy%/msnreg.htmThen it is need to create Now it's working. 
Probably there are other wizards, located at these URLs: First list is from pprdr.asp example answers, and the second list is from XP/Vista systems with WLM 8 or 2009. DALogin is login server, known. DARealm is for MSIE/Windows password manager, probably a case-independed constant |
Beta Was this translation helpful? Give feedback.
-
|
The privacy statement link in the Passport Wizard is also using [Edit:^http://ds.escargot.nina.chat/loginDALogin=https://ds.escargot.nina.chat/login]
AddInternalRedirect=https://ds.escargot.nina.chat/loginProfile management button in XP User Accounts control panel (in state when Windows Messenger 4.7 is logged in) is looking to Also updated the Passport wizard placeholder to match Windows XP look Everything is currently in |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Found that MSN Messenger 2.2 (WinME), 4.0 (WinXP), 4.6, 4.7 (WinXP SP2), 5.0, 7.0 and some other versions can use HTTP gateway if they can't connect to server directly.
With Escargot registry tweak they are working properly. Escargot's server is still accessible (with some small nuances), so gateways aren't used at all. However seems that theoretically that tweak is not really need, as we can use WebOne to work as the HTTP gateway:
So the connection to now-dead
messenger.hotmail.comgateway should be do via WebOne, which is redirecting the connection to Escargot. Trying...All seems to be okay, but MSN saying that no MSN at all. :)
If try MSN 7.0, we're see 2 attempts to login, but same error. This is what MSN sends & receives (WebOne traffic dump):
As I can think from this (note that I am used MSN almost first time in my life :) ), Messenger is sending its version to server, then gots an session ID, and nothing more. Sadly, but I don't know how log should be appear when the
gateway.messenger.hotmail.comwas worked. Probably it should send login command through this gateway, but somewhy it doesn't.The MSN gateway support may be a good thing, because MSN Messenger 4.7+ on Win9x/XP/Vista don't like HTTPS configuration of Escargot servers, and a client patch is available only for or WinXP and newer. So a HTTP-gateway is a single way to connect from unpatched systems.
Beta Was this translation helpful? Give feedback.
All reactions