On 2019-08-18 at 08:24 +0200, Mihai Moldovan wrote:
> So, to summarize, if I process a keyring file generated by gpg 2.2
> with a 1.4 binary, i.e., read-in the former, export all keys and
> import it again, gpg 1.4 generates exactly the same file as it would
> when importing the keys directly.
* Andre Klärner:
> is there a way to properly shared the entire keyring and trust
> settings between two machines?
What "properly" means is quite subjective.
My own .gnupg directories are under Git control. Imagine two computers,
let's call them alpha and bravo, in my local network, which both
raf via Gnupg-users wrote:
> Stefan Claas via Gnupg-users wrote:
>
> > Hi all,
> >
> > some of you may remember the add-photo thread we had a while ago
> > and I wondered why the max image size for a UAT packet is 16 MB.
> >
> > Recently I saw a Twitter post explaining that a .jpeg image
Hi all,
On Thu 05.09.2019 09:16:54, Erich Eckner via Gnupg-users wrote:
> On Thu, 5 Sep 2019, john doe wrote:
>
> > On 9/4/2019 10:41 PM, Andre Klärner wrote:
> >> Hi all,
> >>
> >> is there a way to properly shared the entire keyring and trust settings
> >> between two machines?
>
> [ snip ]
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 5 Sep 2019, john doe wrote:
On 9/4/2019 10:41 PM, Andre Klärner wrote:
Hi all,
is there a way to properly shared the entire keyring and trust settings
between two machines?
[ snip ]
The obvious solution would be to use mutt on your
On 2019-09-05 01:16, Stefan Claas via Gnupg-users wrote:
> Stefan Claas via Gnupg-users wrote:
>
>> Recently I saw a Twitter post explaining that a .jpeg image header
>> can contain 16 MB of data. I do not have the link currently handy,
>> sorry!
>
> I think I talked nonsense here about the 16
On 9/4/2019 10:41 PM, Andre Klärner wrote:
> Hi all,
>
> is there a way to properly shared the entire keyring and trust settings
> between two machines?
>
> My use case is the following:
>
> Mutt, my email client, runs on a containerized mailserver on another machine
> right under my desk.
>
> My
