QCA2

Ron Murray rjmx at rjmx.net
Sun Sep 11 05:18:01 BST 2022


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Oops.

   I said:

"because it forces "--pinentry-mode loopback", which suppresses that."

   I should have said

"because it forces "--no-tty", which suppresses that."

Sorry about that.

 .....Ron

- -- 
Ron Murray <rjmx at rjmx.net>
PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761


On Sat, 2022-09-10 at 22:44 -0400, Ron Murray wrote:
> Hi Albert.
> 
>    OK. I see that it works for a command-line program (I didn't know
> about qcatool, to be honest). Perhaps I didn't make it clear, but my
> project is a GUI program, using Qt5. Currently, QCA invokes the gpg
> executable (although I gather there are plans to switch to GPGME),
> and there are, as far as I know, only three ways to feed gpg with a
> passphrase when it needs one:
> 
> - Have gpg request it directly on the console, as you describe,
> 
> - Directly, on the command line (not a good idea), and
> 
> - Via gpg-agent.
> 
>    gpg, when invoked manually, opens up a pinentry dialog, which
> collects the passphrase and feeds it to gpg-agent. QCA doesn't seem
> to contain the necessary assuan code to do that. Furthermore, it
> can't request for it on the console because it forces "--pinentry-
> mode loopback", which suppresses that. Besides, you don't want to use
> the console for anything when you're running a GUI program.
> 
>    Since QCA invokes the gpg executable anyway, it makes more sense
> to just let gpg bring up a pinentry dialog.
> 
>    I've attached the patch that fixes the library to do just that. I
> don't think it adds much more than 10-12 lines to the code.
> 
> Thanks,
> 
>  .....Ron
> 
> 
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETZlw4yMXM0sUHntjEvfoZbXi52EFAmMdYXkACgkQEvfoZbXi
52G3pQ//YrUazYg8t50Us/es/XZ6GqzGtIllVE7Z7+MxHL4s3VfQuJAhhMPw0elC
2bvldmeNbNL37lLMgRjNn/8WEiJtuhKCIPUuoYqn5wWXWk8jrNLGaPoucqqd3CPg
osTe/lmQ2I6HmbFOM22kZBRHJkk0I8DY05CN+8pAaLc2wRiyEQOHyFKUEHRMKb7z
PodWoeqEg3Qmn3H+TlezGeXlbtkKc6t1Qi0tXPWrtPoQSWGxLTNhm0T+qIeR5xD2
qy4Fi7c5QLpRKTsH8iDGEkhFlZY6tC4ah5GMCrbTZ2BwHJXgK4FnyZ7kyedW3YRT
huoLFDWgFm9v41TTFX8L1PoeG8LieqlKRIfZPV+16unHwuGLJMAcb9uSjE+SBQi1
Gc501WsAPAlScmNaz+qeZyhelmsDC4RJU6+K25gbYHvQGhckUtXzLJLxx2rIJfHx
CTujjJDkObzQDFRtttEh5c61EcPoxq4n0yjSfDCCx9ECS0rBnuMx+NZw9Kb5HYwM
d38vnO+yXlZGnEZ8ePHznF4oNNzJ2qUuACDPKfJxYdReAiZMfXtcUsIzJ/XDu3pm
wQqAHuPW6hXFCJ9VyMrnkNlZoru67y+CKv3r6s2zeFKHkwl2ynzxg/tR8yDHyMRg
88B0B/t8xGCLvuJo5QOhM7aiDg0VTw/p+gdfoBMJNzIg3MlfzaE=
=Cwwg
-----END PGP SIGNATURE-----


More information about the kde-core-devel mailing list