Hello,
On 09/20/2015 05:07 AM, Miguel Barbosa Gonçalves wrote:
> Sometimes, after doing an operation, the smartcard reader apparently
> disconnects and I can only get it to work if I disconnect and
> reconnect it.
How do you conclude that "smartcard reader apparently disconnects"?
Did you see any
I've attended all manner of conferences/meetings from big to small,
invite-only to open doors, expensive to free, heavily organized to improvised.
I think far and away the most productive conferences for groups of 20+ people
are Unconference/Barcamp/"Gunner-style" conferences, which are totally o
So I have a 2.0 installation I'm trying to get up to 2.1, taking
advantage of the opportunity given by sticking my GPG key on a smartcard
and using it for SSH authentication.
Everything is going smoothly, the smartcard part is working fine, but
unfortunately the fixed path used for the GPG agent i
On 21 Sep 2015, n...@esperi.org.uk told this:
> The underying problem here is that Unix-domain sockets with a fixed name
> and shared filesystems are simply not compatible concepts, because
> AF_UNIX bind() always creates a new file so any given socket can only be
> used in one machine in a cluster
On 21 Sep 2015, n...@esperi.org.uk verbalised:
> We are now in serious trouble -- gpg-agent cannot do anything, and half
> the time it's wedged so hard only kill -9 will get rid of it.
A terrible, hacky workaround is to change *_SOCK_NAME in configure.ac to
place all the sockets in a new subdirec
On 21 Sep 2015, n...@esperi.org.uk stated:
> On 21 Sep 2015, n...@esperi.org.uk verbalised:
>
>> We are now in serious trouble -- gpg-agent cannot do anything, and half
>> the time it's wedged so hard only kill -9 will get rid of it.
>
> A terrible, hacky workaround is to change *_SOCK_NAME in con
On Mon, 21 Sep 2015 13:44, n...@esperi.org.uk said:
> catastrophically bad effects on agent forwarding when used in
> conjunction with an NFS-mounted $HOME.
I know that it is not yet well documented, but thre is a solution for
remote file systems which do not allow for special files.
You create
Hi
just for reference, this is the original report:
https://bugs.gnupg.org/gnupg/issue1752
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.g
On 21 Sep 2015, Werner Koch spake thusly:
> On Mon, 21 Sep 2015 13:44, n...@esperi.org.uk said:
>
>> catastrophically bad effects on agent forwarding when used in
>> conjunction with an NFS-mounted $HOME.
>
> I know that it is not yet well documented, but thre is a solution for
> remote file syste
Hi,
root@host:~# gpg --list-keys
gpg: /home/root/.gnupg/trustdb.gpg: trustdb created
root@host:~# rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} -->
%{summary}\n'
package gpg-pubkey is not installed
I dont have the keys installed on my host. Why rpm command is saying
root@host:~# rpm -K
Il 21/09/2015 15:06, Werner Koch ha scritto:
> You create a plain file ~/.gnupg/S.gpg-agent with this content:
Why isn't the hostname included in file name? This way shared
filesystems would have no problems..
BYtE,
Diego
___
Gnupg-users mailing list
11 matches
Mail list logo
