Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
Am currently doing Return to libc attack as part of an assignment. I have analysed the code and I have replaced the return address to point to system() with /bin/sh as argument. I have the following pattern in the stack.
4 bytes - return address - address of system()
4 bytes - address of exit()
4 bytes - Address of /bin/sh.
When I execute the code in gdb my program spawns a shell, whereas when I execute without gdb my program goes for a gracefull exit and I dont get a shell prompt. Please help me out with this?
I notice that you are new to LQ and would like to suggest that you please review the LQ Rules, here.
Unfortunately, your question is a violation of two of them:
Do not expect LQ members to do your homework - you will learn much more by doing it yourself.
Posts containing information about cracking, piracy, warez, fraud or any topic that could be damaging to either LinuxQuestions.org or any third party will be immediately removed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.