Re: GPG - secret key not available?
Jon Dowland <jmtd@debian.org> writes:
> On Wed, Jul 04, 2012 at 06:52:30PM +0200, Csanyi Pal wrote:
>> gpg: skipped "Csanyi Pal <csanyipal@gmail.com>": secret key not
>> available
>> gpg: [stdin]: clearsign failed: secret key not available
>
> Please include the command you actually typed.
You probably mean here what command I used to build the package:
tar -xvf piklab-0.16.0.tar.bz2
cd piklab-0.16.0/
dh_make -e csanyipal@gmail.com -c gpl2 --createorig
Type of package: single binary, indep binary, multiple binary,
library, kernel module, kernel patch?
[s/i/m/l/k/n] s
Done. Please edit the files in the debian/ subdirectory now. piklab
uses a configure script, so you probably don't have to edit the
Makefiles.
dpkg-buildpackage -rfakeroot
>> > (note also that if you are just starting to play around, it would
>> > be worth generating a much stronger key. Read
>> > http://keyring.debian.org/creating-key.html to find out how)
>>
>> I generated such a strong key.
>
> What is the key-id?
0x1A772747
>> Still I get the message as abowe:
>> secret key not available
>
> Please include the command you actually typed.
You probably mean here what command I used to get my GPG key:
I updated ~/.gnupg/gpg.conf with lines at the end:
personal-digest-preferences SHA256
cert-digest-algo SHA256
default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 \
AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
Then I did run the command:
gpg --gen-key
and created gpg key with keysize of 4096 bits.
After that I added subkey for encryption:
gpg --edit-key 0x1A772747
After that I send the new key to key server:
gpg --keyserver subkeys.pgp.net --send-key 1A772747
However, I have two keys, so maybe I should set up the primary key?
--
Regards from Pal
Reply to: