Christopher writes:
> Fedora ships with both gpg and gpg2. Most things seem to work fine
> out of the box with gpg2, but many apps call "gpg" instead of "gpg2".
Ahh, forgot about gpg…
> It looks like that's the case with the default value for fossil's
> pgp-command setting: "gpg --clearsign -o
On 11/15/2016 12:35 PM, Christopher wrote:
I had a similar issue with git. I had to set my gpg.program to gpg2 for
things to work correctly. Fedora ships with both gpg and gpg2. Most
things seem to work fine out of the box with gpg2, but many apps call
"gpg" instead of "gpg2". It looks like that
On Tue, Nov 15, 2016 at 1:14 PM Saša Janiška wrote:
> Hello,
>
> I’m running Fedora f25-beta and have problem that I’ve to repeatedly
> enter my gpg password whenever I e.g. commit with Fossil (DVCS).
>
> gpg-agent.contains the following:
>
> pinentry-program /usr/bin/pinentry-gtk
> #allow-emacs-
On Tue, 2016-11-15 at 19:13 +0100, Saša Janiška wrote:
> I’m running Fedora f25-beta and have problem that I’ve to repeatedly
> enter my gpg password whenever I e.g. commit with Fossil (DVCS).
F25 has not yet been released. Please post to the Fedora Test list.
poc
Thanks for your examples.
What now confuses me no end, is that KMail and GPG "works" as is.
What I've basically done is installing everything, first setting it up on
Thunderbird/Enigmail, and then configuring the pieces for KMail to find my keys
and so on.
All how-to's I've read mentions setti
El 2013-08-23 07:19, Juan Orti Alcaine escribió:
El 2013-08-22 20:18, Martin S escribió:
As I understand it the file gpg-agent-startup.sh should be placed in
/etc/kde/env and made executable for the gpg-agent to start att boot
time?
Agent is also enabled in the ~/.gnupg/gpg.conf
Running the f
El 2013-08-22 20:18, Martin S escribió:
As I understand it the file gpg-agent-startup.sh should be placed in
/etc/kde/env and made executable for the gpg-agent to start att boot
time?
Agent is also enabled in the ~/.gnupg/gpg.conf
Running the file manually it starts the agent, but after having
On Friday, August 23, 2013 01:00:35 AM Raman Gupta wrote:
> On 08/23/2013 12:50 AM, Martin S wrote:
> > I get this too, but one issue remains.
> > Does the value GPGKEYS take 2 keys? I tried seperating the with " " and
> > ","
> > and both fails. As well as having two lines, but it only reads the f
On 08/23/2013 12:50 AM, Martin S wrote:
> I get this too, but one issue remains.
> Does the value GPGKEYS take 2 keys? I tried seperating the with " " and ","
> and both fails. As well as having two lines, but it only reads the first.
According to README.Fedora, you can specify multiple keys, spa
On Thursday, August 22, 2013 11:58:29 PM Raman Gupta wrote:
> On 08/22/2013 11:48 PM, Martin S wrote:
> > On Thursday, August 22, 2013 05:16:57 PM Raman Gupta wrote:
> >> On 08/22/2013 04:18 PM, Martin S wrote:
> >>> As I understand it the file gpg-agent-startup.sh should be placed in
> >>> /etc/kd
On 08/22/2013 11:48 PM, Martin S wrote:
> On Thursday, August 22, 2013 05:16:57 PM Raman Gupta wrote:
>> On 08/22/2013 04:18 PM, Martin S wrote:
>>> As I understand it the file gpg-agent-startup.sh should be placed in
>>> /etc/kde/env and made executable for the gpg-agent to start att boot time?
>>
On Thursday, August 22, 2013 05:16:57 PM Raman Gupta wrote:
> On 08/22/2013 04:18 PM, Martin S wrote:
> > As I understand it the file gpg-agent-startup.sh should be placed in
> > /etc/kde/env and made executable for the gpg-agent to start att boot time?
> > Agent is also enabled in the ~/.gnupg/gpg
On Thursday, August 22, 2013 01:55:26 PM Joe Zeff wrote:
> On 08/22/2013 01:18 PM, Martin S wrote:
> > Where should that file be place to be run at startup?
>
> My guess (and it's only that) is that you should create
> gpg-agent.service and enable it. Either that, or invoke the script from
> /etc
On 08/22/2013 04:18 PM, Martin S wrote:
> As I understand it the file gpg-agent-startup.sh should be placed in
> /etc/kde/env and made executable for the gpg-agent to start att boot time?
> Agent is also enabled in the ~/.gnupg/gpg.conf
>
> Running the file manually it starts the agent, but after
On 08/22/2013 01:18 PM, Martin S wrote:
Where should that file be place to be run at startup?
My guess (and it's only that) is that you should create
gpg-agent.service and enable it. Either that, or invoke the script from
/etc/rc.local, after making sure that rc.local.service is enabled. Of
On 03/31/2010 08:26 AM, Mail Lists wrote:
> On 03/30/2010 06:23 AM, Ed Greshko wrote:
>
>> This is F11, KDE.
>>
>> Seems gpg-agent is hosed for one user. I think it may have to do with
>> the cache for the private key.
>>
> ...
>
>
>> I get the feeling there is a corrupt file...or stuc
On 03/30/2010 06:23 PM, Ed Greshko wrote:
> This is F11, KDE.
>
> Seems gpg-agent is hosed for one user. I think it may have to do with
> the cache for the private key.
>
> I get the following
>
> egres...@meimei .gnupg]$ /usr/bin/gpg --charset utf8 --batch --no-tty
> --status-fd 2 -t --clear
On 03/30/2010 06:23 AM, Ed Greshko wrote:
> This is F11, KDE.
>
> Seems gpg-agent is hosed for one user. I think it may have to do with
> the cache for the private key.
...
> I get the feeling there is a corrupt file...or stuck filefrom what I
> can tell gpg-agent interfaces with pinentry
18 matches
Mail list logo
