[mothered]

yeah, i did. albeit i used some code from my previous projects, and in creating this, discovered more that i could add to my current rootkit project, i.e. only breaking ss if there's a hidden port being used at the time of the calling process being launched.
i'm not sure what else i can add to it... but i don't want to add too much to this. my main focus really, in this project, is security i guess, when it comes to the iswww() function. since in the previous iteration of this project i believe it was quite easy to 'pretend' to be the target service user so that you can see all of the hidden rootkit files.

i was thinking of using one of those public web shells with fully fledged ui, for the php script... but idk. i think those are pretty lame, but my argument against that atm is that they're accessible. maybe i could have a host of scripts to choose from, at some point. that's an idea for me to note down somewhere.

additionally, i need to look a bit more into how the services write their access logs. i've hooked write() so that it breaks itself upon detecting the php script's filename in its buf, but that's all i've done in an effort to prevent log writing when viewing the php script on the server after installation. kinda sucky, as far as 'anti-logging' goes.

Excellent work. I've given you a few green apples for your effort.

I'm planning to delve Into the script this week.

there isn't much to the php script itself. i used to be fairly knowledgeable when it came to working with php, but i'm more or less clueless when it comes to it now. i know the ins and outs, but know nothing about standard functions or variables. unless i'm looking it up on the man pages lmao.
if you should have any suggestions or feedback of any kind, don't hesitate to give me a message, i'd love to hear it.

No worries at all.

Juggling between work commitments and personal computing tasks, I'll endeavor to check It out this week.