* Isolate all pattern listing to manage them without read all code

* close #4

* close #6

* cf #6

* Use () array format better to take in consideration spacing in pattern

* Some hack are executable and build outside php context
* Ignore flat file
* Try to find some part of them

* Use white when any colore has been asked

* Run a specific clean WP actions

* Corrupted files are not related to a specific CMS
* Better to isolate this function from clean_spip function

* Some attack on wp provide differents files patterns, use them to improve detection

Inform about crontab content without display itself

* verbose is to verbose and useful information can be lost
* list is a new option to display only relevant informatoion about detection

* This version looks working on some use case :)

* Enable multiline feature
* Add regex behavior to some other usecase

* When any spip looks hacked display a nice green text

* New pattern to check in files

* New use case new file listing

* Before to delete inform about file with specific pattern name

* Use unique syntax variable as ${..}

* Isolate search pattern function to remove specific files

* If plugins is present in directory we can ignore it
* In some case could be ignore some licit path, but before to propose a better way, looks acceptable

cam.lafit a rédigé 1 year ago et cam.lafit a validé 1 year ago

* some typo
* add verbose explanation

* If a pattern is found by default only display this information
* On verbose mode provide full listing

* Use a loop to check some pattern to check in file

* Disable by default all dry-run execution
* Propose a succint display to get essential information

* see #1
* As we can set pattern on deletion we can be more accurate about file to scan and delete

* Some file to delete contain yet a base64, prevent to display twice some file yet cleaned

* If a pattern path is found act as potential hacked spip

* Display files wich contain some pattern to check

* when find delete some file display them to inform