Marius Schwarz writes:
Hi,
I sorry to tell you, that gpg-agents are inflating on numbers in Fedora
systems:
I miss the days when gpg needed a passphrase it simply prompted a message on
standard output, turned off tty echo, and just read the password that I
typed in.
But that was too simple, primitive, and bulletproof. I guess that things
can't be as simple any more, and the forward march of progress is
unstoppable.
The most simple interface I could get working these days is the curses
pinentry. And that was no easy task to set up. I had to do some serious
googling around, and sifting through the manual pages, to come up with the
right set of spells and magic woids and phrases (I'm channeling Bugs Bunny)
to make it happen.
it would be more effective, if you give any programm who needs it,
the
password directly, instead of having useless processes laying around ;)
Nah. That's too simple of a solution.
Any changes will likely need to originate upstream; I'll be surprised if
there'll be any Fedora-originated development on this topic.
Systemd opens gpg-agents even for mailserver daemons, which do not
need nor
know how to use them.
Oh, sure. I had a nagging feeling something was missing, here. systemd,
that's it.
No idea what caused this invasion lately, but bugreports about it,
get
ignored.
The drive to fix this needs to come upstream. But nobody pays attention any
more to the simpletons like us, who like to work in a terminal or, heavens
forbid, an ssh connection. Or (and I know how this can be shocking to hear)
run build scripts. Everyone expects to have pretty windows, menu, dialogs,
and animated gophers to join them on their quest to use gpg. Hence, the
agent.
Could someone please take a look and fix it, if it's bug.
I would be very happy if someday I can simply run gpg(2) and have it simply
prompt me for my password, by default, without me having to fiddle anything,
not gpg-agent.conf, not anything else. Alas, I've resigned to those simpler
days being just a fond memory.