On Tue, 17 Feb 2009 12:19:07 +1100, Jubei Trippataka said:
memset(buf, 'A', 528);
That's where the original poster is starting from...
You commenting on exploitation is kind of like asking a deaf person what
their favorite song is. You obviously have no clue what you are talking
about due
On Mon, Feb 16, 2009 at 09:00:33AM -0500, ArcSighter Elite wrote:
James Matthews wrote:
I would recommend doing the following things.
1. Ask on the Ubuntu GCC list what protection is implemented. (Or just look
at the source)
2. Use GCC to see where the execution is being redirected and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Matthews wrote:
I would recommend doing the following things.
1. Ask on the Ubuntu GCC list what protection is implemented. (Or just look
at the source)
2. Use GCC to see where the execution is being redirected and so you can
have a
memset(buf, 'A', 528);
Don't do that. This sort of whoops is exactly what the gcc SSP canary is
designed to stop.
I could comment on this, but... I'll leave it.
I have googled my brains out for a solution, but all I have gathered is
that
my Ubuntu's gcc is compiled with SSP and
I would recommend doing the following things.
1. Ask on the Ubuntu GCC list what protection is implemented. (Or just look
at the source)
2. Use GCC to see where the execution is being redirected and so you can
have a better visual of whats going on.
3. Are you sure the stack is executable?
On
I came across a problem that I am sure many security researchers have seen
before:
ja...@uboo:~$ cat bof.c
#include stdio.h
#include string.h
int main()
{
char buf[512];
memset(buf, 'A', 528);
return 0;
}
ja...@uboo:~$
ja...@uboo:~$ ./bof
*** stack smashing detected ***: ./bof terminated
On Fri, 13 Feb 2009 11:50:11 EST, Jason Starks said:
memset(buf, 'A', 528);
Don't do that. This sort of whoops is exactly what the gcc SSP canary is
designed to stop.
I have googled my brains out for a solution, but all I have gathered is that
my Ubuntu's gcc is compiled with SSP and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
valdis.kletni...@vt.edu wrote:
On Fri, 13 Feb 2009 11:50:11 EST, Jason Starks said:
memset(buf, 'A', 528);
Don't do that. This sort of whoops is exactly what the gcc SSP canary is
designed to stop.
I have googled my brains out for a
On Fri, Feb 13, 2009 at 11:50:11AM -0500, Jason Starks wrote:
I came across a problem that I am sure many security researchers have seen
before:
ja...@uboo:~$ cat bof.c
#include stdio.h
#include string.h
int main()
{
char buf[512];
memset(buf, 'A', 528);
return 0;
}
