But but but muh f'~~~{strings}~~~'
. I would argue they are way more convenient than 'something'.encode('hex')
Cool new feature arriving probably today!
Itās gonna take the working hours
options to the next levelā¦
Letās stomp those Behavioral Network Filters by being too Behavioralā¦
Take a look at: https://github.com/operatorequals/covertutils/blob/master/covertutils/handlers/dateable.py
It makes the backdoor NOT respond at all (yet evaluate all input) on:
- non-working hours
- Weekends (you get to choose which days are weekends)
- Holidays (Christmas and New Years Eve are defaults, can be expanded)
- Easter Holidays (you can disable it, as a lot of countries do not have Easter)
Defaults are set and refer to Europeās standards.
Everything gets evaluated at backdoored hostās local date and time so no need to estimate timezones. 9-5
means 9-5
for wherever your backdoorād host resides in the worldā¦
Couple that with a Reverse HTTP shell andā¦
Before I start on super serious PRs, you mind me setting you up with PyFlakes and Bandit on TravisCI so you can do style checks and some simple static analysis?
In my opinion style checks come last and are the least needed. But anything that can help debugging and that Py2/3 compatibility is more than welcome!
See you on github!
Reasonable people can differ, but as someone who has maintained code for a while, style is a ādo as you goā thing. Itās a lot easier to do it right as you add new code than to go back and fix it later.
I see. The thing is that I donāt like the pep8
a whole lot. The snake_case
in functions is something I hate for example, I prefer camelCase
for functions and CapitalizedNames
for classes.
So, I am not really planning to fully follow the pep8
. The new line
policies and the import order
are really good directives though.
Let me handle the code, as I want the packages API to follow the principle of least surprise
on names and symbols in general. Also changing method names now will fuck many things up badly (like some presentations).
So yeah! Letās write compatibility and functionality code!
flake8 doesnāt give two craps about your variable, class, or function names (thankfully, or else Iād be in trouble too). It checks to see if the code can compile/run and if you have spacing/indentation/etc. issues.
Bandit checks for known, obvious security and optimization issues.
Do your magic then! See you on the other side!
Glad you are not a criticizing moron about the pep8
.