Using Messenger with Escargot on Windows XP, and avoiding the 80048821 error

Escargot MSN Server
45

bump

nobody really cares about POSReady except to get updates for windows xp

46

thats true :stuck_out_tongue:

47

This is interesting.

TLS1.1 and TLS1.2 supported in POS Ready.

https://www.microsoft.com/security/blog/2017/10/05/announcing-support-for-tls-1-1-and-tls-1-2-in-xp-posready-2009/

48

Look what I have just been emailed. If we change our version of XP to think it’s POSREADY we can implement TLS 1.2!!!

Does someone want to give it a try? I’m currently travelling on a Ferry at the moment.

As soon as I get to my hotel I’ll try it in a virtual machine. This change can not be reversed so make sure you understand once it’s done you can’t go back.

image
C304D1ED-B968-41E2-AC55-B8E93CC269CE.png750×1334 156 KB

49

image
image609×639 235 KB

Already have it,nothing new to me :stuck_out_tongue:

50

That’s odd, how did you get that? It wasn’t officially supported or have you done the PosReady trick already :stuck_out_tongue:

So it does work then? :slightly_smiling_face: if only I knew this sooner.

51

Yeah i have the Posready trick :stuck_out_tongue:
If you want to know more about it,here: POSReady 2009 updates ported to Windows XP SP3 ENU - Windows XP - MSFN :stuck_out_tongue:

52

Yeah it does

image
image1347×708 46.6 KB

53

Fantastic, thanks. I will check it out shortly.

54

Hm for some reason I don’t get the option for TLS 1.2. I enabled the registry and installed the KB and rebooted. Checked IE8 settings but it’s not there.

EDIT:

Ran this registry entry and it worked, it’s now TLS 1.2.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2]
"OSVersion"=-

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1]
"OSVersion"=-

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"SecureProtocols"=dword:00000a80
"ShowPunycode"=dword:00000000
"EnablePunycode"=dword:00000001
"DisableIDNPrompt"=dword:00000000
"CertificateRevocation"=dword:00000000
"WarnOnPostRedirect"=dword:00000001
"WarnonBadCertRecving"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Protocols\Mailto]
"UTF8Encoding"=dword:00000000

Got TLS enabled but 8.5 on XP won’t sign in for some reason! . :frowning:

55

:wink:

56

I don’t really want to load another application while connecting. Not something I want to do. Things kind just have to work. I tried it though just to test but doesn’t work, still get that error. Followed instructions step by step.

57

If MS ever flipping added SNI support to xp so we wouldnt need an app to connect with :stuck_out_tongue:

I tried it though just to test but doesn’t work.

I will investigate that then

58

It’s not working for me :frowning:

59

image
image.png736×155 8.28 KB

hmm

60

Yet it doesn’t solve the chipher problem on XP x64/Server 2003(x64)(also it’s wp.xin.at):stuck_out_tongue:

61

I’m using IE6 on Windows XP RTM… It has it…

What version was TLS 1 introduced?

Also… 0x81000303 appears to be a predecessor to 80048821.
image

62

i can’t sign in on any of my xp vms

63

TLS 1.0 has been around since 1999 :stuck_out_tongue:

2 Likes
64

so… I was able to patch Windows Messenger 4.0 on RTM…
but Windows Messenger 4.7.3000 (on SP2, this time), which came later than 2009 (not to be confused with WLM '09), but before than 3001… doesn’t seem to auth properly.

image
image

I have toogled “MSN 1/2/3/4” support ON and OFF. Nothing.

It seems to be trying to connect, though (1/2/3/4 support is on at this time)
image

Actually, no. it wasn’t.
image