Skip to content

Commit 9b665bd

Browse files
committed
doc: explain why numeric suffixes on function names are avoided
1 parent 2113d6d commit 9b665bd

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,8 @@ The pool names are intentionally generic — they are indistinguishable from fun
108108

109109
On top of that, junk functions and randomized routing tokens add further noise: each build looks like a different application, not a variant of the same tool.
110110

111+
> **Design note — why no random numeric suffix (`fetchClusterStatus_4823`):** appending digits would make every name look machine-generated at a glance — no real PHP codebase does this. It would destroy the "legitimate app" camouflage and, worse, create its own YARA signature (`[a-zA-Z]+_\d+`). The pool size (275 names, ~20 drawn per build) already makes per-build combinations astronomically large; suffixes add risk, not safety.
112+
111113
### 2. Routing token randomization
112114

113115
The AJAX routing parameter `?feature=` and its values (`shell`, `hint`, `pwd`, `upload`) are replaced by random alphanumeric tokens generated at build time and injected coherently into both PHP and JS.

0 commit comments

Comments
 (0)