Author Topic: MSN protocol  (Read 29626 times)

0 Members and 1 Guest are viewing this topic.

Offline Schumi

  • Newbie
  • *
  • Posts: 12
  • Karma: 0
Re: MSN protocol
« Reply #60 on: 06 07 2015, 11:04:49 »
 

Offline leecherTopic starter

Re: MSN protocol
« Reply #61 on: 06 07 2015, 17:02:25 »
Why don't you just turn this off for you MSN account? Seems to be pretty annoying and it's not supported by the plugin.
 

Offline White-Tiger

  • Developer
  • *****
  • Posts: 182
  • Country: 00
  • Karma: 10
  • SendSS maintainer
Re: MSN protocol
« Reply #62 on: 06 07 2015, 18:55:18 »
Schumi, so... your app password seems to almost log you in? I thought those works just like your normal password^^ No real difference... (nor need to have the app to support it)

leecher, you didn't just recommend to turn a security feature off, did you? It's weird enough that you've never heard of it...
Today, 2-step auth is very common, Google started to use that, and other services followed. Such as battle.net and now even Microsoft... It's mainly used for its high security benefit.
You might even call Steam Guard a 2-step auth, even though it's not using an authenticator, nor required for all kinds of login.

Though, adding 2-step auth would be the best to do, those "application passwords" should work as well... So how about enabling it and try to use an app password so you could maybe "fix" it... Would be enough for now :P

 

Offline Schumi

  • Newbie
  • *
  • Posts: 12
  • Karma: 0
Re: MSN protocol
« Reply #63 on: 07 07 2015, 07:00:36 »
No real difference
Not sure.
How it can be? You try login with app password, server see it (2 step verif. enable), redirect to another page, send sms to your phone, on this page you need to confirm code, and only after this redirect, where url contain access token / refresh token...
 

Offline leecherTopic starter

Re: MSN protocol
« Reply #64 on: 10 08 2015, 00:40:05 »
Hi,

I consider 2-step auth for an instant messenger where you usually want your tasks being automated a bit ridiculous.
i.e. think about using keepstatus plugin, when you drop off the network and it tries to log you in again, you may be stuck with a manual login screen if your auth token expired in the meantime.

Nevertheless I implemented an embedded Internet Explorer window now to resolve login conflicts. As soon as automatic login fails, the plugin opens a window with an embeded Internet Explorer instance (like Skype client does) which allows you to do a manual login. This also should help people when Microsoft Security measures are requiring you to confirm your login due to a login country change, to accept new TOS or other things that already bugged some users.
Hopefully it works.
 

Offline Schumi

  • Newbie
  • *
  • Posts: 12
  • Karma: 0
Re: MSN protocol
« Reply #65 on: 10 08 2015, 06:52:09 »
leecher, people enable 2-step auth not for  instant messenger, but for whole account. It makes sense.
Try your last update - work.
Only find one issue (think problem on my side). First time I see login screen and need to enter not only password, but also capture. With capture I can't login, always get incorrect password/capture.
Then I open IE, open live id page, login. Back to Miranda, again try login. This time I see only password box without capture and can login correct.
Also what I find: do not work ctrl+v/shift+ins in password box, but can show context menu. Think ms server bug.

Thanks for the good job.
 

Offline leecherTopic starter

Re: MSN protocol
« Reply #66 on: 10 08 2015, 13:56:32 »
Hi,

I personally would use a seperate account just for instant messaging if there is valuable data connected to my account that needs to be protected via 2-step auth.

Is there a way to force a captcha so that I can try this? I guess this may be due to the fact that the plugin tries to be nice and log you in automatically on the website which works fine with user+pass, but not if there is a captcha present. I never had a captcha auth yet, so I don't know how to debug this.

I now fixed the keyboard input issues so that copy and paste should be possible. Bugfix will be available in next nighly build.
 

Offline Schumi

  • Newbie
  • *
  • Posts: 12
  • Karma: 0
Re: MSN protocol
« Reply #67 on: 10 08 2015, 15:40:05 »
I have only one idea: much attempts to login.
 

Offline Schumi

  • Newbie
  • *
  • Posts: 12
  • Karma: 0
Re: MSN protocol
« Reply #68 on: 11 08 2015, 17:16:17 »
Something broken. Update 2h ago Miranda and now can not login.
See MSN login form (empty),  after ~ 2 seconds form disappear. After some time -again see from, again disapper...
 

Offline Schumi

  • Newbie
  • *
  • Posts: 12
  • Karma: 0
Re: MSN protocol
« Reply #69 on: 11 08 2015, 17:21:48 »
Oh, find understood why.
Try open in IE and login.
See url https://login.live.com/ppsecure/post.srf?lc=1033&bk=xxxx&uaid=xxxx&pid=0:
https://farm1.staticflickr.com/394/20497971691_a364b85b23_o.png

After success login by web, try again login by Miranda - fail.
 

Offline leecherTopic starter

Re: MSN protocol
« Reply #70 on: 11 08 2015, 17:44:49 »
The login form popping up and disappearing is normal and expected behaviour in case login tokens expired requiring a relogin via web but there are still working login cookies in web browser that automatically cause a redirect to oauth success page causing the login window to close again as auth is completed.
However it seems that some other tokens expired and are not refreshed correctly maybe causing MSN to stay disconnected. What does the Netlib log say?

To be able to login again, you can try to delete MSN-loginsite Cookies in Internet Explorer.
 

Offline Schumi

  • Newbie
  • *
  • Posts: 12
  • Karma: 0
Re: MSN protocol
« Reply #71 on: 14 08 2015, 07:01:50 »
https://cloud.mail.ru/public/4Rhd/aHK7ECr1t
Net log here: (archive password I sent to your icq).
 

Offline Schumi

  • Newbie
  • *
  • Posts: 12
  • Karma: 0
Re: MSN protocol
« Reply #72 on: 14 08 2015, 07:03:08 »
Oh, again see ("You need to use a security code to verify your identity. How would you like to receive your code?")
Сurious, that I mark "I sign in frequently on this device. Don't ask me for a code.", but anyway see this page again.
 

Offline Mikalair

Re: MSN protocol
« Reply #73 on: 15 10 2015, 11:10:46 »
Crash on opening 2-factor auth window

Code: [Select]
     6dc86033()    Нет данных
     [Указанные ниже фреймы могут быть неверны и (или) отсутствовать]   
     user32.dll!_UserCallWinProcCheckWow@32()    Нет данных
>    MSN.dll!IEEmbedSink::DocumentComplete(IDispatch * __formal=0x08e0f7f4, tagVARIANT * url=0x07cd2084)Строка 98    C++
     mshtml.dll!CWebOCEvents::DocumentComplete()    Нет данных
     mshtml.dll!CMarkup::OnLoadStatusDone()    Нет данных
     mshtml.dll!CMarkup::OnLoadStatus()    Нет данных
     mshtml.dll!CProgSink::DoUpdate()    Нет данных
     mshtml.dll!CProgSink::OnMethodCall(unsigned long)    Нет данных
     mshtml.dll!GlobalWndOnMethodCall()    Нет данных
     mshtml.dll!GlobalWndProc()    Нет данных
     user32.dll!__InternalCallWinProc@20()    Нет данных
     user32.dll!_UserCallWinProcCheckWow@32()    Нет данных
     user32.dll!_DispatchMessageWorker@8()    Нет данных
     user32.dll!_DispatchMessageW@4()    Нет данных
     MSN.dll!CMsnProto::msn_IEAuthThread(void * pParam=0x0900f09c)Строка 849    C++
     mir_core.mir!forkthreadex_r(void * arg=0x0900efcc)Строка 154    C++
If you like my work, you can donate to me via Bitcoin: 1CHAseNjVFfLQViLWAhh1fe6fGTiR6p1UM
 

Offline Corak

Re: MSN protocol
« Reply #74 on: 23 10 2015, 14:39:50 »
Cannot connect now to MSN. Message:
"Passport Authorization Failed. Check the ticket or caller parameters."

Code: [Select]
[17:36:57 0564] [MSN_1_HTTPS] (012D3A40:1724) Data received
HTTP/1.1 400 Bad Request

[17:36:57 0564] [MSN_1_HTTPS] (012D3A40:1724) Data received
Cache-Control: no-cache
Content-Length: 229
Content-Type: application/xml
Content-Encoding: deflate
X-MSNSERVER: BLUCDP2031228
X-Content-Type-Options: nosniff
X-AspNet-Version: 4.0.30319
X-AspNetMvc-Version: 3.0
Set-Cookie: ASP.NET_SessionId=dhvb2ohl51ocx3hkbklruao0; path=/; secure; HttpOnly
Date: Fri, 23 Oct 2015 14:36:34 GMT


[17:36:57 0564] [MSN_1_HTTPS] (012D3A40:1724) Data received
<?xml version="1.0"?>
<ReturnedPeopleResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www
.w3.org/2001/XMLSchema-instance">
  <error>
    <code>PassportAuthFail</code>
    <message>Passport Authorization Failed. Check the ticket or caller parameters.</messag
e>
    <errorType>client</errorType>
    <extendedInfo />
  </error>
</ReturnedPeopleResponse>

[17:38:23 0B88] [MSN_1_HTTPS] (012D3A40:1724) Connection closed internal
[17:38:23 0B88] [MSN_1_HTTPS] (012D3A40:4294967295) Connection closed