Hello, H3athe4d here, today I bring you some topics on metasploit and it’s very basics, you may call it as it’s foundation and the layout. So,in this post, I will go through the MSF framework in a definitive way. for anyone following my posts.
First and foremost, let me explain why people need metasploit, and why it is being used in penetration testing in a more successful way. They key to success with metasploit is it’s modular structure, and it’s flexibility with it’s different user interfaces and it’s functionality. I will discuss here the architecture of the metasploit framework.
The architecture of the metasploit framework is based on primarily 3 things, first is “libraries”, second is “interfaces”, and the third and the most important one to the user is “modules”.
The Library consists of:
a.) REX
b.) MSF CORE
c.) MSF BASE
The Interfaces consists of:
a.) CONSOLE
b.) CLI
c.) GUI
d.) COMMUNITY EDITION
e.) Armitage
although MSG GUI and Armitage both fall under the GUI interface, both aren’t the same, as well as this applies to the community edition of the metasploit. There are different “plugins” and “tools” in the metasploit directory that serves the libraries of the framework and then this whole bunch of library in turn serves to the interface, which the users rely on.
Then, there is this, “MODULES”, it consists of:
a.) Payload.
b.) Exploits.
c.) Encoders.
d.) NOPS.
e.) Auxiliaries.
I will elaborate all these terms at a later point, but, let’s concentrate on how the framework is “modular” and works in a perfect way, as it should. The metasploit filesystem and the libraries consists of:
LIB || DATA || TOOLS || MODULES || PLUGINS || SCRIPTS || EXTERNAL ||
So, this was my first post regarding METASPLOIT< I will continue explaining the whole framework in bit’s of posts, easy to follow, and understand the whole framework, catch you people at a later time.