Comment 6 for bug 336910

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Belchenko wrote:
> John A Meinel пишет:
>> Just adding a 'me-to' to this, as it prevents me from using "bzr
>> qcommit" for my day-to-day work.
>
> I'm sorry, but this is clearly problem in bzrlib in first place.
>
>> Oddly enough, I see the warning:
>> gpg: WARNING: using insecure memory!
>> gpg: please see http://www.gnupg.org/faq.html for more information
>>
>> show up in both the console that I spawned 'bzr qcommit' from and in the
>> Status window of qcommit.
>
> Maybe this is side-effect of running commit as subprocess?
>
>> So it at least looks like gpg can somewhat connect to the raw terminal,
>> it just doesn't prompt me for a password there.
>>
>> Note that it wouldn't be a full solution once you are using something
>> like Bazaar Explorer that doesn't want to have a console window shown.
>
> Yes, so I guess proper solution to prompt for password via GUI is
> required. Can we use gpgme library and avoid gpg binary?
>
> Another question: John, why you don't use gpg-agent?
>

There isn't really a gpg-agent on Windows...

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqw5FcACgkQJdeBCYSNAAOJuQCeL44iUDNJvi0KnbsWJKN7lLHA
T3AAoLyDKZfdG6lDuAkhjg7tJnsIxDji
=UArK
-----END PGP SIGNATURE-----