Cool beans, cant wait for port
What conveniences though? In my experience py3 was nothing but conveniences 
print took some getting used to but its small price to pay for all the goodies that come with it.
I am mainly talking about my beloved "string here".encode(whatever) function!
It even supports zip.
I know that strings are fundamentally different in Py3 (and I can see that it is a more correct approach) nevertheless I can’t help but use Py2 str like bytearrays…
Well… At least you arent in denial and agree that new ways are kosher ways But in py3 you can too use binary strings: b'raw binary string'. But you knew that i guess.
Computer community doesn’t need more fellows in denial.
Did you see what happened with exa as an ls alternative on Hacker News (https://news.ycombinator.com/item?id=14923362)? Most of the mess was made by denial of a better tool than the legendary ls. The rest by guys hating the guys on denial.
I just can’t get used to hexlify and such stuff. It gets frustrating at times, but If Py3 is the new better way, I don’t want to code Py2 just by myself.
Yet, Py2 is the standard, and, in the other hand, I can see why and I don’t believe that it is only that people are used to code in certain ways… I find it a little more intuitive.
Anyway, this conversation can take forever. This topic is unsolvable. You can screw a screw with a knife and cut an apple with a screwdriver, but I guess there is a reason we do it the other way. Tools are good at things. Unifying tools is handy but difficult.
1 Like
Once py3 is complete can i start lobbying for spaces and pep8 formatting?
Yeah. My pylint score is about -17 already (claps).
Do not bother that before the code gets passed through an autopep.
The thing is that I started coding for myself, and there is legacy code in there, even if legacy means 7 month old. All my code is bloated with spaces between arguments and parentesis because “that’s how I usually do it” (it’s a Vivek’ish coding style). I also prefer tabs to the point I sed my code to insert tabs instead of 4 spaces.
God am I heretic…
1 Like
I was tab fan in the past as well. Thing is it creates too much friction when majority out there is using spaces. And so i capitulated - if you cant win then join them And now tabs are discouraging contribution because i know there will be nonsense i have to deal with…
This is probably one of the best python package i am going to use… Yet to try it out but im sure it is going to be awesome…
Yeah man, i support … I am still figuring out a way to change my style… Using cap is just too addictive
But since it is no longer supported/encourage. Gonna try using spaces.
@rokups, i still love using py2.7.
You can use both anyway by installing them differently unless you are too much in love with py3
The tutorial is ready and already published in 0x00sec post.
Free beers can be won by reading it (you have been warned)…
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…
2 Likes
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…
2 Likes
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.
1 Like
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.
3 Likes