Hello,
awesome, thank you, it's working now.
Required file gpg-agent.conf was missing ..
On 10/02/2018 10:56:11 AM, Albrecht Dreß wrote:
> Am 02.10.18 09:43 schrieb(en) Mario Mikočević:
> > It's not actual balsa hang but it very much feels like one
> > - ssh window where balsa is started gets fully working ascii dialogue, if
> > dealt with (passphrase or smlr) balsa window resumes working ..
> >
> > Something like ->
>
> Ah! That's the Pinentry curses dialogue… The calling chain is something like
>
> Balsa ⟶ GpgME library ⟶ gpg or gpgsm ⟶ GPG Agent ⟶ pinentry
>
> to get the passphrase for signing or decryption.
>
> > Every other 'popup' window works fine so this very much could be gpg config
> > problem, just that I don't know how to fix that .. yet.
>
> On the machine where balsa is running (i.e. the remote box), you must install
> (Debian/Ubuntu package names, ymmv) gpg-agent and pinentry-gnome3 or
> pinentry-gtk2 (or the Qt/kde flavour of pinentry). As they are X11
> applications (in contrast to the curses version), they get tunnelled through
> ssh like Balsa itself.
>
> Then, make sure (again on the remote machine), the file
> ~/.gnupg/gpg-agent.conf exists and contains something like (see man gpg-agent
> for more options)
>
> <snip>
> debug-level none
> default-cache-ttl 10800 # …or whatever you like, in seconds
> pinentry-program /usr/bin/pinentry-gtk-2 # …may be named differently on
> other distos
> allow-mark-trusted
> lc-ctype de_DE.UTF-8 # …German locale for me, choose the proper one
> lc-messages de_DE.UTF-8
> </snip>
>
> Note that the “use-agent” option in ~/.gnupg/gpg.conf is a no-op and gpg2 now
> /always/ uses the agent (gpgsm never worked without it).
--
Mario Mikocevic (Mozz)
mozgy at t dash com dot hr
It's never too late to have a good childhood!
The older you are, the better the toys!
My favourite FUBAR ...
_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list
