Why it's not safe to weave dreams.

Someone around said that.

Reply content:

Someone around said that.

There is a problem with the architecture of the 1,dedecms itself. A large number of global variables, using variables of the weird variables $$ , MySQL executes the SQL is self-assembled, that is, the use of Mysql_escape_ String also does not cover its own logic errors. Instead of using PDO for parameter execution.
2, widely circulated, nature is a lot of people take to study the burrow.
3, the official website "Boycott Japanese goods".
4, round-robin

Weaving dreams is notorious, and there is no reason to casually question it, unlike PHP.

Weaving the hole in the dream itself, and the official lazy to fix the loopholes, in the webmaster and host business circles have broad consensus. You can inquire about how many PHP hosts have explicitly refused to weave a dream from the outset, or refused to weave a dream after the server was attacked.

It's not good to start writing 1.
2 getting bigger, more complicated, more bloated.
3 of people are much more concerned. Just as many windows vulnerabilities

1. More Vulnerabilities
2. Officials seem to have nothing to mend the vulnerability
3. As an open source, there is a risk in itself (I mean to be dug up by someone)

For not inviting me to develop

