I hereby claim:
- I am rahuldhawan291 on github.
- I am dhawan291 (https://keybase.io/dhawan291) on keybase.
- I have a public key ASARgNoNdQPJWPw9zON7-J8eX-t0ohCwc-X4JdrS3HyUCgo
To claim this, I am signing this object:
// Determine linux distribution and version | |
cat /etc/issue | |
cat /etc/*-release | |
cat /etc/lsb-release | |
cat /etc/redhat-release | |
// Determine kernel version - 32 or 64-bit? | |
cat /proc/version | |
uname -a | |
uname -mrs |
{ | |
"Rules": [ | |
{ | |
"Reason": "AWS API Key", | |
"Rule": "AKIA[0-9A-Z]{16}", | |
"Noise": 3 | |
}, | |
{ | |
"Reason": "AWS Access Key ID Value", | |
"Rule": "(A3T[A-Z0-9]|AKIA|AGPA|AIDA|AROA|AIPA|ANPA|ANVA|ASIA)[A-Z0-9]{16}", |
I hereby claim:
To claim this, I am signing this object:
Web Application Hacker's Handbook Task checklist as a Github-Flavored Markdown file
This gist includes my work summary and my experience during Google Summer of Code'18 with Metasploit
When interacting with a Meterpreter session in Metasploit Framework, the user is either in direct control of the session prompt or has backgrounded the sessions. To execute post modules the user must background the session and then interact with the console to find modules they wish to run.
The aim is to enhance the user experience by making it easier for them to navigate through the list of available Post Exploitation modules and available extension commands for the active session. By launching a separate interaction as a web console, the user gains the flexibility of having module lists available in a point and click context driven menu, while still being able to have a quick interaction directly with the session. Also, creating a view that is associated to an individual session the context of the menu can filter modules and extension that do not apply