Android gpg-agent crashes in libgcrypt when signing, decrypting, importing secret keys
Hans-Christoph Steiner
hans at guardianproject.info
Thu Jan 30 03:59:39 CET 2014
On 01/29/2014 07:36 PM, Hans-Christoph Steiner wrote:
>
>
> On 01/29/2014 06:14 PM, Werner Koch wrote:
>> On Wed, 29 Jan 2014 23:59, hans at guardianproject.info said:
>>
>>> That was very helpful! Now all the tests so far pass on the emulator. The
>>> problem is that is has gotten stuck on libgcrypt/tests/random for over an
>>> hour. Its stuck here:
>>
>> Collecting entropy is a major problem on embedded devices. For some
>> weeks now there is a discussion about this going on at coderpunks
>> (ie. cryptography at metzdowd.com)
>>
>>> random: checking whether RNG type switching works
>>
>> You may want to run the random test manually:
>>
>> ./random --verbose --progress
>
> Adding --progress. I canceled the test after it was running for 4 hours. I
> know that entropy is bad on mobile devices, but this is an emulator/VM. And
> yes, its bad there, but really 4 hours bad?
Good news! Now that --disable-neon-support works, the Android build is
passing all of the tests except for libgcrypt/random, which hangs on that
prefer-fips-rng test, and libassuan/fdpassing, which I am not sure is needed
on Android. Also, the gnupg/tests are not run because they require a UNIX
shell environment which Android does not have (things like /usr/bin/test,
/usr/bin/[, etc)
.hc
--
PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81
More information about the Gnupg-devel
mailing list