linux-kernel - Re: possible BUG while doing gpg --gen-key

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <40f323d00708241057k6549f22fl6abf802f14c03e44@mail.gmail.com>
Date:	Fri, 24 Aug 2007 19:57:20 +0200
From:	"Benoit Boissinot" <bboissin@...il.com>
To:	"Udo van den Heuvel" <udovdh@...all.nl>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: possible BUG while doing gpg --gen-key

On 8/24/07, Udo van den Heuvel <udovdh@...all.nl> wrote:
> While doing gpg --gen-key I can reproduce quite well some sort of
> crash/bug/etc:
> # gpg --gen-key

[snip]

> We need to generate a lot of random bytes. It is a good idea to perform
> some other action (type on the keyboard, move the mouse, utilize the
> disks) during the prime generation; this gives the random number
> generator a better chance to gain enough entropy.
>
[snip]
> Segmentation fault
> (...)
> Call Trace:
>  [<c0103b75>] show_trace_log_lvl+0x1a/0x2f
>  [<c0103c27>] show_stack_log_lvl+0x9d/0xa5
>  [<c0103dfc>] show_registers+0x1cd/0x2e3
>  [<c0104010>] die+0xfe/0x200
>  [<c010fb77>] do_page_fault+0x43c/0x511
>  [<c030220a>] error_code+0x6a/0x70

iirg gpg-keygen uses a lot of cpu time during that phase, you probably
should verify your ram and cpu. This kind of problem is often due to
faulty hardware.

regards,

Benoit
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/