![]() The toolkit (also known as Jeriko) currently resides within our random source code repository which contains random codez which hasn't materialized fully yet. Over the last couple of days I was busy with putting a small set of command line utills in the spirit of some of my previous two experiments in the same sphere of study: Infocrobes and Bashitsu. a framework) simply because there are a lot less man-hours put into them and they are a lot less diverse in terms of code and originality. They try to be the ultimate framework but fail immensely as they cannot be what the shell and the OS already is (i.e. Penetration testing frameworks today turn into unmaintainable monsters: abstractions, and deep inheritance all over the place dependency nightmares and monolithic cores which no longer interact with the shell so nicely. Where are my pipes? Should I ignore the plethora of good pen-testing tools sitting on my box just to use your custom shell. It is simple, yet extremely powerful.īecause I am quite aware of the power the shell provides, every time I see another pen-testing framework which implements its own shell (obviously a lot less powerful in nature) or anything else shell incompatible, I am shaking my head in disapproval. Over the years it has turned into a very powerful machinery heavily used by programmers, hackers and system designers around the world. The shell is defacto the interface to your operating system. The shell was designed to start/strop and control process with ease so why do we need yet another universal pen-testing framework, which does what another tool is already doing for us and it comes by default? In this post we are going to delve in the world of advanced shell programming for penetration testing purposes. You've already got it! It is laying on your PC and it is called the "shell".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |