All geek questions in one place

Classic asp obfuscate

I have a small classic asp site and I am worried that the client may stop paying me. The site is located on its server, so I basically want to "turn off the switch" in case they stop paying me. I could not come up with a good way to do this, because they have a technical person who has access to the server, so any code that I write to stop the site will be easily found and modified on the classic asp site (no many pages).

So, we thought that perhaps we would confuse 2 pages of the main class so that they could not easily edit the pages, and we still have code to stop the site from working. My questions:

  • What is the best option for obfuscating classic asp code (if someone has done this before)?
  • Is there any other option that we cannot think of?

Thanks for any help you can provide.

+3
source share
6 answers

I think your energies are better for setting milestones in your project that are tied to payments. This is ideally done in steps, so that neither side feels at a disadvantage regarding the amount of work performed / the amount of money paid.

Obfuscation is easily removed and decoded, as a rule.

Remote verification of the security license opens a hole for the security of the application and can also be easily defeated.

Entering a code that "self destructs" if any action or code is not deleted is also not a big practice.

. , , . , , , . , , - , .

, . .

, StackOverflow. .

+4

? ? , , .

+1

, ; "" . .

0

, - . , , / -.

, -, , . , , , .

,

0

Microsoft Script encoder, Script , .

0

Source: https://habr.com/ru/post/1710112/

More articles:


All Articles