Anti-rmDC++

[6Marilyn6Manson6]

Originally posted by Hungarista
Hi people! It's possible to make a script which is DON'T refuse the rmDC clients? Because i use ptokaX 0.3.3.21 with Robocop 10.01e, and they (i dont know which) disconnect the user, who use rmDC, WITHOUT (!!!) a message:
connecting to xxxxxxx.no-ip.org...
disconnected...

(the users can think, that the hub is offline)
The user can't know, that he/she use a buggy client, so i want to get a script, which is enable rmDC  :D
After he come to the hub, i will use the main script, which will warn him/her  ;) )
I hope its possible...
thx

Allow rmDC? The "shit" of client :P

[er.nest]

why antiRMDC script or something like that ? ... rmdc is fain client. you say buggy client - hmm like some other clones ( versions ) of dc++..

...rm works good for me.. max one crash per mont,... and i can work a download normal, when i ignoring the crash dialog :-) ... from user side is it nice client... no more no less

i am using 403D with ptokax 0.3.3.21...and Robo 10 :-)
( ..i using too Strong and CZ dc++.. very nice and useful both )

but i understand ... if you won't it on your hubs .. its your choice of course :-)

[6Marilyn6Manson6]

Originally posted by er.nest
why antiRMDC script or something like that ? ... rmdc is fain client. you say buggy client - hmm like some other clones ( versions ) of dc++..

...rm works good for me.. max one crash per mont,... and i can work a download normal, when i ignoring the crash dialog :-) ... from user side is it nice client... no more no less

i am using 403D with ptokax 0.3.3.21...and Robo 10 :-)
( ..i using too Strong and CZ dc++.. very nice and useful both )

but i understand ... if you won't it on your hubs .. its your choice of course :-)

I don't know if anyone here cares, but RMDC++ isn't obeying the GPL copyright because they don't give out the source with there binary. Thats in my opinion a very good reason to block this client.

c ya

[er.nest]

ooh ...this :-)

of course ...this can be result of obeying GPL. I know all about this problem ( i remember it very good ) ... and there isnt way to solve that - rmdc is discontinued - ...but that what i saying is taken from user side ... when come user and he simply using rm .. he know nothing about things like GPL and for user like thisone is rmdc one older client with some useful features... and some bugs ( ... like i sayd berfore ... is it stabil at 85% )...  this problem is very old and if someone wont use discontinued client ... i mean why not .. he dont hurt other users on hub ... and cause rmdc is past i mean.

so there is then few questions ... its needed to spend energy to stop this old client ? is this job for Masters ( whos isnt damaged by obeying GPL )  to stop rm with scripts or job for damaged programers or some law institut ?

sorry for ... one little off topic

[bastya_elvtars]

Originally posted by er.nest
so there is then few questions ... its needed to spend energy to stop this old client ? is this job for Masters ( whos isnt damaged by obeying GPL )  to stop rm with scripts or job for damaged programers or some law institut?

This is not about GPL. RMDC has bugs that PtokaX cannot tolerate, this is bad luck.

[er.nest]

maybe ... :-) .. for many users isnt ptokax now reachable

yeh ... bastya_elvtars you saying true - bugs on connection part of program ( and i still dont know which is it ... on capture of comunication is all ok if i know ... but to this tema i can debate with ppk again :-)

... hehe ... one "but" more - other hubsofts havn't problem with "buggy client" and older ptokax too .. :-) is this problem so big ... or is it only way how to block :-)

[Tw?sT?d-d?v]

Originally posted by er.nest
maybe ... :-) .. for many users isnt ptokax now reachable

yeh ... bastya_elvtars you saying true - bugs on connection part of program ( and i still dont know which is it ... on capture of comunication is all ok if i know ... but to this tema i can debate with ppk again :-)

... hehe ... one "but" more - other hubsofts havn't problem with "buggy client" and older ptokax too .. :-) is this problem so big ... or is it only way how to block :-)

Debate it with PPK all you want ..Untill PPK thinks it isnt a buggy client he not gonna allow it to get in ptokax hubs

[blackwings]

Originally posted by er.nest
maybe ... :-) .. for many users isnt ptokax now reachable

yeh ... bastya_elvtars you saying true - bugs on connection part of program ( and i still dont know which is it ... on capture of comunication is all ok if i know ... but to this tema i can debate with ppk again :-)

... hehe ... one "but" more - other hubsofts havn't problem with "buggy client" and older ptokax too .. :-) is this problem so big ... or is it only way how to block :-)

the difference between the latest ptokax and ynhub  and other hubs, is that ptokax purposly doesn't allow any kinds of bugs it can find in the info sent to the hub. The reason is to force people to leave the old buggy clients and upgrade to new clients ;)

[Stravides]

Thats all well and good, but

[11:22:57] *** Connecting to rpgbooks-cymru.no-ip.org:412...
- [11:22:58] *** Connected
- [11:23:00] *** Disconnected

is not handled very well is it... can you please look to input a message - sorry Client Banned from this Hub - please change your client

otherwise users may think your hub to be deceased !

I am asking this as there are a lot of users that use this client including myself in the hub.  

You have gone to the trouble of banning this client - I agree with the why, but please can you add a little message so that the users are in no way confused as to WHY they cannot get in.

regards

[Thor]

Originally posted by bastya_elvtars
Why the hell do you want to allow rmDC? It never worked normally here.

Because i want more user :-)  The maker of the PtokaX have right, that is a buggy client, so the hub have to ban it, but when the user is being banned, ha want to get a banmessage =)
Connecting...
Disconnect...
Its not a banmessage i think. So it will be very good, that in the PtokaX 0.3.3.3 i see it:
Connecting...
You have a buggy client (rmDC), please change it and reconnect!
Disconnected...

I said it: we know, that rmDC is a shit, but the users don't...

[6Marilyn6Manson6]

Its not a banmessage i think. So it will be very good, that in the PtokaX 0.3.3.3 i see it:
Connecting...
You have a buggy client (rmDC), please change it and reconnect!
Disconnected...

Mm no, This is exact:

Connecting...
You have a shit client (rmDC), please change it and reconnect!
Disconnected...

:P c ya

[Stravides]

Originally posted by 6Marilyn6Manson6
Mm no, This is exact:

Connecting...
You have a shit client (rmDC), please change it and reconnect!
Disconnected...

:P c ya

Irrelevant what you think of the client - we accept it is banned, but a litle more error friendly response is needed. 

Also I do not believe that profanity is required in the hubsoft - it was bad enough with your ass is banned - do not need any more of this ilk.

I think a generic message to change the client would be better.

[6Marilyn6Manson6]

Originally posted by Stravides

Originally posted by 6Marilyn6Manson6
Mm no, This is exact:

Connecting...
You have a shit client (rmDC), please change it and reconnect!
Disconnected...

:P c ya

Irrelevant what you think of the client - we accept it is banned, but a litle more error friendly response is needed. 

Also I do not believe that profanity is required in the hubsoft - it was bad enough with your ass is banned - do not need any more of this ilk.

I think a generic message to change the client would be better.

Spiace to contradict to me to you but rmDC it deserves this message because it does not respect the GNU General Public License. c ya

[Stravides]

Originally posted by 6Marilyn6Manson6

Spiace to contradict to me to you but rmDC it deserves this message because it does not respect the GNU General Public License. c ya

Spiace - sorry doesnt compute

As far as the Client deserving it thats one thing - the user using it - NO !!  Thats like slagging off users who use microsoft because bill gates is allegedly a knob ???

There should be no need to resort to defamatory messages for client usage

[PPK]

Originally posted by er.nest
and i still dont know which is it ... on capture of comunication is all ok if i know

I know, is hard to see this bug...

    while(sData != NULL && sData[0] != NULL) {
        if((cTemp = strchr(sData, ' ')) != NULL) {
            cTemp[0] = NULL;
            cTemp++;
        }

        switch(sData[0]) {
            case 'N':
                // Supports starting with N
                break;
            case 'Q':
                // Supports starting with Q
                break;
            case 'U':
                // Supports starting with U
                break;
            case 'B':
                // Supports starting with B
                break;
            case 0: {
                // PPK ... corrupted $Supports ???
                int imsgLen = sprintf(msg, "[SYS] Bad $Supports from %s (%s) - user closed.", curUser->Nick, curUser->IP);
                UdpDebug->Broadcast(msg, imsgLen);
                curUser->Close();
                return;
            }
            default:
                // PPK ... unknown supports
                break;
        }

        sData = cTemp;
    }

Client send corrupted supports and is disconnected

[6Marilyn6Manson6]

PPK I love you LOL

[Stravides]

Originally posted by PPK

Originally posted by er.nest
and i still dont know which is it ... on capture of comunication is all ok if i know

I know, is hard to see this bug... :D

    while(sData != NULL && sData[0] != NULL) {
        if((cTemp = strchr(sData, ' ')) != NULL) {
            cTemp[0] = NULL;
            cTemp++;
        }

        switch(sData[0]) {
            case 'N':
                // Supports starting with N
                break;
            case 'Q':
                // Supports starting with Q
                break;
            case 'U':
                // Supports starting with U
                break;
            case 'B':
                // Supports starting with B
                break;
            case 0: {
                // PPK ... corrupted $Supports ???
                int imsgLen = sprintf(msg, "[SYS] Bad $Supports from %s (%s) - user closed.", curUser->Nick, curUser->IP);
                UdpDebug->Broadcast(msg, imsgLen);
                curUser->Close();
                return;
            }
            default:
                // PPK ... unknown supports
                break;
        }

        sData = cTemp;
    }

Client send corrupted supports and is disconnected :rolleyes:

But can you send client a message before disconnect ?? I do not know - that is why I ask - I do not need fascetious commentary, just an answer please..

regards

Stravides

[Naithif]

Hi all

Well, GDC++ (based on StrongRC9f2) also breaks GPL as not releasing the source
(and also VERY buggy too  : )
Link: www.glesius.it
Anybody knows a way to block it? ;D

[Thor]

I cant download it from the link, maybe if you send me it to see how it send myinfo, or maybe it has an own tag (the easiest way )

[Pothead]

Pretty sure is has sommit like
glesius.it
in it's description.

[Cêñoßy†ê]

Pretty sure is has sommit like
glesius.it
in it's description.

Description:      [/]-=VirtualHub.it=- & -=Glesius.it=-
Tag:         <GDc++    V:1.00 RC9,M:A,H:11/0/0,S:8>

[Naithif]

Hi all

These are all default options, doubt anyone would leave them this way.
And with RC9f2 descript can be totally cleared as i remember, i'm taking down gdc already, i had it, but it was buggy, so i deleted it.

[Naithif]

Also i couldn't detect [AI]Fake with any op or "half-op" clients with slotlocking on, is there any way of a script that could detect it?

[bastya_elvtars]

Also i couldn't detect [AI]Fake with any op or "half-op" clients with slotlocking on, is there any way of a script that could detect it?

If an op-client cannot detect a fak0r mod, then hardly can I believbe it is accomplishable serverside...

[Naithif]

I thought that they might have some bug like rmDC++... but as you can go to any hubs with a client like AI with 3-4 ops constantly checking, and not even zion, ldc or dcdm could detect it... So, if hubside detection is not possible then it's a --problem--...
I've seen so many client check in serverside detection... Everyone asked to disallow strong or such, but those clients not really do anything bad, AI fake, and DC stealthy for example do, and they can't be detected, because they're based on default dc++ with no specials, just some extra slot lock, full limit, and hammering functions? Well, i would rather allow rmDC++ then them...