Hi,
this post just to say that I saw the encryption constant length (2113444489) and if i recall correctly, ASProtect had a problem with 8 digits encryption constants (2 digit less than enigma) because crackers were able to bruteforce or otherwise get it. So I think it would be better to extend it to 128 bit or higher(16 digits or more).
About encryption constant
Re: About encryption constant
Hi Gabriele, really, 2113444489 is not a 8 digit number, it is just a Dec constant converted from Hex 0x7DF89A89, i.e. 4 bytes constant.
I could agree that bruteforce may sometimes help. But imagine what time is needed to get this secure value of particular application?
There is another side why this constant is so little. It is being embeded into each registration key (if key is generated with Decrypt Section). If we increase this constant to 128 bits, the registration key will be also longer on 21 symbols (using Base32 for keys). It could be well if you are using long keys, but a very huge deal for developers who use phone sales and a very short registration key.
Anyway, if I find any application, for which this constant had been extracted with bruteforce, I will add a new secure features with longer secure constant.
I could agree that bruteforce may sometimes help. But imagine what time is needed to get this secure value of particular application?
There is another side why this constant is so little. It is being embeded into each registration key (if key is generated with Decrypt Section). If we increase this constant to 128 bits, the registration key will be also longer on 21 symbols (using Base32 for keys). It could be well if you are using long keys, but a very huge deal for developers who use phone sales and a very short registration key.
Anyway, if I find any application, for which this constant had been extracted with bruteforce, I will add a new secure features with longer secure constant.