1. Skip the browser and rewrite the communication data directly.

2. Modify the browser so that it can read and write any domain cookie locally.

3. Using the signature script, the browser can read and write any domain cookie locally (there is a security problem).

4. Deceive the browser to get a fake domain name.

These include:

Methods 1 and 2 require professional programming knowledge and are not suitable for ordinary users.

There are two ways to realize method 3:

1, use the signature script directly, without signature verification, but it causes serious security problems, because everyone has to surf the Internet. If you do this, your hard disk file will be destroyed. ...

2. Sign the script before using it, but it needs a special digital signature tool, which is not suitable for ordinary users.

Method 4 seems to be the most suitable. Domain name spoofing is very simple and does not require any tools (of course, it would be better if your machine is equipped with a web server). Let me take Ninetowns as an example to explain the cookie spoofing process based on this method (any server-side bug mentioned below has been improved, so this article has no security impact on Ninetowns):

Note: The cookie we are talking about will not leave a trace in the cookie file on the hard disk, that is, it will only be generated in the browser's session. If the browser closes (session ends), the cookie will be deleted!