On 17.04.2018 22:50, Kristian Fiskerstrand wrote:
> On 04/17/2018 10:48 PM, Paul H. Hentze wrote:
>>
>>
>> On 17.04.2018 17:48, Daniel Kahn Gillmor wrote:
>>> On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote:
On 04/17/2018 10:52 AM, Paul H. Hentze wrote:
> Actually those com
On 04/17/2018 10:48 PM, Paul H. Hentze wrote:
>
>
> On 17.04.2018 17:48, Daniel Kahn Gillmor wrote:
>> On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote:
>>> On 04/17/2018 10:52 AM, Paul H. Hentze wrote:
Actually those commands
> find ~/.gnupg -type d -exec chown 0700 '{}
On 17.04.2018 17:48, Daniel Kahn Gillmor wrote:
> On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote:
>> On 04/17/2018 10:52 AM, Paul H. Hentze wrote:
>>> Actually those commands
find ~/.gnupg -type d -exec chown 0700 '{}' ';'
find ~/.gnupg -type f -exec chown 0600 '{
On 17.04.2018 17:48, Daniel Kahn Gillmor wrote:
> On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote:
>> On 04/17/2018 10:52 AM, Paul H. Hentze wrote:
>>> Actually those commands
find ~/.gnupg -type d -exec chown 0700 '{}' ';'
find ~/.gnupg -type f -exec chown 0600 '{}
On 04/16/2018 02:14 PM, Werner Koch wrote:
>> Could gnupg 2.2.7 detect if gpgme is installed at all and if it is,
>> make sure it's at least version 1.10.1 / 1.11.0?
> :-) - No.
Speaking for Gentoo we can do this on distribution level by adding a
blocker on the lower version if needed.
--
--
On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote:
> On 04/17/2018 10:52 AM, Paul H. Hentze wrote:
>> Actually those commands
>>> find ~/.gnupg -type d -exec chown 0700 '{}' ';'
>>> find ~/.gnupg -type f -exec chown 0600 '{}' ';'
>> didn't work.
>> The terminal responded: "chown
Hi Andre,
Great, the commit works well. And as far as I see the source code, SELFCHECK=0
seems better for my case this time. I would use it as a workaround.
I look forward to new version release fixing this issue.
Thanks,
Yuki
2018-04-17 21:19 GMT+09:00 Andre Heinecke :
> Hi,
>
> thanks for try
Hi,
thanks for trying out up to date GnuPG :-)
On Tuesday, April 17, 2018 5:55:26 PM CEST Yuki Ito wrote:
> The build script verifies GnuPG version based on gnupg21_ver in swdb.lst:
> https://dev.gnupg.org/source/gnupg/browse/master/build-aux/getswdb.sh;
> 6fbe2ddbaf5123ae444c95fdf8da67840f794c76
Hi,
I've tried speedo build on GnuPG 2.2.6, but I've got an error like this:
$ make -f build-aux/speedo.mk native
make -f /gnupg-2.2.6/build-aux/speedo.mk UPD_SWDB=1 TARGETOS=native
WHAT=release WITH_GUI=0 all
make[1]: Entering directory '/gnupg-2.2.6'
gpgv: Signature made Fri Apr 13 08:47:30 201
Hi,
I've tried speedo build on GnuPG 2.2.6, but I've got an error like this:
$ make -f build-aux/speedo.mk native
make -f /gnupg-2.2.6/build-aux/speedo.mk UPD_SWDB=1 TARGETOS=native
WHAT=release WITH_GUI=0 all
make[1]: Entering directory '/gnupg-2.2.6'
gpgv: Signature made Fri Apr 13 08:47:30 201
On 04/17/2018 10:52 AM, Paul H. Hentze wrote:
> Actually those commands
>> find ~/.gnupg -type d -exec chown 0700 '{}' ';'
>> find ~/.gnupg -type f -exec chown 0600 '{}' ';'
> didn't work.
> The terminal responded: "chown: The owner of data XXX is going to be
> changed. This is not allowed.
On 17.04.2018 00:49, Daniel Kahn Gillmor wrote:
> On Tue 2018-04-17 00:04:11 +0200, Paul H. Hentze wrote:
>>> gpg: WARNING: unsafe permissions on homedir '/home/giraffenhorde/.gnupg'
>>
>> So I fixed that with
>>
>>> chown -R "$USER:$(id -gn)" ~/.gnupg
>>> chmod 700 ~/.gnupg
>>> chmod 600 ~/.gnup
12 matches
Mail list logo
