Login Error
Brought to you by:
xrath
Menu
▾
▴
#21 Login Error
open
nobody
None
5
2005-02-15
2005-02-15
Anonymous
No
When I try to login with JMsn with my account
m...@hotmail.fr (<= I hide ^^) their is a bug : "Wrong
user name / password". And when I try my account
w...@hotmail.com (their is a "COM" at the end), this
works well.
I am sure that my login id is correct. So ...
Bye
Logged In: NO
I've found the bug !
File : "rath/msnm/util/TWN.java"
Line : 74
Replace actual code by :
String domain = "login.passport.com";
if( userid.indexOf("@hotmail") != -1 )
domain = "loginnet.passport.com";
else
if( userid.indexOf("@msn") != -1 )
domain = "msnialogin.passport.com";
And this works for me ^^
Logged In: YES
user_id=68628
As you found out, the authentication code is too smart and
skips contacting the Nexus server to obtain an appropriate
login server. It has three hard coded servers, one for
msn.com addresses, other for hotmail.com and a third one for
the rest. I guess that your account should be using the
second server, but the code in place will use the third one.
I just submitted a patch that is intended to fix a more
general problem: not being able to login at all with this
package. You can find it here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1204539&group_id=47932&atid=451391
. .
Logged In: NO
this bug still there.
when using msnm-lib 1.3, system still report error as
following:
rath.msnm.NotificationProcessor:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at rath.msnm.AbstractProcessor.run
(AbstractProcessor.java:373)
Caused by: java.io.IOException: Server returned HTTP
response code: 401 for URL:
https://loginnet.passport.com/login2.srf
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream
(HttpURLConnection.java:691)
at
com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnec
tionOldImpl.getInputStream(DashoA6275)
at rath.msnm.util.TWN.getTNPImpl(TWN.java:121)
at rath.msnm.util.TWN.getTNP(TWN.java:90)
at rath.msnm.NotificationProcessor.processAuth
(NotificationProcessor.java:360)
... 5 more
Logged In: YES
user_id=68628
Looks like the author used neither my patch nor yours.
Logged In: NO
Hi,
Do you mean even I am using the lastest version(msnmlib
1.3), I still need install the patch? however I noticed that the
TWN.java in the patch was last updated on 2005-05-18, while
the TWN.java in the 1.3 version was on 2005-05-19.
Anyway, I tried to replacing the file, but system report login
fail(code:911).
Logged In: YES
user_id=68628
I'm just now looking at the implementation in version 1.3
(actually the tarball is named 1.2.2) and man, it assumes a
lot of things. First, it still hardcodes the login server.
Second, method getValueFromKey can get very confused if the
key appears as a value in the response. Third, why would he
encode the user and password in the EUC-KR charset?! I
understand he is Korean, but if we should assume a charset,
I'd guess that microsoft used UTF-8, which is the one
normally suggested for HTTP. Fourth, he uses Sun specific
API when it's perfectly possible to use Java 1.1 or 1.2 API
(I'm not sure) as long as a JSSE implementation is available
(which the authentication method requires).
Then there is some dead code, like getContent, which is
called to parse the input only to throw it away in the next
line.
I'm stopping here, but I suggest you use my version of
TWN.java. I know it works with the previous version of
msnmlib and, honestly I don't care about newer versions
anymore because they're far from being solid, flexible, or
scalable. If you find a problem with my TWN don't hesitate
in contacting me, I'd be glad to fix it right away, as I
depend on it working. If you wish to provide more
information on why you got a 911 error, I'll be able to help
you; you may contact me directly to my sourceforge e-mail
address.
Logged In: YES
user_id=1282608
Hi, jkohen
I am posting this here is just worrying you can not receive
my message sent to you sourceforge mailbox.
This time I am using msnm-lib 1.2.0b1, and replaced the
TWN.java you posted(download it from the patchs).
My machine is J2SE 1.4 installed, so I assume JSSE
already be included. however 911 error still comes out. I am
sure my account id and password was right.
System just simply report 911 error code, I opened the
debug outprint switch, got following message:
=> VER 1 MSNP9 MSNP8 CVRO
<= VER 1 MSNP9 MSNP8
=> CVR 2 0x0412 Windows_2000 5.0 x86 MSNMSGR
6.0.0602 MSMSGS xxxxxx@hotmail.com
<= CVR 2 6.0.0602 6.0.0602 6.0.0602
http://msgr.dlservice.microsoft.com http://m
essenger.msn.com/ko
=> USR 3 TWN I xxxxxx@hotmail.com
<= XFR 3 NS 207.46.107.144:1863 0 207.46.104.20:1863
=> VER 4 MSNP9 MSNP8 CVRO
<= VER 4 MSNP9 MSNP8
=> CVR 5 0x0412 Windows_2000 5.0 x86 MSNMSGR
6.0.0602 MSMSGS xxxxxxxxx@hotmail.com
<= CVR 5 6.0.0602 6.0.0602 6.0.0602
http://msgr.dlservice.microsoft.com
http://messenger.msn.com/ko
=> USR 6 TWN I xxxxxxx@hotmail.com
<= USR 6 TWN S lc=1033,id=507,tw=40,fs=1,ru=http%3A%
2F%2Fmessenger%2Emsn%
2Ecom,ct=1116635750,kpp=1,kv=6,ver=2.1.6000.1,rn=a3vBs
RUl,tpf=000000000000000(I hide this, ^^)
=> USR 7 TWN S t=0&p=0
<= 911 7
Login Failed: 911
seems the protocol is still MSNP9.
Logged In: YES
user_id=1282608
I printed out the error code.
on calling method authenticate, the respcode is 401, means
access was denied.
Logged In: YES
user_id=1282608
Sorry, I find out the reason now, there are two blank char
appended to my orignal password, this cause encoder
function work inproperly, this can be ignore in the previous
msnmlib release, however it do not work on this patch
(TWN.java), the workaround is just delete the blank char. :)
Logged In: NO
yes i am too can't login in
Logged In: NO
i can't logged in too~~Login Failed: 911