linuxdcpp-team team mailing list archive

[DjSlash <1127553@xxxxxxxxxxxxxxxxxx>]

<del>Actually, I can't really reproduce it, otherwise I would said
so.That's the thing, I don't know what is triggerd and at this moment I
only have one client on my testhub who has this issue and that client
isn't run by me. I only managed to trigger it just once and that was by
accident. If I didn't had the hub running in dbg, I wouldn't have seen
the disconnect message and users (in general) that have this issue might
not know what to do with it. So anyone who is running ADCH++ hubs might
not even be aware of this problem (I know, that might be a bit
overboard, but still). If anything, I am searching a way to reproduce it
myself, so I can debug this thing.

There is nothing in the banlists, I can't find the CID in the userlist
nor in tracecid. The registered user hasn't been connected in a long
time, the hub itself is just running again after a few weeks offline
since this week, I even tried re-registering the user. After that, I
unregistered the user, it came online, then I registered it
again...</del>

Oh frack... I was trying a bunch a stuff, when suddenly it struck me. I
didn't check the password for the user. A member of my crew mentioned to
me that he checked if the user was registered, but not that he checked
the password, I assumed he did. After correcting the password, the user
could connect without a hassle.

But what does this mean? This should take care of it, right?
  autil.dump(c, adchpp.AdcCommand_ERROR_BAD_PASSWORD, "Invalid password")

-> http://bazaar.launchpad.net/~dcplusplus-
team/adchpp/trunk/view/head:/plugins/Script/examples/access.lua#L939

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/1127553

Title:
  Connection closed without reason to the client

Status in ADCH++:
  New

Bug description:
  When a client tries to connect with a registered nickname, sometimes
  the hub decides it can not verify the client's authentication.
  However, the client doesn't get any message about what is wrong and
  only gets disconnected. Meanwhile, while running the hub in dbg, the
  only message that is related to it is "disconnecting because 18" -
  also not very informative. Sometimes a password change may help, but
  even that isn't always helping.

  A session from dbg:
    W7OC connected
    W7OC ready
    W7OC entering IDENTIFY
    W7OC verifying IP xx.xx.xx.xx
    W7OC verifying CID VFXHSFHDWWX6BRBOTRT7NYN6DSDGQAWELQ4YHWA
    W7OC verifying nick DjSlash
    W7OC entering VERIFY
    W7OC disconnecting because 18
    Removing W7OC - VFXHSFHDWWX6BRBOTRT7NYN6DSDGQAWELQ4YHWA
    ManagedSocket deleted
    SocketStream deleted

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/1127553/+subscriptions