On Sun, Dec 04, 2022 at 04:28:00PM +0200, Teemu Likonen wrote:
> * 2022-12-04 12:05:56+, Alain D. D. Williams wrote:
>
> > Part of the problem is the hopeless message "Server indicated a
> > failure" which says little. Any idea how I could get something more
> > informative ?
>
> You can chan
* 2022-12-04 12:05:56+, Alain D. D. Williams wrote:
> Part of the problem is the hopeless message "Server indicated a
> failure" which says little. Any idea how I could get something more
> informative ?
You can change debug logging level. Edit ~/.gnupg/dirmngr.conf file and
write something l
On Sat, Dec 03, 2022 at 02:59:41PM -0500, Jeffrey Walton wrote:
> keys.openpgp.org should be operational. It responds to ping.
>
> Also have a look at
> https://lists.gnupg.org/pipermail/gnupg-users/2021-June/065261.html .
No, that is not the issue. It works on Debian 11 but not Debian 10, both
On Sat, Dec 3, 2022 at 12:42 PM Alain D D Williams wrote:
>
> I am running Debian 10 (buster). I generated a new key that I wanted to
> upload,
> but it fails:
>
> $ gpg --send-keys 0xBA366B977C06BAF7
> gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org
> gpg: keyserver send failed:
I am running Debian 10 (buster). I generated a new key that I wanted to upload,
but it fails:
$ gpg --send-keys 0xBA366B977C06BAF7
gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org
gpg: keyserver send failed: Server indicated a failure
gpg: keyserver send failed: Server indicated a f
On Tue, Sep 25, 2007 at 08:37:12AM -0500, Ron Johnson <[EMAIL PROTECTED]> was
heard to say:
> -BEGIN PGP SIGNED MESSAGE-
> What about:
> sudo (command_1 | command_2)
Won't work -- the ()s are shell metacharacters, and sudo knows
nothing about them. What you would need to do this with j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/24/07 21:44, Marc Shapiro wrote:
> Kamaraju S Kusumanchi wrote:
>> David Fox wrote:
>>
>>> It might be worth mentioning that "sudo" doesn't work across pipes:
>>>
>>> For instance:
>>>
>>> sudo command_1 | command_2
>>>
>>> The first command wi
Kamaraju S Kusumanchi wrote:
David Fox wrote:
It might be worth mentioning that "sudo" doesn't work across pipes:
For instance:
sudo command_1 | command_2
The first command will be run as root, but the second will be run with
normal user permissions. You can probably get around that by enc
David Fox wrote:
>
> It might be worth mentioning that "sudo" doesn't work across pipes:
>
> For instance:
>
> sudo command_1 | command_2
>
> The first command will be run as root, but the second will be run with
> normal user permissions. You can probably get around that by enclosing
> the ent
On 9/23/07, Marc Shapiro <[EMAIL PROTECTED]> wrote:
> If I had run as root, it probably would have worked, but I used sudo.
> This only runs the first command as root (I believe), so the command
> 'apt-key add - ' was run as a normal user and did not like that. Using
It might be worth mentioning
Marc Shapiro wrote:
I followed the instructions on the backports instruction page:
If you are using *etch* and you want apt to verify the downloaded
backports you can import backports.org archive’s key into apt:
gpg --keyserver hkp://subkeys.pgp.net -
I am running Etch and I want to install the alpine package from
etch-backports.
I also want to verify the downloaded files.
I followed the instructions on the backports instruction page:
If you are using *etch* and you want apt to verify the downloaded
On Wed, Aug 20, 2003 at 08:31:47PM +0100, Karl E. Jorgensen wrote:
> On Wed, Aug 13, 2003 at 04:32:05PM -0400, Vikki Roemer wrote:
> > Hi,
> > I have a gpg key, and under my old install I could get gpg to work with
> > mutt. Now mutt and gpg won't work together. Apparently gpg can't find my
> > k
On Wed, Aug 13, 2003 at 04:32:05PM -0400, Vikki Roemer wrote:
> Hi,
> I have a gpg key, and under my old install I could get gpg to work with
> mutt. Now mutt and gpg won't work together. Apparently gpg can't find my
> key, or something like that. The errors I get every time I try to send a
> si
Hi,
I have a gpg key, and under my old install I could get gpg to work with
mutt. Now mutt and gpg won't work together. Apparently gpg can't find my
key, or something like that. The errors I get every time I try to send a
signed email are:
gpg: [don't know]: invalid packet (ctb=00)
gpg: read_key
15 matches
Mail list logo
