On Samstag, 9. November 2019 01:42:47 CET Bobby Richardson (bobbyric) wrote:
> Hello:
>
> I need a help in my gpg decryption with crontab.
> Recently my gpg decryption with crontab started failing.
What did you change recently?
> If I do gpg decryption without crontab, it works fine.
cron provi
Hello:
I need a help in my gpg decryption with crontab.
Recently my gpg decryption with crontab started failing.
If I do gpg decryption without crontab, it works fine.
Here is my background information:
Platform: Centos 7
gpg version: 2.0.22
# When I use crontab with my decryption script in perl
ses error :
>
> gpg --yes --sign message.txt
>
> It shows the following error:
>
> gpg: no default secret key: secret key not available
> gpg: signing failed: secret key not available
>
> How can I solve this error, without modifying the command? (do I need to
> cha
nning a
> shell script in which following line causes error :
>
> |gpg --yes --sign message.txt |
>
> It shows the following error:
>
> |gpg: no default secret key: secret key not available gpg: signing
> failed: secret key not available |
>
> How can I solve this err
rror :
>
> gpg --yes --sign message.txt
>
> It shows the following error:
>
> gpg: no default secret key: secret key not available
> gpg: signing failed: secret key not available
>
> How can I solve this error, without modifying the command? (do I need to
> change an
ault secret key: secret key not available
gpg: signing failed: secret key not available
How can I solve this error, without modifying the command? (do I need to
change any settings). I am using gpg version (GnuPG) 1.4.16
>which gpg
is giving the output
/usr/bin/gpg
I Tried with --default-key
Awesome! you are genius, thanks for your assistance!
On 07/16/2015 11:48 PM, NIIBE Yutaka wrote:
On 07/17/2015 01:45 PM, punksgt wrote:
Still getting this error.
GPGError: GPG Failed, see log below:
= Begin GnuPG log =
gpg: no default secret key: secret key not available
gpg: [stdin
On 07/17/2015 01:45 PM, punksgt wrote:
> Still getting this error.
>
> GPGError: GPG Failed, see log below:
> = Begin GnuPG log =
> gpg: no default secret key: secret key not available
> gpg: [stdin]: sign+encrypt failed: secret key not available
> = End GnuPG
Okay, not to be a complete noob.
So I created a new key and selected "RSA and RSA"
Still getting this error.
GPGError: GPG Failed, see log below:
= Begin GnuPG log =
gpg: no default secret key: secret key not available
gpg: [stdin]: sign+encrypt failed: secret key not
On 07/16/2015 12:13 AM, punksgt wrote:
> Here is the details of my keys:
>
> |/home/bege/.gnupg/pubring.gpg
> -
> pub 2048R/7E4B6B9B 2015-07-15
> uid Chad H
>
> /home/bege/.gnupg/secring.gpg
> -
> sec 2048R/7E4B6B9B 201
purged gpg altogether and started with a
fresh start.
I created a new key and this is the response I get. |GPGError: GPG
Failed, see log below: = Begin GnuPG log = gpg: no default
secret key: secret key not available gpg: [stdin]: sign+encrypt failed:
secret key not available = End
ELG-E key, ID 1B8A6A37
> gpg: decryption failed: secret key not available
>
> But it is enough to confirm that this is not my key; I'll ask them to resend.
Note that gpg only shows the ID of the encryption subkey. The primary
key is what is what is commonly used to specify a key id.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 25.05.2012 16:39, DUELL, BOB wrote:
> Hi,
>
> Couple quick questions (and probably a FAQ):
>
> 1. Attempting to decrypt a file that was sent to me by someone
> else, I get this message:
>
> gpg: decryption failed:
B8A6A37
gpg: decryption failed: secret key not available
But it is enough to confirm that this is not my key; I'll ask them to resend.
And BTW, I really enjoy reading all the crypto discussions, although I
only understand about one percent. I suppose that makes me a "one percenter&q
e:
>
> gpg: decryption failed: secret key not available
>
> Could that mean the file was not encrypted with my public key?
Indeed.
> 2. Assuming the above it "yes", is there a command I can use to
> display what key(s) were used to encrypt the file?
On 05/25/2012 09:39 AM, DUELL, BOB wrote:
> 1. Attempting to decrypt a file that was sent to me by someone else,
> I get this message:
>
> gpg: decryption failed: secret key not available
>
> Could that mean the file was not encrypted with my public key?
yes, tha
Hi,
Couple quick questions (and probably a FAQ):
1. Attempting to decrypt a file that was sent to me by someone else,
I get this message:
gpg: decryption failed: secret key not available
Could that mean the file was not encrypted with my public key?
2. Assuming the above it
On 05/10/2011 18:43, Yard, John wrote:
I exported a key that was needed by a bank
from a pgp 6.5.8 secret keyring
...
When I cat the exported key asc block It describes itself
as a public key.
So I think you've described the problem ... you didn't export the secret
key, you exported the pu
I exported a key that was needed by a bank
from a pgp 6.5.8 secret keyring and inported into
gpg using -import .
Now when I sign using that key I get
'signing failed: secret key not available'.
In gpg I see the key when I do a gpg -list-keys,
But don't see it when I do a gpg -l
>>>> ýý ýglobals.gpg_profile, globals.volsize)
> >>>> ýýFile
> >>>>
> >
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/gpg.py",
> >>>> line 283, in GPGWriteFile
>
line 283, in GPGWriteFile
>>>> ýý ýfile.write(data)
>>>> ýýFile
>>>>
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/gpg.py",
>>>> line 153, in write
>>>> ýý ýself.gpg
> line 153, in write
> > �� �self.gpg_failed()
> > ��File
> >
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/gpg.py",
> > line 165, in gpg_failed
> > �� �raise GPGError, msg
> > GPGError: GPG Failed, s
uplicity/gpg.py",
line 153, in write
self.gpg_failed()
File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/gpg.py",
line 165, in gpg_failed
raise GPGError, msg
GPGError: GPG Failed, see log below:
= Begin GnuPG log =
Singh
To: gnupg-users@gnupg.org
Subject: Re: Can't use GPG key - secret key not available
Date: Thu, 30 Sep 2010 10:40:21 -0500
It did not work. I still get the same error as before.
I somehow doubt that this suggested solution would work, but how do I
get the 16 last characters ? I rem
Tried this.
No use.
I have two keys installed on this machine (different email addresses). It
just can't seem to use the newer one, regardless of the default-key
parameter.
Do I have to restart start-gpg-agent on Mac ? If so, how do I restart
without rebooting ?
On Thu, Sep 30, 2010 at 8:53 AM,
Thanks. I will try this out.
This is not for a mail user agent. This is for a duplicity backup to S3.
On Thu, Sep 30, 2010 at 12:04 PM, Charly Avital wrote:
> Madhusudan Singh wrote the following on 9/30/10 11:40 AM:
> > It did not work. I still get the same error as before.
> >
> > I somehow d
Madhusudan Singh wrote the following on 9/30/10 11:40 AM:
> It did not work. I still get the same error as before.
>
> I somehow doubt that this suggested solution would work, but how do I
> get the 16 last characters ? I remember seeing it when it was generated.
In Terminal:
gpg --fingerprint [y
It did not work. I still get the same error as before.
I somehow doubt that this suggested solution would work, but how do I get
the 16 last characters ? I remember seeing it when it was generated.
On Thu, Sep 30, 2010 at 8:53 AM, Charly Avital wrote:
> Noiano wrote the following on 9/30/10 3:4
Noiano wrote the following on 9/30/10 3:48 AM:
> Hi,
> check your gpg.conf. You should have a "default-key" parameter set. I
> have "default-key AB10E8D2".
>
> Hope this helps.
>
>
> Noiano
If the above does not help, try using the long key ID, 16 last
characters (instead of 8) of the key's fin
=
> gpg: no default secret key: secret key not available
> gpg: [stdin]: sign+encrypt failed: secret key not available
> = End GnuPG log =
>
>
> GPGError: GPG Failed, see log below:
> = Begin GnuPG log =====
> gpg: no default secret key: secret key n
I finally bit the bullet and cleaned out my old S3 bucket on Amazon and
started afresh with a new key.
Generated an RSA and RSA (4096 bit) key.
Tried to use it with duplicity. It fails:
= Begin GnuPG log =
gpg: no default secret key: secret key not available
gpg: [stdin]: sign+encrypt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rahul R wrote:
> But how to generate a secret key in command mode... i have the public
> key with me and imported it.. but still not able to decrypt...
>
My guess is that your best bet is to generate a new key-pair and send
the public key to a key-ser
But how to generate a secret key in command mode... i have the public key
with me and imported it.. but still not able to decrypt...
On Wed, Jul 21, 2010 at 9:22 PM, Hauke Laging wrote:
> Am Mittwoch 21 Juli 2010 17:37:44 schrieb Rahul R:
>
> > Can you please help me in importing the secret key?
ted 2010-05-11
> > "TEST_ENV (For testing new test env) >"
> > gpg: decryption failed: secret key not available
> >
> >
> >
> > Can anyone shed some light on how to troubleshoot this?
>
> The error message isn't
Am Mittwoch 21 Juli 2010 18:01:58 schrieb Rahul R:
> But how to generate a secret key in command mode... i have the public key
> with me and imported it.. but still not able to decrypt...
You are funny... Obviously it is impossible to "generate" the secret key for a
given public key. Otherwise it
Am Mittwoch 21 Juli 2010 17:37:44 schrieb Rahul R:
> Can you please help me in importing the secret key?
>
> Whats the command I should use and how?
gpg --import secretkey.asc
It might make sense for you to use an GUI (like GPA or Kleopatra) as tasks
like key import are very easy with a GUI.
pg: encrypted with 1024-bit ELG-E key, ID 424E35F0, created 2010-05-11
> "TEST_ENV (For testing new test env) "
> gpg: decryption failed: secret key not available
>
>
>
> Can anyone shed some light on how to troubleshoot this?
Obviously you
pg: encrypted with 1024-bit ELG-E key, ID 424E35F0, created 2010-05-11
> "TEST_ENV (For testing new test env) "
> gpg: decryption failed: secret key not available
>
>
>
> Can anyone shed some light on how to troubleshoot this?
The erro
(For testing new test env) "
gpg: decryption failed: secret key not available
Can anyone shed some light on how to troubleshoot this?
--
Thanks,
Regards,
Rahul R
.~.
/V\
// \\
/( )\
^`~'^
Mob: 09008030921
___
Gnup
CONNIE RODRIGUEZ wrote:
> I hope someone can help. I can encrypt files for our vendor but they cannot
> decrypt as it errors to secret key not available. I signed the vendors
> public key after I imported it into the unix system. Any ideas?
Likely 1 of 3 problems:
1. You're not
I hope someone can help. I can encrypt files for our vendor but they cannot
decrypt as it errors to secret key not available. I signed the vendors public
key after I imported it into the unix system. Any ideas?
Thank you in advance for any help anyone can provide.
Connie Rodriguez
D 5D969323
gpg: decryption failed: secret key not available
I am able to encrypt files using a script from the job scheduler, but
apparently running in this way the secret key can be located for
decrypting.
In another similar posting I found the response:
"It's n
gpg: encrypted with ELG-E key, ID 9B1D9DED
> gpg: decryption failed: secret key not available
>
> I have tried this with both a hard code passphrase (txt) as well as a
> passphrase file as well and still no luck? Anyone ever run into this by
> chance? I am wondering if it is som
. It comes up with the
following:
$gpg -batch -passphrase gocatsgo -output out.txt -decrypt 810x12.pgp
E:\ew\sv53\recv\tmp_recv>echo off
Press any key to continue . . .
gpg: encrypted with ELG-E key, ID 9B1D9DED
gpg: decryption failed: secret key not available
I have tried this with both a h
A.
>
> Encrypted how, symmetrically, or asymmetrically?
>
>> I put this encrypted txt-file to computer B and wanted to decrypt
>> it there. Then computer B said "secret key not available".
>> So I exported my keys from computer A and imported them in
>> c
here. Then computer B said "secret key not available".
> So I exported my keys from computer A and imported them in
> computer B.
How did you export them?
gpg -a --export YOURKEYID > yourkey.asc
# or
gpg -a --export-secret-keys YOURKEYID > yoursecretkey.asc
The first just e
: Telandor <[EMAIL PROTECTED]>
To: gnupg-users@gnupg.org
Subject: secret key (not) available
Date: Wed, 13 Dec 2006 01:24:30 -0800 (PST)
MIME-Version: 1.0
Received: from trithemius.gnupg.org ([217.69.76.44]) by
bay0-mc1-f4.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Wed, 13
D
Hallo everybody
I use GPG 1.4.4 and have encrypted a txt-file on computer A.
I put this encrypted txt-file to computer B and wanted to decrypt it there.
Then computer B said "secret key not available".
So I exported my keys from computer A and imported them in computer B.
But the erro
IN
gpg: verify CHV1 failed: invalid passphrase
gpg: using subkey B0DACEAB instead of primary key 0DC0B7D6
gpg: encrypted with 1024-bit RSA key, ID B0DACEAB, created 2006-08-15
"Wouter van Heyst <[EMAIL PROTECTED]>"
gpg: public key decryption failed: invalid passphrase
g
try to decrypt:
gpg: Warning: using insecure memory!
gpg: encrypted with ELG-E key, ID 7725AAB6
gpg: decryption failed: secret key not available
We're using GnuPG version 1.0.6.
What have we done wrong?
William F. Holmes
Sr. PeopleSoft Oracle Database Administrator
Desk: 703-818-5635
E
50 matches
Mail list logo
