#5.1.0 Address rejected.

"A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk."

Read more: #5.1.0 Address rejected.

Meterpreter session 1 closed. Reason: Died

Get a shell, lose a shell, get a shell, lose a shell.  That's basically what was happening while attacking this one particular box.  I'd get a shell and moments later my shell would close on me.  I had just enough time to drop into a command line but, poof, then it was gone.

Read more: Meterpreter session 1 closed. Reason: Died

Catch ICMP (Ping) Requests

I managed to find a small hole in a web application that appeared as if it wold allow me to execute commands on the local machine.  I tried a simple reverse shell but no joy.  Taking it down to a very basic level, I tried to ping but I needed to capture my ping requests on the other end.  

Read more: Catch ICMP (Ping) Requests

Shells on the target cannot be upgraded...

You get a shell on a linux box, you attempt to upgrade the shell to meterpreter using the command "sessions -u", and then you receive the following error:

"Shells on the target platform, linux, cannot be upgraded to meterpreter at this time."

Read more: Shells on the target cannot be upgraded...

PowerShell Download Script

I've spent a number of years bouncing back and forth between *nix machines and Windows machines.  But after the 90's, Windows really took hold and I've spent more hours on Windows than anything else and yet when I get a shell on a Windows machine, I feel like I have less control.  Scratch that, I HAVE less control but I can get what I want from outside of the box through PowerShell.

Read more: PowerShell Download Script

"sh: no job control in this shell"

I remember when I would get this error -- seemed like the kiss of death as far as trying to maneuver once I got a shell.  I'd flounder around, trying to figure out how to accomplish the task at hand but this issue would severely limit my ability.

Somewhere along the way, I discovered the cause -- you don't have a TTY.   What do you do?

Read more: "sh: no job control in this shell"