Re: GPG problems
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 change debug logging level. Edit ~/.gnupg/dirmngr.conf file and > write something like this: > > debug-level expert #or: guru > log-file /tmp/dirmngr-log.txt > > Then kill dirmngr > > $ gpgconf --kill dirmngr > > and try key servers again. See the log file mentioned above. Thanks ... it does not really help (I attach it). The message is: command 'KS_PUT' failed: Server indicated a failure I ran it with debugging on the Debian 11 machine where it works. I put the PIv4 address for keys.openpgp.org into /etc/hosts - the Debian 10 machine has IPv6 that works, the Debian 11 machine is IPv4 only. No change. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html #include 2022-12-04 17:44:27 dirmngr[18851.0] permanently loaded certificates: 138 2022-12-04 17:44:27 dirmngr[18851.0] runtime cached certificates: 0 2022-12-04 17:44:27 dirmngr[18851.0]trusted certificates: 138 (137,0,0,1) 2022-12-04 17:44:27 dirmngr[18851.6] handler for fd 6 started 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> # Home: /home/addw/.gnupg 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> # Config: /home/addw/.gnupg/dirmngr.conf 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> OK Dirmngr 2.2.27 at your service 2022-12-04 17:44:27 dirmngr[18851.6] connection from process 18850 (1000:1000) 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- GETINFO version 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> D 2.2.27 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> OK 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- KEYSERVER 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> S KEYSERVER hkps://keys.openpgp.org 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> OK 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- KS_PUT 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> INQUIRE KEYBLOCK 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- [ 44 20 98 33 04 60 ec 50 1f 16 09 2b 06 01 04 01 ...(626 byte(s) skipped) ] 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- END 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> INQUIRE KEYBLOCK_INFO 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- D pub::256:22:BA366B977C06BAF7:1626099743:::%0Afpr:4D48D5BAF3736D50214AFC3FBA366B977C06BAF7:%0Auid:1626099743Alain D D Williams :::%0Auid:1670002234Alain D D Williams :::%0Asub::256:18:0315E84A964E21C9:1626099743:::%0Afpr:75F7570849B82972171A762C0315E84A964E21C9:%0A 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- END 2022-12-04 17:44:27 dirmngr[18851.6] command 'KS_PUT' failed: Server indicated a failure 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> ERR 219 Server indicated a failure 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- BYE 2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> OK closing connection 2022-12-04 17:44:27 dirmngr[18851.6] handler for fd 6 terminated 2022-12-04 17:55:27 dirmngr[18851.0] running scheduled tasks 2022-12-04 18:05:28 dirmngr[18851.0] running scheduled tasks 2022-12-04 18:15:28 dirmngr[18851.0] running scheduled tasks 2022-12-04 18:25:29 dirmngr[18851.0] running scheduled tasks 2022-12-04 18:33:58 dirmngr[18851.6] handler for fd 6 started 2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 -> # Home: /home/addw/.gnupg 2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 -> # Config: /home/addw/.gnupg/dirmngr.conf 2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 -> OK Dirmngr 2.2.27 at your service 2022-12-04 18:33:58 dirmngr[18851.6] connection from process 22347 (1000:1000) 2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 <- KILLDIRMNGR 2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 -> OK closing connection 2022-12-04 18:36:18 dirmngr[22361.0] permanently loaded certificates: 138 2022-12-04 18:36:18 dirmngr[22361.0] runtime cached certificates: 0 2022-12-04 18:36:18 dirmngr[22361.0]trusted certificates: 138 (137,0,0,1) 2022-12-04 18:36:18 dirmngr[22361.6] handler for fd 6 started 2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 -> # Home: /home/addw/.gnupg 2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 -> # Config: /home/addw/.gnupg/dirmngr.conf 2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 -> OK Dirmngr 2.2.27 at your service 2022-12-04 18:36:18 dirmngr[22361.6] connection from process 22360 (1000:1000) 2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 <- GETINFO version 2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 -> D 2.2.27 2022-12-04 18:36:18 dirmngr[22361.6] DBG
Re: GPG problems
* 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 like this: debug-level expert #or: guru log-file /tmp/dirmngr-log.txt Then kill dirmngr $ gpgconf --kill dirmngr and try key servers again. See the log file mentioned above. -- /// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/ // OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462 signature.asc Description: PGP signature
Re: GPG problems
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 attempts within a few minutes of each other, both connect to hkps://keys.openpgp.org Both run the same version of gpg (GnuPG) 2.2.27 (I installed from backports on Debian 10) gpg reports the version of libgcrypt On Debian 10 it is 1.8.4 on Debian 11 it is 1.8.8 Could that be an issue ? I am reluctant to speculatively upgrade for fear of breaking something else. Part of the problem is the hopeless message "Server indicated a failure" which says little. Any idea how I could get something more informative ? -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html #include
Re: GPG problems
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: Server indicated a failure > gpg: keyserver send failed: Server indicated a failure > > I copied my ~/.gnupg to a Debian 11 (bullesys) machine, it works: > > $ gpg --send-keys 0xBA366B977C06BAF7 > gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org > $ > > Back on buster I grabbed the latest version: > /etc/apt/sources.list: > deb http://deb.debian.org/debian/ buster-backports main contrib > non-free > # apt -V -t=buster-backports install gpg > > I killed the dirmngr daemon: > > # killall dirmngr > > I tried the send-keys again and got the same result, ie failure. > > Please: what should I do to fix this. 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 . Jeff
GPG problems
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 failure I copied my ~/.gnupg to a Debian 11 (bullesys) machine, it works: $ gpg --send-keys 0xBA366B977C06BAF7 gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org $ Back on buster I grabbed the latest version: /etc/apt/sources.list: deb http://deb.debian.org/debian/ buster-backports main contrib non-free # apt -V -t=buster-backports install gpg I killed the dirmngr daemon: # killall dirmngr I tried the send-keys again and got the same result, ie failure. Please: what should I do to fix this. Thanks in advance -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html #include
Re: Etch-backports and gpg problems (SOLVED)
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 just one sudo is something like: sudo sh -c "command_1 | command_2" with appropriate wariness towards quoting gremlins. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Etch-backports and gpg problems (SOLVED)
-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 will be run as root, but the second will be run with >>> normal user permissions. You can probably get around that by enclosing >>> the entire pipechain in quotes, but there's sometimes when just >>> entering su for the command and exiting su when finished is easier. >>> >>> >> >> hmmm... How about >> >> sudo command_1 | sudo command_2 >> >> > That's exactly the way I did it. Worked like a charm. What about: sudo (command_1 | command_2) - -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+Q8IS9HxQb37XmcRAuZ2AKDC/UmOaIjXhxO91YyXP1YQGA6CNgCgyFqi aHfoYyJi61SPlXS7UMbqL6A= =oxZK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Etch-backports and gpg problems (SOLVED)
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 enclosing the entire pipechain in quotes, but there's sometimes when just entering su for the command and exiting su when finished is easier. hmmm... How about sudo command_1 | sudo command_2 That's exactly the way I did it. Worked like a charm. -- Marc Shapiro [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Etch-backports and gpg problems (SOLVED)
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 entire pipechain in quotes, but there's sometimes when just > entering su for the command and exiting su when finished is easier. > >> hmmm... How about sudo command_1 | sudo command_2 raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Etch-backports and gpg problems (SOLVED)
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 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 entire pipechain in quotes, but there's sometimes when just entering su for the command and exiting su when finished is easier. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Etch-backports and gpg problems (SOLVED)
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 --recv-keys 16BA136C gpg --export | apt-key add - or wget -O - http://backports.org/debian/archive.key | apt-key add - but after executing the second option (or the second line of the first option) I get the following messages: gpg: no writable keyring found: eof gpg: error reading `-': general error gpg: import from `-' failed: general error This occurs whether I run this as a normal user, or with sudo. What am I doing wrong? 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 sudo on that command, as well, ran without errors. Alpine is now installed and aptitude gives me no errors. -- Marc Shapiro [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Etch-backports and gpg problems
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 backports you can import backports.org archive’s key into apt: gpg --keyserver hkp://subkeys.pgp.net --recv-keys 16BA136C gpg --export | apt-key add - or wget -O - http://backports.org/debian/archive.key | apt-key add - but after executing the second option (or the second line of the first option) I get the following messages: gpg: no writable keyring found: eof gpg: error reading `-': general error gpg: import from `-' failed: general error This occurs whether I run this as a normal user, or with sudo. What am I doing wrong? If I then try to run 'aptitude update' I get the following: [EMAIL PROTECTED]:~$ sudo aptitude update Get:1 http://debian.oregonstate.edu etch Release.gpg [378B] Get:2 http://security.debian.org etch/updates Release.gpg [189B] Hit http://debian.oregonstate.edu etch Release Hit http://security.debian.org etch/updates Release Ign http://debian.oregonstate.edu etch/main Packages/DiffIndex Get:3 http://www.debian-multimedia.org etch Release.gpg [189B] Ign http://security.debian.org etch/updates/main Packages/DiffIndex Ign http://debian.oregonstate.edu etch/contrib Packages/DiffIndex Ign http://debian.oregonstate.edu etch/non-free Packages/DiffIndex Ign http://security.debian.org etch/updates/contrib Packages/DiffIndex Ign http://debian.oregonstate.edu etch/main Sources/DiffIndex Ign http://debian.oregonstate.edu etch/contrib Sources/DiffIndex Ign http://debian.oregonstate.edu etch/non-free Sources/DiffIndex Ign http://security.debian.org etch/updates/non-free Packages/DiffIndex Hit http://debian.oregonstate.edu etch/main Packages Hit http://debian.oregonstate.edu etch/contrib Packages Hit http://debian.oregonstate.edu etch/non-free Packages Hit http://debian.oregonstate.edu etch/main Sources Hit http://debian.oregonstate.edu etch/contrib Sources Hit http://security.debian.org etch/updates/main Packages Hit http://www.debian-multimedia.org etch Release Get:4 http://www.backports.org etch-backports Release.gpg [189B] Hit http://debian.oregonstate.edu etch/non-free Sources Hit http://security.debian.org etch/updates/contrib Packages Hit http://security.debian.org etch/updates/non-free Packages Hit http://www.backports.org etch-backports Release Err http://www.backports.org etch-backports Release Ign http://www.debian-multimedia.org etch/main Packages/DiffIndex Get:5 http://www.backports.org etch-backports Release [43.7kB] Hit http://www.debian-multimedia.org etch/main Packages Ign http://www.backports.org etch-backports Release Hit http://www.backports.org etch-backports/main Packages/DiffIndex Hit http://www.backports.org etch-backports/contrib Packages/DiffIndex Hit http://www.backports.org etch-backports/non-free Packages/DiffIndex Hit http://www.backports.org etch-backports/contrib Packages Fetched 43.9kB in 2s (18.0kB/s) Reading package lists... Done W: GPG error: http://www.backports.org etch-backports Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EA8E8B2116BA136C W: You may want to run apt-get update to correct these problems Can someone help me get this sorted out, please? -- Marc Shapiro [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gpg problems
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 > > 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_keyblock: read error: invalid packet > > gpg: enum_keyblocks failed: invalid keyring > > gpg: no default secret key: invalid keyring > > gpg: signing failed: invalid keyring > > I'd suspect that this is just gpg - not mutt. To eliminate mutt, try > signing some file - if that fails too, then the problem is most likely > with gnupg. Ok, it's a gnupg problem. > > I don't know how to get it work now. I kept all my dotfiles from my old > > install (I was running testing, but now that I'm running a server I'm > > running stable-- don't know if that's pertinent or not), so everything > > should run the same as before, right? > > So: you used to run testing, but now run stable. This would imply that > you have downgraded gnupg: stable has version 1.0.6-3, testing has > 1.2.2-1... Right. > Perhaps the newer version (=older for you) of gnupg may have done things > to your keyring that the older (=newer for you) version doesn't > understand. Or perhaps there were key types added in gnupg.. > > Did you generate your gnupg key with the testing version of gnupg? The > stable version might not understand that sort of key. I don't think so. IIRC, I generated the key *before* I upgraded to testing, so the key was generated with stable's gpg. But, OTOH, the past ~8 months are kinda fuzzy (for reasons I'd rather not go into), so I'm not entirely sure when I upgraded. *shrug* Sorry. > I'd suggest studying gnupg's changelog for details; if it is only the > keyring format that has changed, then you should be able to export all > the keys (using gnupg/testing) and re-create them using gnupg/stable. > [make backups until ankle-depth first though. Keys are important] How do I run testing apps in stable? I don't want to upgrade and then downgrade again. Can I just run the testing version of gpg in a stable system? If so, at that rate I could run metalog, too. (I love metalog, but it's only in testing, not stable, so I'm stuck with syslog-ng. :b) Anyway... Is it possible to run kind of a hybrid system? TIA. -- Vikki RoemerHomepage: http://neuromancer.homelinux.com/ Registered Linux user #280021 http://counter.li.org/ Linux is like a wigwam: no Windows, no Gates, Apache inside. PGP fingerprint: 0A3E 0AE4 CCD9 FF31 B4BB C859 2DE1 B1D8 5CE0 1578 Keyserver: http://pgp.mit.edu/ -BEGIN GEEK CODE BLOCK- Version: 3.12 GAT d-(?) s: a--- C(++) UL P+ L+++> E W++ N+ o? K- w--() O? M? V?(-) PS+(+++) PE(++) Y+ PGP++ t+@ 5 X-() R*(?) tv-- b+++(++) DI+ D--(?) G e-(*)>+ h! r% x? --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gpg problems
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 > signed email are: > gpg: [don't know]: invalid packet (ctb=00) > gpg: read_keyblock: read error: invalid packet > gpg: enum_keyblocks failed: invalid keyring > gpg: no default secret key: invalid keyring > gpg: signing failed: invalid keyring I'd suspect that this is just gpg - not mutt. To eliminate mutt, try signing some file - if that fails too, then the problem is most likely with gnupg. > I don't know how to get it work now. I kept all my dotfiles from my old > install (I was running testing, but now that I'm running a server I'm > running stable-- don't know if that's pertinent or not), so everything > should run the same as before, right? So: you used to run testing, but now run stable. This would imply that you have downgraded gnupg: stable has version 1.0.6-3, testing has 1.2.2-1... Perhaps the newer version (=older for you) of gnupg may have done things to your keyring that the older (=newer for you) version doesn't understand. Or perhaps there were key types added in gnupg.. Did you generate your gnupg key with the testing version of gnupg? The stable version might not understand that sort of key. I'd suggest studying gnupg's changelog for details; if it is only the keyring format that has changed, then you should be able to export all the keys (using gnupg/testing) and re-create them using gnupg/stable. [make backups until ankle-depth first though. Keys are important] HTH -- Karl E. Jørgensen [EMAIL PROTECTED] http://karl.jorgensen.com Today's fortune: If you're not part of the solution, you're part of the precipitate. pgp0.pgp Description: PGP signature
gpg problems
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_keyblock: read error: invalid packet gpg: enum_keyblocks failed: invalid keyring gpg: no default secret key: invalid keyring gpg: signing failed: invalid keyring I don't know how to get it work now. I kept all my dotfiles from my old install (I was running testing, but now that I'm running a server I'm running stable-- don't know if that's pertinent or not), so everything should run the same as before, right? TIA. -- Vikki RoemerHomepage: http://neuromancer.homelinux.com/ Registered Linux user #280021 http://counter.li.org/ What's this script do? unzip ; touch ; finger ; mount ; gasp ; yes ; umount ; sleep Hint for the answer: not everything is computer-oriented. Sometimes you're in a sleeping bag, camping out with your girlfriend. PGP fingerprint: 0A3E 0AE4 CCD9 FF31 B4BB C859 2DE1 B1D8 5CE0 1578 Keyserver: http://pgp.mit.edu/ -BEGIN GEEK CODE BLOCK- Version: 3.12 GAT d-(?) s: a--- C(++) UL P+ L+++> E W++ N+ o? K- w--() O? M? V?(-) PS+(+++) PE(++) Y+ PGP++ t+@ 5 X-() R*(?) tv-- b+++(++) DI+ D--(?) G e-(*)>+ h! r% x? --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
