Timeline for Regarding plugin security
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 25, 2014 at 8:30 | comment | added | Pieter Goosen | It is my pleasure, glad I could help | |
| Apr 25, 2014 at 8:28 | vote | accept | user50716 | ||
| Apr 25, 2014 at 8:27 | comment | added | user50716 | Ah I see, so I should look for any code that's trying to hide what its doing and investigate that, thanks for the help! I'll be sure to use a test site as well | |
| Apr 25, 2014 at 8:18 | comment | added | Pieter Goosen | Malicious code is usually encrypted code that should not be to difficult to spot, but as I said, you should not worry to much about malicious code in wordpress.org plugins. Apart from normal bugs, they should be fine to use. And if you test plugins first on a test site and something bad happens, you will know not to use that plugin again. You should also always rerport problems with plugins to their respective authours | |
| Apr 25, 2014 at 8:12 | comment | added | user50716 | That's good advice, is there anything in particular that you look out for when looking for malicious code? | |
| Apr 25, 2014 at 8:10 | history | answered | Pieter Goosen | CC BY-SA 3.0 |