On 02/22/2018 11:13 PM, Kristian Fiskerstrand wrote:
> On 02/22/2018 11:03 PM, Henry wrote:
>> 2018-02-21 20:56 GMT+09:00 Kristian Fiskerstrand
>> :
>>> On 02/21/2018 11:53 AM, Peter Lebbing wrote:
>>> Touché :) Indeed, didn't notice it was an old file/signature , then
>>> gnupg 1.4 is the recommen
On 02/22/2018 11:03 PM, Henry wrote:
> 2018-02-21 20:56 GMT+09:00 Kristian Fiskerstrand
> :
>> On 02/21/2018 11:53 AM, Peter Lebbing wrote:
>> Touché :) Indeed, didn't notice it was an old file/signature , then
>> gnupg 1.4 is the recommended official suggestion presuming established
>> validity of
2018-02-21 20:56 GMT+09:00 Kristian Fiskerstrand
:
> On 02/21/2018 11:53 AM, Peter Lebbing wrote:
> Touché :) Indeed, didn't notice it was an old file/signature , then
> gnupg 1.4 is the recommended official suggestion presuming established
> validity of key material etc etc.
gpg (GnuPG) 1.4.22 do
Hi Peter,
thank for your attention to this smallest problem of mine which I
wouldn't even hope to have your attention for to begin with)
my bad, I should have started a new thread, well noted
on the other hand that's probably why I suddenly had all the big gnupg
minds helping me)
what a rewardi
On 22/02/18 21:17, Peter Lebbing wrote:
> The only way in which this might work is if I misinterpreted "not
> co-installable", and 2.0 in /usr and 2.1+ in /usr/local is not actually
> an instance of "co-installation". But I don't think that's the case. It
> might also work by pure chance and break
On 22/02/18 18:10, Dmitry Gudkov wrote:
> problem solved by configuring Enigmail to use the new gnupg location in
> /usr/local/bin/gpg (in the "Preferences" dialog, "Basic" tab, override
> the default setting /usr/bin/gpg2)
While my mind was idly mulling this over, I suddenly wondered if what
you
Hello!
We are is pleased to announce the availability of a new GnuPG release:
version 2.2.5. This is a maintenance release; see below for a list of
fixed bugs.
About GnuPG
===
The GNU Privacy Guard (GnuPG) is a complete and free implementation
of the OpenPGP standard which is commonly
dear all,
thank you for your time and help
problem solved by configuring Enigmail to use the new gnupg location in
/usr/local/bin/gpg (in the "Preferences" dialog, "Basic" tab, override
the default setting /usr/bin/gpg2)
Dmitry
On 22.02.2018 19:14, Damien Goutte-Gattat wrote:
> Hi,
>
> On 02/2
Hi,
On 02/22/2018 02:21 PM, Dmitry Gudkov wrote:
sudo make -f build-aux/speedo.mk INSTALL_PREFIX=/usr/local
[...]
*and all works fine in terminal*
however after installing Enigmail I get this error
You installed GnuPG 2.2.4 in /usr/local, but you still have an older
version in /usr.
Everyt
On 22/02/18 15:21, Dmitry Gudkov wrote:
> sudo make -f build-aux/speedo.mk INSTALL_PREFIX=/usr/local
That would mean that GnuPG is in /usr/local/bin/gpg
Yet:
On 22/02/18 11:04, Dmitry Gudkov wrote:
> Error - key extraction command failed
> /usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --
On Wed, Feb 21, 2018 at 10:22 PM, Ben McGinnes wrote:
>> And when you're on those certified, curated systems, you have
>> access to tools like
>> https://www.open-scap.org/resources/documentation/make-a-rhel7-server-compliant-with-pci-dss/
>> to help make sure you're in compliance, I think.
>
> op
Hi Werner,
yes, i am.
*I just manually compiled it on the fresh install of ubuntu 16.04 per
the below script:*
cd ~/Downloads
version=gnupg-2.2.4
wget https://gnupg.org/ftp/gcrypt/gnupg/$version.tar.bz2
wget https://gnupg.org/ftp/gcrypt/gnupg/$version.tar.bz2.sig
tar xf $version.tar.bz2
cd $vers
On 22/02/18 15:18, helices wrote:
> Let's cut through these ill-informed suppositions once and for all
You are rapidly squandering good will here. Your hostile tone will not
motivate anyone to help you any further. You are asking people to spend
their spare time on your issues, you should not derid
Let's cut through these ill-informed suppositions once and for all: If host
compliance was our problem, I would not have posted here at all.
Also, nowhere in this thread have I stated any inability to compile myself.
Having been doing such for 40+ years, that is not our problem either.
Defending
Hi!
On Thu, 22 Feb 2018 11:04, bere...@hotmail.com said:
> gpg: skipped packet of type 12 in keybox
Are you sure this if gpg 2.2.4 ? The error looks more like this is a
gpg version < 2.1.20.
Type 12 are ring trust packets which are used internally by gpg. The
code which shows this error is
dear all,
when trying to use enigmail with latest gpg 2.2.4 I get the following error:
Error - key extraction command failed
/usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --use-agent
--batch --no-tty --status-fd 2 -a --export 0xFB417E72
gpg: skipped packet of type 12 in keybox
gpg: skippe
16 matches
Mail list logo
