Re: [paperkey] Always output "interrupt"

2018-06-20 Thread Damien Cassou
David Shaw  writes:
> On Jun 20, 2018, at 11:28 AM, Damien Cassou  wrote:
>> $ gpg2 --export-secret-key "FooBar" | paperkey -
>
> What happens if you do this:
>
> $ gpg2 --export-secret-key "FooBar" > /tmp/foo.key
> $ paperkey < /tmp/foo.key

You are right, paperkey works fine. The problem comes from EShell's
(Emacs shell-like command interpreter) implementation of pipe
apparently.

Sorry for the noise.

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

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


Re: git repo won't build for lack of source files?

2018-06-20 Thread Mike Inman
Sorry, forgot a critical trick or maybe 2, should have just pasted the
script in the first place:

#!/bin/bash
#
# https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=README

set -e

export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH

pushd npth
./autogen.sh --force
./configure --enable-maintainer-mode
make -j
make check
sudo make install
popd

pushd libgpg-error
./autogen.sh --force
./configure --enable-maintainer-mode
make -j
make check
sudo make install
popd

pushd libgcrypt
./autogen.sh --force
./configure --enable-maintainer-mode
make -j
make check
sudo make install
popd

pushd libksba
./autogen.sh --force
./configure --enable-maintainer-mode
make -j
make check
sudo make install
popd

pushd libassuan
./autogen.sh --force
./configure --enable-maintainer-mode
make -j
make check
sudo make install
popd

pushd gnupg
./autogen.sh --force
./configure --enable-maintainer-mode --enable-all-tests --enable-gpg-is-gpg2
make -j
make check
sudo make install
popd

pushd gpgme
./autogen.sh --force
./configure --enable-maintainer-mode
make -j
make check
sudo make install
popd
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: git repo won't build for lack of source files?

2018-06-20 Thread Mike Inman
Are you also building the required support libraries?

I have recently build 2.2.8 successfully using this set of support libs:

git checkout npth-1.5
git checkout libgpg-error-1.31
git checkout libgcrypt-1.8.2
git checkout libksba-1.3.5
git checkout libassuan-2.5.1
git checkout gnupg-2.2.8

then run the following commands in each of the lib folders (in the order
shown above):

./autogen.sh --force
./configure --enable-maintainer-mode
make -j
make check
sudo make install

make check is optional, but if you want to be extra sure, you can also add
a  --enable-all-tests to the configure of gnupg (but not the others...)  It
doesn't take too long to build and check them all.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: [paperkey] Always output "interrupt"

2018-06-20 Thread David Shaw
On Jun 20, 2018, at 11:28 AM, Damien Cassou  wrote:
> 
> David Shaw  writes:
>> Which version of paperkey is this?
> 
> both the version from source and from Fedora package are 1.5.
> 
>> If that doesn't resolve your problem, can you send me a sample secret
>> key (not your real secret key, of course - just generate a dummy one)
>> that exhibits the problem?  I'll make it work.
> 
> Please find attached the very secret key :-).

I tested this on my regular development box and it worked fine.  Just for 
completeness, I spun up a Fedora 28 VM and it worked fine there as well.  It 
occurs to me that given the pipeline you were using, the "interrupt" error may 
have come from gpg2 rather than paperkey:

> $ gpg2 --export-secret-key "FooBar" | paperkey -

What happens if you do this:

$ gpg2 --export-secret-key "FooBar" > /tmp/foo.key
$ paperkey < /tmp/foo.key

David


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


Re: Won't recognize my secret key

2018-06-20 Thread Phillip Susi
On 6/19/2018 3:05 PM, Phillip Susi wrote:
> gpg keeps telling me that I have no secret key.  Even after I deleted
> the .gnupg directory and copied the pubring and secring from another
> computer where it works, this system keeps saying I have no secret keys.
>  Why does it keep throwing out my secret keys?

I have built gnupg-2.0.31 from source and found it to work.  gnupg-2.2.4
refuses to import my private keys ( but will import a newly created test
key ).  So something broke somewhere between 2.0 and 2.2, but apparently
2.1 was a development branch, and it likes to yell at you that you
shouldn't be using production keys and refuses to import any private
keys, so I can't test to see where it lost the ability to import *my*
private key.

Is there a way to turn off this damn protection so I can continue to bisect?




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


Re: git repo won't build for lack of source files?

2018-06-20 Thread Phillip Susi
On 6/20/2018 1:52 PM, Phillip Susi wrote:
> I cloned the git repo and checked out gnupg-2.2.4, ran ./autogen.sh,
> ./configure, then when I try to make, it is apparently missing some files:
> 
> make[2]: Entering directory '/home/psusi/gnupg/common'
> make[2]: *** No rule to make target 'audit-events.h', needed by 'all'.
> Stop.
> 
> 
> What gives?

Apparently you have to configure with --enable-maintainer-mode to avoid
this.




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


git repo won't build for lack of source files?

2018-06-20 Thread Phillip Susi
I cloned the git repo and checked out gnupg-2.2.4, ran ./autogen.sh,
./configure, then when I try to make, it is apparently missing some files:

make[2]: Entering directory '/home/psusi/gnupg/common'
make[2]: *** No rule to make target 'audit-events.h', needed by 'all'.
Stop.


What gives?



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


Re: [paperkey] Always output "interrupt"

2018-06-20 Thread Damien Cassou
David Shaw  writes:
> Which version of paperkey is this?

both the version from source and from Fedora package are 1.5.

> If that doesn't resolve your problem, can you send me a sample secret
> key (not your real secret key, of course - just generate a dummy one)
> that exhibits the problem?  I'll make it work.

Please find attached the very secret key :-).

I got it using:

$ gpg2 --export-secret-key "FooBar" > /tmp/foo.key

if you need it, the passphrase is "iletaitunpetithomme1".

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill


foo.key
Description: Binary data
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: [paperkey] Always output "interrupt"

2018-06-20 Thread David Shaw
On Jun 20, 2018, at 5:14 AM, Damien Cassou  wrote:
> 
> Hi,
> 
> The output of paperkey is just "interrupt" instead of being a printable
> output. I've tried to use paperkey on 2 different main private keys and
> failed twice. I tried with both the Fedora package and from paperkey's
> source. Same result in every case.
> 
> System:
> - Fedora 28
> - gpg (GnuPG) 2.2.8, libgcrypt 1.8.3
> 
> Keys:
> - key1: ed25519
> - key2: rsa4096
> 
> Command:
> $ gpg2 --export-secret-key "FooBar" | paperkey -
> interrupt
> $

Hi Damien,

Which version of paperkey is this?  The latest is 1.5 (and support for EdDSA 
keys was only added in that version), so if you're using an old version can you 
try the latest?

If that doesn't resolve your problem, can you send me a sample secret key (not 
your real secret key, of course - just generate a dummy one) that exhibits the 
problem?  I'll make it work.

David


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


[paperkey] Always output "interrupt"

2018-06-20 Thread Damien Cassou
Hi,

The output of paperkey is just "interrupt" instead of being a printable
output. I've tried to use paperkey on 2 different main private keys and
failed twice. I tried with both the Fedora package and from paperkey's
source. Same result in every case.

System:
- Fedora 28
- gpg (GnuPG) 2.2.8, libgcrypt 1.8.3

Keys:
- key1: ed25519
- key2: rsa4096

Command:
$ gpg2 --export-secret-key "FooBar" | paperkey -
interrupt
$

Best

-- 
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

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