For some time now I've seen ICQ receive messages, from unknown people,
occassionally make the client core dump'. The messages are often
gibberish - more like the ASCII characters from someone trying to make
it execute something it shouldn't.
My interpretation of this is unknown parties are trying
Hello everyone,
I noticed last week that the Debian packaged version of cryptsetup has a
little limitation, which could be a security issue for people who have to
destroy their data forever.
It is impossible to destroy a keyslot when you used it to unlock the master
key.
I reported the bug to
Great history, excellent method.
Thanks!
-Mensaje original-
De: listbou...@securityfocus.com [mailto:listbou...@securityfocus.com]
En nombre de Adriel T. Desautels
Enviado el: Jueves, 12 de Febrero de 2009 13:24
Para: pen-test list
CC: Untitled
Asunto: Facebook from a hackers perspective
- Original Message -
From: Adriel T. Desautels
Sent: Thursday, February 12, 2009 6:23 AM
Subject: Facebook from a hackers perspective
Lets start off by talking about the internet and identity. The
internet is a shapeless world where identities are not only dynamic
but can't ever
That is awesome! I am going to add that to the blog post :)
On Feb 13, 2009, at 5:41 AM, Michael Painter wrote:
- Original Message -
From: Adriel T. Desautels
Sent: Thursday, February 12, 2009 6:23 AM
Subject: Facebook from a hackers perspective
Lets start off by talking about
On Fri, Feb 13, 2009 at 10:12 AM, bobby.mug...@hushmail.com wrote:
Your transgender technical attack was pioneered and perfected in
2008 by information security expert Eric Loki Hines - why are you
taking credit for a lesser version of his groundbreaking work, and
insisting on originality?
Sounds to me like you have a crush on Eric Loki Hines.
On Feb 13, 2009, at 10:12 AM, bobby.mug...@hushmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear ATD,
Because most of the targeted employees were male between the ages
of 20 and 40 we decided that it would be best
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attentive Dialtone,
Are you suggesting there is something wrong with my feelings for
her?
- -bm
On Fri, 13 Feb 2009 11:28:22 -0500 Adriel T. Desautels
ad_li...@netragard.com wrote:
Sounds to me like you have a crush on Eric Loki Hines.
On Feb
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi..
according to http://en.wikipedia.org/wiki/Unixtime unixtime will have
today the 'magic' number 1234567890
gratulations --- and who know where the party is? :)
/soylent
btw: sry 4 non-sec-posting... i know the list has enough to carry with
that just means it's the end of the world...
On Fri, Feb 13, 2009 at 12:25 PM, the.soylent the.soyl...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi..
according to http://en.wikipedia.org/wiki/Unixtime unixtime will have
today the 'magic' number 1234567890
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --
Debian Security Advisory DSA 1724-1secur...@debian.org
http://www.debian.org/security/ Steffen Joeris
February 13th, 2009
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;
}
FreeBSD (7.0-RELEASE) telnet daemon local privilege escalation -
And possible remote root code excution.
There is a rather big bug in the current FreeBSD telnetd daemon.
The environment is not properly sanitized when execution /bin/login,
what leads to a (possible) remote root hole.
The telnet
16 matches
Mail list logo
