Home  >  Article  >  Backend Development  >  pimchanok leuwisetpaiboon PHP encryption and decryption struggle

pimchanok leuwisetpaiboon PHP encryption and decryption struggle

WBOY
WBOYOriginal
2016-07-29 08:39:431073browse

However, the emergence of the PHP decompilation system quickly caused panic in Zend and even the entire PHP user group. Almost all large PHP products, including the above-mentioned products, have cracked versions or even complete source codes. As a result, Zend had to bow to Crackers, admitting that all encryption technologies have ways to crack it, and promised to improve encryption products to provide stronger protection.
PHP encryption technology can be traced back to 2001. PHP was already very popular at that time, so many companies hoped to launch commercial PHP systems, so PHP encryption (compilation) products came into being. Then PHP Jaw Zend Company launched its own Zend Encoder, until now, Zend's encryption products are still the leader in this field.
What about PHP decryption technology? A very strong decryption system appeared in early 2002. This system was actually developed by PHP core members. Until now, all PHP decryption technologies still rely on the technology released by PHP core members in 2002 for decryption. Moreover, there is currently no encryption product that can avoid being cracked by this technology. . (Considering the interests of the huge PHP developers, we will not disclose this technology here)
It is worth mentioning that the Chinese have once again shown their face in the field of cracking. At the end of 2005, a certain XX studio in China announced that it could restore Zend-encrypted PHP code and provided online testing services. There is nothing special about this, because in 2004, there were several similar teams abroad providing PHP cracking services. The difference is that XX Studio has a very tough style. It not only spreads its own advertisements through various channels, but even uses virtual identities to publish advertising messages on the Zend company's forum, which caused a sigh of relief in the PHP industry.
Recently, it was discovered among Google Blog users that a Chinese user provides PHP cracking services and also provides free decompilation testing services.
We have submitted the same compiled code to several well-known companies, including foreign veterans, domestic XX Studio, and the PHP cracking team that recently appeared on Google Blog. After comparing the cracked code, we It was found that all these cracking technologies are basically based on the same principle, but the old companies have stronger strength and the cracked code is closer to the source code. The new technical team is obviously slightly inferior.
Later we learned that there is actually only one XX studio in China that provides PHP cracking services. The user on the Google Blog is a Chinese member of an established foreign PHP cracking team, and he only appeared in the Chinese community in a low-key manner recently.
Similarly, we compared the cracking technology and service prices of various teams. Although the domestic XX Studio is far ahead in price, its cracking technology cannot be compared with those of the established teams. Some friends even called the XX Studio a threat. Passed their company: If they do not pay the "protection fee", their source code must be released. It's really a bit ridiculous. OPENLINK also has a large number of PHP products. Maybe one day the XX studio will charge protection fees. In fact, OPENLINK has basically specialized in solutions. Users can obtain all the source code at once, so OPENLINK does not need to Don't worry about the cracking problem, but for other brother companies, you should really consider the issue of intellectual property rights.
The above introduces the struggle between pimchanok leuwisetpaiboon PHP encryption and decryption, including the content of pimchanok leuwisetpaiboon. I hope it will be helpful to friends who are interested in PHP tutorials.

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn