Protect website background with USB key

USB keys are no stranger to friends who often use banks, but how can they protect their websites?
Required materials: a useless USB flash drive (provided that it can be used), a USB flash drive mass production tool, and an e-language compiling environment
:

========================================================== ========================================================== ====================
This time my USB key program is open-source and I hope it will not be changed to copyright.
Use DES to encrypt your string, and then create an encrypt. sys
Then download the source code of main, modify detext = to decrypt the data (read the file ("encrypt. sys"), "Your DES encrypted string", # DES algorithm)

Click to download the E language source code: http://up.2cto.com/2011/1017/20111017102614321.zip
 

Download and click to download PHP code: http://up.2cto.com/2011/1017/20111017102637626.zip
 

Open server. php
Set

 

Modify
The following uses wordpress as an example to illustrate how to call
First upload server. php to the root directory of the website, then open the wp-login.php and add a sentence at the top
Require ("./server. php ");
Then open wp-admin/admin-header.php
Add one sentence at the top
Require ("../server. php ");
For example

Save
Then open wp-content/
Create a directory named sEsSi0ns4v3p4tHqk
Then open the sEsSi0ns4v3p4tHqk directory and create a logs
This is used to store the session and used code.
In this way, the website and program have been completed.
The following will be a mass production program into the U Disk
Write an autorun. inf
Content is
[Autorun]
Icon = ico. ico (Icon)
Open‑key.exe (compiled file name)
Then, use the production tool to write the USB flash drive and set the read-only (ReadOnly)
This usb key is complete.

Now insert the USB flash drive and automatically autorun. the USB key is displayed. After the USB flash drive is unplugged, the program exits automatically.
P.S. If you find that the copyright is changed, you will not issue the source code next time.

From: network security technology blog (www.safe121.com)