Re: gnupg-2.2.4: how to deal with failed tests

2018-01-20 Thread MFPA 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



On Friday 19 January 2018 at 3:50:22 PM, in
, Shannon Mess
via Gnupg-users wrote:-


> REMOVE my email address from this thread!

You are subscribed to the mailing list or not subscribed to it. There
is no feature to be removed from an individual discussion thread.

In the event you wish to unsubscribe from the list, you can do this at
the bottom of the page linked below.
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Or by sending an email to  with the
single word "unsubscribe" (without quotes) as the message subject.


- --
Best regards

MFPA  

Confusion is always the most honest response
-BEGIN PGP SIGNATURE-

iNUEARYKAH0WIQSWDIYo1ZL/jN6LsL/g4t7h1sju+gUCWmNeVl8UgAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0OTYw
Qzg2MjhENTkyRkY4Q0RFOEJCMEJGRTBFMkRFRTFENkM4RUVGQQAKCRDg4t7h1sju
+g8jAPoC6PCVQoqrx1gRu594ArZhnzd76l+7LbOQTlhGcUjHJgD9FidVLnA2bKur
CES7AV/7RburSe5CU/sNl8eAHzIoawWJApMEAQEKAH0WIQRSX6konxd5jbM7JygT
DfUWES/A/wUCWmNeVl8UgAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0NTI1RkE5Mjg5RjE3Nzk4REIzM0IyNzI4MTMw
REY1MTYxMTJGQzBGRgAKCRATDfUWES/A/0nvD/94it3CD7AuoJXFwzt8pIAdqGkN
LiPQhXhrzodc3KMKB8m2WDVuGPA6yzYa7fMRdFIhnlADbm39jlFNYl3bHk+L1xnp
Lz5n+moj9tf7/+/Yn+K7SaBdRTtvk9QO0YZe3pfsfBOiLxgSXg5Ub5JNknF3gTMB
pa1OziTSN5TYelsNtVVrvOrYvXEqKs/GeRnexdJMUi42oGDxlbLZtLjDQ+KxbLbk
JiBTFdTrritRQ4QTOPqp4NGFGumLtu81tiJPRZFELKUTRfHPDMV8QblqTFXUwSU3
TjWBNmOfWkdPu9wY/dofH9aEcbMj0qbFAMppGyK83MwFo47zrdhGXbVhzjceZtPI
g/zGnGSvvIarU7GcK/GA/icZiRdXyR3jLpGmVg1BBka8KfHfIEWT6SB+8Y/AR3oc
/rmduYkUUfmJggDRzpFXsHgOY68j/f8GOIeBRl1yidg52tBuoXWLQbVn4L/bz/KF
yD9CQPDt7pcOo5AmutkxIT+qj3D4KDdQwWwiFwXdh/vUKxdlM/FZHO0XkoaIRPQn
SZLeAnfAUOVw4B20EfY1Cmnv1mxG4jqKegNEFgtaywP9ywYeXfYbYKtpircYReY6
h99vHlXt9M6YAAZoO+Xr4wB8h1M8UvA3ZEVdRgtXIWe/1MMAc9/i3vc209VjHQvA
bt7S/gLIPiGBpfadMQ==
=47as
-END PGP SIGNATURE-


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-19 Thread Shannon Mess via Gnupg-users 
 REMOVE my email address from this thread! 
On Friday, January 19, 2018, 8:27:25 AM EST, Henry  
wrote:  
 
 THANK YOU!! THANK YOU!!

Configured simply with:
% ./configure --enable-g13 --enable-symcryptrun --enable-wks-tools \
  --with-readline=/usr/local
and all tests run seemed to PASS.

(I will later be installing gnupg2 on darwin and ubuntu.)

Henry

2018-01-19 3:27 GMT+09:00 Werner Koch :
> On Thu, 18 Jan 2018 15:41, nbsd4e...@gmail.com said:
>
>>  --enable-selinux-support --with-libgpg-error-prefix=/usr/local \
>      ^^
>
> Ah!  There is a second case where you see the reported error message:
>
> #ifdef ENABLE_SELINUX_HACKS
>  if (1)
>    {
>      /* We don't allow importing secret keys because that may be used
>          to put a secret key into the keyring and the user might later
>          be tricked into signing stuff with that key.  */
>      log_error (_("importing secret keys not allowed\n"));
>      return 0;
>    }
> #endif
>
> I wonder why you enable this at all.  I doubt that NetBSD supports
> SElinux.
>
>
> Salam-Shalom,
>
>    Werner
>
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
  ___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-19 Thread Henry 
THANK YOU!! THANK YOU!!

Configured simply with:
% ./configure --enable-g13 --enable-symcryptrun --enable-wks-tools \
  --with-readline=/usr/local
and all tests run seemed to PASS.

(I will later be installing gnupg2 on darwin and ubuntu.)

Henry

2018-01-19 3:27 GMT+09:00 Werner Koch :
> On Thu, 18 Jan 2018 15:41, nbsd4e...@gmail.com said:
>
>>   --enable-selinux-support --with-libgpg-error-prefix=/usr/local \
>   ^^
>
> Ah!  There is a second case where you see the reported error message:
>
> #ifdef ENABLE_SELINUX_HACKS
>   if (1)
> {
>   /* We don't allow importing secret keys because that may be used
>  to put a secret key into the keyring and the user might later
>  be tricked into signing stuff with that key.  */
>   log_error (_("importing secret keys not allowed\n"));
>   return 0;
> }
> #endif
>
> I wonder why you enable this at all.  I doubt that NetBSD supports
> SElinux.
>
>
> Salam-Shalom,
>
>Werner
>
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-18 Thread Werner Koch 
On Thu, 18 Jan 2018 15:41, nbsd4e...@gmail.com said:

>   --enable-selinux-support --with-libgpg-error-prefix=/usr/local \
  ^^

Ah!  There is a second case where you see the reported error message:

#ifdef ENABLE_SELINUX_HACKS
  if (1)
{
  /* We don't allow importing secret keys because that may be used
 to put a secret key into the keyring and the user might later
 be tricked into signing stuff with that key.  */
  log_error (_("importing secret keys not allowed\n"));
  return 0;
}
#endif

I wonder why you enable this at all.  I doubt that NetBSD supports
SElinux.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpJi85oHvga6.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-18 Thread Henry 
2018-01-18 4:12 GMT+09:00 Werner Koch :
> On Wed, 17 Jan 2018 15:18, nbsd4e...@gmail.com said:
>
>> "gpg: importing secret keys not allowed"
>
> Which means you are trying to import from a keyserver, WKD, DANE etc.

I do not know; the tests are trying to do it, AFAIK.

> That is very strange.  How did you build gnupg, did you checked the
> signature of the source, is there anything special in your setup?

Source was checked with gnupg1, which in turn was only checked with
sha1 checksum.

% setenv LDFLAGS "-Wl,-R/usr/local/lib -L/usr/local/lib -L/usr/lib"
% ./configure --enable-g13 --enable-symcryptrun --enable-wks-tools \
  --enable-selinux-support --with-libgpg-error-prefix=/usr/local \
  --with-npth-prefix=/usr/local --with-libgcrypt-prefix=/usr/local \
  --with-libassuan-prefix=/usr/local --with-ksba-prefix==/usr/local \
  --with-readline=/usr/local
% gmake

(Reason for LDFLAGS is that get an error during tests like "can't find
shared object libgcrypt.so")

Thank you,
Henry
>
> Salam-Shalom,
>
>Werner
>
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-17 Thread Werner Koch 
On Wed, 17 Jan 2018 15:18, nbsd4e...@gmail.com said:

> "gpg: importing secret keys not allowed"

Which means you are trying to import from a keyserver, WKD, DANE etc.

That is very strange.  How did you build gnupg, did you checked the
signature of the source, is there anything special in your setup?


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpJmhwtylqvm.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-17 Thread Henry 
Thank you very much.  The log files seem to indicate there is some problem
involving import of "secret keys".  Still, I have no idea how to solve
this problem.
Excerpts from those files below.  -- Henry

issue2346.scm.log, ssh-export.scm.log,and ecc.scm.log all have in common
the following:
"gpg: importing secret keys not allowed"

export.scm.log has as the last line:
"gpg --no-permission-warning --always-trust --output - --export-secret-keys D74C
5F22 -"

armor.scm.log has:
"Importing alpha_seckey
(((/usr/local/src/gnupg-2.2.4/g10/gpg --no-permission-warning --always-trust --o
utput - --import -) 4408 2))"

2018-01-17 18:15 GMT+09:00 Werner Koch :
> On Wed, 17 Jan 2018 07:50, nbsd4e...@gmail.com said:
>
>> tests/openpgp/armor.scm
>
> There will be a file
>
>   tests/openpgp/armor.scm.log
>
> which should give you some more insight.  You can alos run single tests
> or all in a more verbose mode.  See the ERADME file in the tests directory.
>
>> Grateful for any advice on how to configure/build gnupg2 so that
>
> Our Jenkins is currentluy not running but we used to run tests also on
> OpenBSD without failures.  I also test from time on FreeBSD.  Thus I am
> sure it will be only a minor problem on your installation.
>
>
> Salam-Shalom,
>
>Werner
>
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-17 Thread Kristian Fiskerstrand 
On 01/17/2018 07:50 AM, Henry wrote:
> I finally got gnugp2 built without any fatal errors.
> Most of the tests passed, but the following tests failed:
> tests/openpgp/issue2346.scm
> tests/openpgp/ssh-export.scm
> tests/openpgp/export.scm
> tests/openpgp/ecc.scm
> tests/openpgp/armor.scm
> 
> I am not hip on using a binary that fails its tests.
> Grateful for any advice on how to configure/build gnupg2 so that
> it passes all its tests.
> 

Some observations on test
* in Gentoo we've had to shorten the socket path length, max is 108
chars of which 42 is used by gpgscm by default.
* Parallel tests fail if building without tofu support
* sparc architecture has a failure in
tests/openpgp/quick-key-manipulation.scm:219 on assert

-- 

Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk

Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3

Qui audet vincit
Who dares wins



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: gnupg-2.2.4: how to deal with failed tests

2018-01-17 Thread Werner Koch 
On Wed, 17 Jan 2018 07:50, nbsd4e...@gmail.com said:

> tests/openpgp/armor.scm

There will be a file 

  tests/openpgp/armor.scm.log

which should give you some more insight.  You can alos run single tests
or all in a more verbose mode.  See the ERADME file in the tests directory.

> Grateful for any advice on how to configure/build gnupg2 so that

Our Jenkins is currentluy not running but we used to run tests also on
OpenBSD without failures.  I also test from time on FreeBSD.  Thus I am
sure it will be only a minor problem on your installation.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgprVQZLOoia2.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

gnupg-2.2.4: how to deal with failed tests

2018-01-16 Thread Henry 
I finally got gnugp2 built without any fatal errors.
Most of the tests passed, but the following tests failed:
tests/openpgp/issue2346.scm
tests/openpgp/ssh-export.scm
tests/openpgp/export.scm
tests/openpgp/ecc.scm
tests/openpgp/armor.scm

I am not hip on using a binary that fails its tests.
Grateful for any advice on how to configure/build gnupg2 so that
it passes all its tests.

TIA

Henry

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users