08.09.2009, 16:59
Updating pawn is likely to introduce unwelcome incompatibilities. We have also made many patches to the pawn runtime ourselves that would need to be reimported in to the latest base.
Security concerns in terms of pawn are mild because scripts only run on the server, not the client, and most server owners aren't accepting random amx files from people they don't trust. Most servers run their own scripts which they compiled themselves. Server owners have to accept that, even without vulnerabilities in the pawn runtime, there is always a chance a script you don't have the source for or didn't compile yourself could contain something malicious.
That being said, it's possible for us to fix that reported vulnerability without updating pawn. The guy who found the vulnerability is actually the same guy who wrote the pawn decompiler and I think I was the first person he reported the problem to.
Security concerns in terms of pawn are mild because scripts only run on the server, not the client, and most server owners aren't accepting random amx files from people they don't trust. Most servers run their own scripts which they compiled themselves. Server owners have to accept that, even without vulnerabilities in the pawn runtime, there is always a chance a script you don't have the source for or didn't compile yourself could contain something malicious.
That being said, it's possible for us to fix that reported vulnerability without updating pawn. The guy who found the vulnerability is actually the same guy who wrote the pawn decompiler and I think I was the first person he reported the problem to.

