What's it gonna do to protect you from reversing the digital signature?



  • Objective: Provide adequate protection against reversing of assembly.

    What has already been tested: It was signed by the strict name of all the project kits, but in fact, it doesn't give anything, and it's bluntly reflexed. It was thought to send some parameters to the server, for example. SHA1Token (sighs)sha1 Hech from the last 8 byte public key. So the calculation was that the reverser would not be able to counteract the token, but unfortunately the idea had not been worked out, the public key (and the token) could be distinguished by the same stubbornness. sn.exe from the studio set.

    Question: the use of digital certificates (test/commercial) to protect (signature with help) signtoolWhat's the difference between signing a strict name? Can we put one on another?



  • The objectives of the digital signature are a certificate of authorship and integrity. I mean, for the signed datablock, we can say who signed it and that the datablock hasn't changed since the signing. The signature has nothing to do with reversing.




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2