Offline
Forum
Off Topic FUD crypters
FUD crypters
8 Antworten
1 
The logic behind it goes like this:
Client requests a page from Server.
Server encrypts the page with salt and send it over.
Client receives the page and encrypts it again with own salt.
Client sends the double encrypted page back.
Server decrypts page with own salt and sends page back.
Client decrypts page with own salt and reads it as html.
Using this, no one can crack through, -- well not with the time they're given.
Apache uwu hat geschriebenWell ssl (aes 256) is pretty damn secure.
The logic behind it goes like this:
Client requests a page from Server.
Server encrypts the page with salt and send it over.
Client receives the page and encrypts it again with own salt.
Client sends the double encrypted page back.
Server decrypts page with own salt and sends page back.
Client decrypts page with own salt and reads it as html.
Using this, no one can crack through, -- well not with the time they're given.
The logic behind it goes like this:
Client requests a page from Server.
Server encrypts the page with salt and send it over.
Client receives the page and encrypts it again with own salt.
Client sends the double encrypted page back.
Server decrypts page with own salt and sends page back.
Client decrypts page with own salt and reads it as html.
Using this, no one can crack through, -- well not with the time they're given.
Well... it has nothing to do with FUD crypters. FUD crypters are used to encrypt trojans malwares rats etc so antivirus cant detect them.
1
2
3
4
5
6
7
8
9
10
11
12
2
3
4
5
6
7
8
9
10
11
12
void encryptData(char *dat, unsigned long datlen, char **out){
char *enc_data = malloc(datlen);
unsigned long i;
for( i = 0; i < datlen; i++ ){
if( i % 2 == 0 ){
enc_data[i] = trans_table_1[data[i]];
} else {
enc_data[i] = trans_table_2[data[i]];
}
}
*out = enc_data;
}
Btw, be careful with the way you generate your random numbers, they need to be random but still cannot be repeated multiple times.
Also, once you get to the other side, you need to convert the unencrypted data pointer to a function pointer, which requires a compiler that is not too type-safe. This is a fairly big ordeal, but it's not very easy to convert a char pointer to a function pointers without a lot of programming experience.
EDIT: Btw, just to give you an example of how to convert the unencrypted data back to a form that C will be okai with:
1
2
3
4
2
3
4
typedef void(*func)(); [...] func my_malware_function = (func) data; my_malware_function();
EDIT2: Also, PartyPooPer, don't assume the worst. He could be trying to test his anti-virus in a sandbox environment and needs to get it into the virtual machine without it being tampered with. ( Or even possibly to get a windows crack past the anti-virus
) 3× editiert, zuletzt 29.01.12 15:28:14
DannyDeth hat geschriebenTranslation tables, they are effective at getting rid of patterns in data, which is what the anti-virus would use to find a trojan or other malicious software:
Btw, be careful with the way you generate your random numbers, they need to be random but still cannot be repeated multiple times.
Also, once you get to the other side, you need to convert the unencrypted data pointer to a function pointer, which requires a compiler that is not too type-safe. This is a fairly big ordeal, but it's not very easy to convert a char pointer to a function pointers without a lot of programming experience.
EDIT: Btw, just to give you an example of how to convert the unencrypted data back to a form that C will be okai with:
Where "data" is the unencrypted data which makes up the function.
1
2
3
4
5
6
7
8
9
10
11
12
2
3
4
5
6
7
8
9
10
11
12
void encryptData(char *dat, unsigned long datlen, char **out){
char *enc_data = malloc(datlen);
unsigned long i;
for( i = 0; i < datlen; i++ ){
if( i % 2 == 0 ){
enc_data[i] = trans_table_1[data[i]];
} else {
enc_data[i] = trans_table_1[data[i]];
}
}
*out = enc_data;
}
Btw, be careful with the way you generate your random numbers, they need to be random but still cannot be repeated multiple times.
Also, once you get to the other side, you need to convert the unencrypted data pointer to a function pointer, which requires a compiler that is not too type-safe. This is a fairly big ordeal, but it's not very easy to convert a char pointer to a function pointers without a lot of programming experience.
EDIT: Btw, just to give you an example of how to convert the unencrypted data back to a form that C will be okai with:
1
2
3
4
2
3
4
typedef void(*func)(); [...] func my_malware_function = (func) data; my_malware_function();
Thank you. This will come in handy.
EDIT: Also, you are probably going to have to verify the data, in this case I would recommend Fletcher's algorithm, it's quite effective.
1× editiert, zuletzt 28.01.12 12:08:20
1