On Wed, Jul 04, 2012 at 06:52:30PM +0200, Csanyi Pal wrote:
gpg: skipped Csanyi Pal csanyi...@gmail.com: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
Please include the command you actually typed.
(note also that if you are just starting to play around
Jon Dowland j...@debian.org writes:
On Wed, Jul 04, 2012 at 06:52:30PM +0200, Csanyi Pal wrote:
gpg: skipped Csanyi Pal csanyi...@gmail.com: secret key not
available
gpg: [stdin]: clearsign failed: secret key not available
Please include the command you actually typed.
You probably mean
Csanyi Pal csanyi...@gmail.com writes:
However, I have two keys, so maybe I should set up the primary key?
It doesn't matter, still get the messages:
signfile piklab_0.16.0-1.dsc
gpg: skipped Csanyi Pal csanyi...@gmail.com: secret key is not
available
gpg: [stdin]: clearsign failed: secret
Pal csanyi...@gmail.com: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
(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
package, I have success in
this but failed to sign .dsc and .changes files.
The output of dpkg-buildpackage at the and of the process is:
gpg: skipped Csanyi Pal csanyi...@gmail.com: secret key not available
gpg: [stdin]: clearsign failed: secret key not available
dpkg-genchanges ../piklab_0.16.0
On Tue, Jul 03, 2012 at 04:51:09PM +0200, Csanyi Pal wrote:
Hi,
I did run the
gpg --gen-key
command and I have the secret key:
gpg -K
/home/csanyipal/.gnupg/secring.gpg
--
sec 2048D/CD3E2F9A 2012-07-01
[snip]
I exported this key in both
6 matches
Mail list logo
