• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 397
  • Last Modified:

Encryption and Decrypting Illegally

Hey all

I seen the following link on whilst trying to find out more about encrypting:

Anyway, my question is how can you stop somebody creating a dummy DLL with the same naming conventions (assuming of course they havent use obfescution(sp?) to hide things), and decrypting the info with your own libraries?

Does the following section of code (when creating the keys) really help limit that?  And also I'm assuming that you can put any values in for the key and iv?  Or am I wrong?
byte[] key = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 
              13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24};
byte[] iv = {8, 7, 6, 5, 4, 3, 2, 1};

Open in new window

1 Solution
1) sign your dll ... its a super pain to get around this (i.e. hacking the CLR painful)
2) use public key encryption for any data you want to keep from changing ... they will be able to view the data but not change it.
angus_young_acdcAuthor Commented:
How do you go about doing 1 and 2?  Would that solve my problem of having the byte key in every form?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now