exploit code

[A v a r a]

I already disable those specials chars in my HTlauncher by using Hex Editor .

Your further elaboration regarding that matter is deeply appreciated. As to how and how really...

[Lunatic]

just message me if you are interested :)

[dTantra]

Client side blocking is a very shitty way to do it, instead why not filter packets like the big servers do??

struct MSG_STANDARD
{
WORD wType;
WORD wSeq;
WORD wPDULength;
WORD wDummy;
DWORD dwClientTick;
int nID;
};

bool ValidString(char * cString){
	string lFilter = "!@#$^&*()_+-=[]{}|;:,./<>?`~ ";
	int iResult = 1;
	int i, j;
	bool Continue = false;
	const char * cFilter = "!@#$^&*()_+-=[]{}|;:,./<>?`~ ";


	string sString = string(cString);


	if(sString.size() == 0)
	{
		return true;
	}


	for ( i = 0; i <= sString.size() - 1 && iResult == 1; i++)
	{
		if(cString[i] < 0)
		{
			return false;
		}
		else if(!isalnum(cString[i]))
		{
			Continue = true;
			for( j = 0; j <= lFilter.size() - 1 && Continue == true; j++)
			{
				Continue = true;
				iResult = 0;
				if(cFilter[j] == cString[i])
				{
					iResult = 1;
					Continue = false;
					break;
				}
			}
		}
	}


	if(iResult == 1)
	{
		return true;
	}
	else
	{
		return false;
	}
};


bool ValidName(char * cName, int cSize)
{
	int cResult = 0;
	for (int i = 0; i <= cSize - 1; i++)
	{
		if(cName[i] < 0)
		{
			return false;
		}
		else if(!isalnum(cName[i]))
		{
			return false;
		}
	}
	return true;
}

[Lunatic]

Client side blocking is a very shitty way to do it, instead why not filter packets like the big servers do??

struct MSG_STANDARD
{
WORD wType;
WORD wSeq;
WORD wPDULength;
WORD wDummy;
DWORD dwClientTick;
int nID;
};

bool ValidString(char * cString){
    string lFilter = "!@#$^&*()_+-=[]{}|;:,./<>?`~ ";
    int iResult = 1;
    int i, j;
    bool Continue = false;
    const char * cFilter = "!@#$^&*()_+-=[]{}|;:,./<>?`~ ";


    string sString = string(cString);


    if(sString.size() == 0)
    {
        return true;
    }


    for ( i = 0; i <= sString.size() - 1 && iResult == 1; i++)
    {
        if(cString[i] < 0)
        {
            return false;
        }
        else if(!isalnum(cString[i]))
        {
            Continue = true;
            for( j = 0; j <= lFilter.size() - 1 && Continue == true; j++)
            {
                Continue = true;
                iResult = 0;
                if(cFilter[j] == cString[i])
                {
                    iResult = 1;
                    Continue = false;
                    break;
                }
            }
        }
    }


    if(iResult == 1)
    {
        return true;
    }
    else
    {
        return false;
    }
};


bool ValidName(char * cName, int cSize)
{
    int cResult = 0;
    for (int i = 0; i <= cSize - 1; i++)
    {
        if(cName[i] < 0)
        {
            return false;
        }
        else if(!isalnum(cName[i]))
        {
            return false;
        }
    }
    return true;
}

yes we can .
but we have a different kind of idea's on how to disable those characters in .exe
one of them is using offset .
don't worry i will post some tutorials how to disable it. :)

[A v a r a]

yes we can .
but we have a different kind of idea's on how to disable those characters in .exe
one of them is using offset .
don't worry i will post some tutorials how to disable it. :)

I can't wait for your tutorial mate.

[dTantra]

lol hahaha

Let me tell you why you don't want to bother with "clientside" fixing...

What happens when someone else uses a different client exe but yours to connect?
What happens when someone uses your client and just sends the packets directly without relying on the client?

The real solution at this point is to filter the string out of your packets serverside, that way you can prevent the crashing, log who does it, disconnect just them etc.

Enough of the source code for tantra was released that you can have a look and write new code to handle it. The same goes for all these dupes that people are exploiting, all you really need to do is save the character data right after they do anything important, eg: trading, buying, selling.

[A v a r a]

Client side blocking is a very shitty way to do it, instead why not filter packets like the big servers do??

struct MSG_STANDARD
{
WORD wType;
WORD wSeq;
WORD wPDULength;
WORD wDummy;
DWORD dwClientTick;
int nID;
};

bool ValidString(char * cString){
    string lFilter = "!@#$^&*()_+-=[]{}|;:,./<>?`~ ";
    int iResult = 1;
    int i, j;
    bool Continue = false;
    const char * cFilter = "!@#$^&*()_+-=[]{}|;:,./<>?`~ ";


    string sString = string(cString);


    if(sString.size() == 0)
    {
        return true;
    }


    for ( i = 0; i <= sString.size() - 1 && iResult == 1; i++)
    {
        if(cString[i] < 0)
        {
            return false;
        }
        else if(!isalnum(cString[i]))
        {
            Continue = true;
            for( j = 0; j <= lFilter.size() - 1 && Continue == true; j++)
            {
                Continue = true;
                iResult = 0;
                if(cFilter[j] == cString[i])
                {
                    iResult = 1;
                    Continue = false;
                    break;
                }
            }
        }
    }


    if(iResult == 1)
    {
        return true;
    }
    else
    {
        return false;
    }
};


bool ValidName(char * cName, int cSize)
{
    int cResult = 0;
    for (int i = 0; i <= cSize - 1; i++)
    {
        if(cName[i] < 0)
        {
            return false;
        }
        else if(!isalnum(cName[i]))
        {
            return false;
        }
    }
    return true;
}

I think this code is strong enough to handle those exploit but the problem is I don't know how to implement this thing. I have been looking everywhere to find a solution and I guess yours is the strong one. Please shred us some light regarding this code you have shared.

Ciao!