Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange behavior when getting a shell #39

Closed
offlinemark opened this issue Oct 15, 2014 · 0 comments
Closed

Strange behavior when getting a shell #39

offlinemark opened this issue Oct 15, 2014 · 0 comments

Comments

@offlinemark
Copy link

Hi, I've noticed something weird when I pop a shell using peda.

Starting program: /home/me/class/stack/ip "$(./newexp.py)"
�����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������H�H1��T$(H�/bin//shH�T$ H�|$ H�|$H�L$H�LH�t$H�TH�Ȱ;��
process 25780 is executing new program: /bin/dash
$ ls
[New process 25788]
process 25788 is executing new program: /bin/ls
Makefile    ip    myexp.py   payload.asm  peda-session-cat.txt  peda-session-ls.txt
exploit.py  ip.c  newexp.py  payload.bin  peda-session-ip.txt   peda-session-whoami.txt
[Inferior 2 (process 25788) exited normally]
$ Warning: not running or target is remote

[1]+  Stopped                 ~/gdb-7.7/gdb/gdb -data-directory ~/gdb-7.7/gdb/data-directory ip
me@server:~$

The shell is launched and when I execute command from it, after the command finishes, peda itself gets stopped. Regular gdb doesn't behave this way, it gives me a functional shell. Can I get some help with this? How can I make my shell functional (aside from porting my exploit to non peda env)?

@longld longld closed this as completed Mar 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants