Bailar
07-31-2009, 10:08 AM
I have a program which include main module and some dlls. I need to crack one of this dll. After decompilation main module with ildasm I see some publickeytokens
.assembly extern somename_1
{
.publickeytoken = (B7 7A 5C 56 19 34 E0 89 )
.ver 1:0:5000:0
}
.
.
.
.
.assembly extern somename_N
{
.publickeytoken = (79 82 76 05 57 09 C9 8A )
.ver 2:1:5000:0
}
When I change some bytes in dll with hex editor program run with exeption becase of strong name. If I remove strong name from dll I also have exeption becase of .publickeytoken in main module.
Main module protected with "Remotesoft .NET protector" and I can see only class' names but not IL codes. That's why I can't decompile main module with new .publickeytoken (or remove it). What should I do in that case?
.assembly extern somename_1
{
.publickeytoken = (B7 7A 5C 56 19 34 E0 89 )
.ver 1:0:5000:0
}
.
.
.
.
.assembly extern somename_N
{
.publickeytoken = (79 82 76 05 57 09 C9 8A )
.ver 2:1:5000:0
}
When I change some bytes in dll with hex editor program run with exeption becase of strong name. If I remove strong name from dll I also have exeption becase of .publickeytoken in main module.
Main module protected with "Remotesoft .NET protector" and I can see only class' names but not IL codes. That's why I can't decompile main module with new .publickeytoken (or remove it). What should I do in that case?