- WLUG - wlug.mailman3.com

Re: [Wlug] traceroute troubles

by James Baldassari

Hi Greg. I have a similar situation at home. When I need to do a traceroute I use the -I switch (e.g. traceroute -I www.google.com) which uses ICMP echos instead of UDP datagrams. I believe that ping uses ICMP requests by default, which may explain why you can ping outside your network. Hope this helps. -James Baldassari > I'm having trouble getting traceroutes to go out with my slick new dsl > connection. The modem has a router built into it, and even with its > internal firewall turned off, the only output I get from a traceroute is > the router'r IP number and times, followed by 29 lines of stars. > > I tried shutting down the network and using my dialup account, and > traceroute works fine. I know it's not the firewall on my machine, > because it makes no difference if it's on or off with the dsl, and > traceroute works on the dialup with the firewall running. (Yes, I did > remember to change the default path in the firewall config from eth0 to > ppp0) > > Any ideas? Is this likely to be something built into the dsl modem, or > something with Verizon? Or might I have something screwed up in my > network setup? I can ping my other computers and I can ping out to the > internet ok. > > Thanks, > Greg Avedissian > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > > >

April 28, 2004

traceroute troubles

by gma2004＠verizon.net

I'm having trouble getting traceroutes to go out with my slick new dsl connection. The modem has a router built into it, and even with its internal firewall turned off, the only output I get from a traceroute is the router'r IP number and times, followed by 29 lines of stars. I tried shutting down the network and using my dialup account, and traceroute works fine. I know it's not the firewall on my machine, because it makes no difference if it's on or off with the dsl, and traceroute works on the dialup with the firewall running. (Yes, I did remember to change the default path in the firewall config from eth0 to ppp0) Any ideas? Is this likely to be something built into the dsl modem, or something with Verizon? Or might I have something screwed up in my network setup? I can ping my other computers and I can ping out to the internet ok. Thanks, Greg Avedissian

April 28, 2004

Re: [Wlug] ssh known_hosts

by Bill Mills-Curran

Frank, 10.14.36.204 is the server IP. BTW, it gives that message even though I use the hostname on the ssh command line. I ran ssh -v, and found the problem... I needed to modify known_hosts2, not known_hosts. Silly mistake on my part, although the documentation does not mention known_hosts2 Thanks for the push in the right direction. Bill On Tue, Apr 27, 2004 at 10:53:24AM -0400, frank p wrote: > > Is '10.14.36.204' your client or your server? > First reaction is that you should just replace the old ip with the new one > in the known_hosts file, though maybe it's no that simple. > It could be that either your client doesn't want to connect to a server it > doesn't know about, or your server doesn't want to accept connections from > a client it doesn't know about. It could be changes needed in your > ~/.ssh/known_hosts on the client or /etc/ssh/ssh_known_hosts on the > server. > Can you be a little more explicit about exactly what you are trying to do? > Maybe include output from doing a 'ssh -v <host/ip>'... > > np, > -poz > > > On Tue, 27 Apr 2004, Bill Mills-Curran wrote: > > > I'm having a problem with known (or unknown!) hosts since changing the > > IP address on a server. > > > > Server info: > > Redhat 8.0 > > ssh -V: OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f > > > > Client info: > > Redhat 9 > > ssh -V: OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f > > > > When logging into the server, I'm getting the following message: > > > > RSA host key for IP address '10.14.36.204' not in list of known hosts. > > > > I've played around with ~/.ssh/known_hosts (even renaming it), but I > > still get the message. Looking at the documentation for the > > known_hosts file format (in sshd man page), my current known_hosts > > file, looks quite a bit different (many fields are omitted). > > > > Why do I get the message, and how do I get rid of it? > > > > TIA, > > Bill > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug

April 27, 2004

Re: [Wlug] ssh known_hosts

by frank p

Is '10.14.36.204' your client or your server? First reaction is that you should just replace the old ip with the new one in the known_hosts file, though maybe it's no that simple. It could be that either your client doesn't want to connect to a server it doesn't know about, or your server doesn't want to accept connections from a client it doesn't know about. It could be changes needed in your ~/.ssh/known_hosts on the client or /etc/ssh/ssh_known_hosts on the server. Can you be a little more explicit about exactly what you are trying to do? Maybe include output from doing a 'ssh -v <host/ip>'... np, -poz On Tue, 27 Apr 2004, Bill Mills-Curran wrote: > I'm having a problem with known (or unknown!) hosts since changing the > IP address on a server. > > Server info: > Redhat 8.0 > ssh -V: OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f > > Client info: > Redhat 9 > ssh -V: OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f > > When logging into the server, I'm getting the following message: > > RSA host key for IP address '10.14.36.204' not in list of known hosts. > > I've played around with ~/.ssh/known_hosts (even renaming it), but I > still get the message. Looking at the documentation for the > known_hosts file format (in sshd man page), my current known_hosts > file, looks quite a bit different (many fields are omitted). > > Why do I get the message, and how do I get rid of it? > > TIA, > Bill

April 27, 2004

ssh known_hosts

by Bill Mills-Curran

I'm having a problem with known (or unknown!) hosts since changing the IP address on a server. Server info: Redhat 8.0 ssh -V: OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f Client info: Redhat 9 ssh -V: OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f When logging into the server, I'm getting the following message: RSA host key for IP address '10.14.36.204' not in list of known hosts. I've played around with ~/.ssh/known_hosts (even renaming it), but I still get the message. Looking at the documentation for the known_hosts file format (in sshd man page), my current known_hosts file, looks quite a bit different (many fields are omitted). Why do I get the message, and how do I get rid of it? TIA, Bill

April 27, 2004

Re: [Wlug] test

by gma2004＠verizon.net

Bill Smith wrote: > > > What were you testing? > New email address. Wanted to make sure I was still here and see who it said I was. Greg

April 26, 2004

Re: [Wlug] test

by Bill Smith

On Fri, 23 Apr 2004 17:27:06 -0400 gma2004(a)verizon.net wrote: > test What were you testing? -- William Smith wsmith(a)chezsmith.com Fall River, MA

April 26, 2004

Re: [Wlug] PGP Keysigning

by gma2004＠verizon.net

Theo, Thanks. No, I didn't import revoke.asc, and your suggestion worked. Next step is to figure out encryption. Greg Theo Van Dinter wrote: > On Fri, Apr 23, 2004 at 05:39:38PM -0400, gma2004(a)verizon.net wrote: > >>I did gpg --fingerprint >> >>When I do gpg --list-sigs, my new key is listed as revoked. Did I screw >>up on following the first set of directions? > > > It depends. Did you do something like "gpg --import revoke.asc" ? > If so, you revoked your public key. The last version of your key that I > saw on the keyserver isn't revoked, so ... You could, in theory, go in, > delete your public key from your keyring, then do a recv-key to download > the non-revoked one. > > > more info on revoking in: http://www.hackdiary.com/archives/000042.html, > http://www.gnupg.org/(en)/documentation/faqs.html#q4.17 >

April 24, 2004

Re: [Wlug] PGP Keysigning

by gma2004＠verizon.net

OK, I guess that older key is really mine. I was able to change the password, but I'm still not sure about how to handle this. If I do use this older key, how do I change the email address on it? Is adduser the correct command for this? Would it make more sense to revoke that one and make a new one? Greg gma2004(a)verizon.net wrote: > I got as far as 'Really sign?' and then it didn't like my passphrase. > > I did gpg --fingerprint > > It seems that I already have a key that I allegedly made in December 2003. I don't remember doing this, and I don't understand how I could have done it without going through the procedure that we all just used this week. > > When I do gpg --list-sigs, my new key is listed as revoked. Did I screw up on following the first set of directions? > > I tried putting the new key ID in the default key line of my options file, and when I try to sign someone's key, I get the message > gpg: no default secret key: unusable secret key > > Any suggestions on what to do? > > Thanks > > Greg Avedissian

April 23, 2004

Re: [Wlug] PGP Keysigning

by Theo Van Dinter

On Fri, Apr 23, 2004 at 05:39:38PM -0400, gma2004(a)verizon.net wrote: > I did gpg --fingerprint > > When I do gpg --list-sigs, my new key is listed as revoked. Did I screw > up on following the first set of directions? It depends. Did you do something like "gpg --import revoke.asc" ? If so, you revoked your public key. The last version of your key that I saw on the keyserver isn't revoked, so ... You could, in theory, go in, delete your public key from your keyring, then do a recv-key to download the non-revoked one. more info on revoking in: http://www.hackdiary.com/archives/000042.html, http://www.gnupg.org/(en)/documentation/faqs.html#q4.17 -- Randomly Generated Tagline: "At least it had heated rear windows--so your hands would stay warm while you pushed." - Unknown about the Yugo

April 23, 2004

Re: [Wlug] PGP Keysigning

by gma2004＠verizon.net

I got as far as 'Really sign?' and then it didn't like my passphrase. I did gpg --fingerprint It seems that I already have a key that I allegedly made in December 2003. I don't remember doing this, and I don't understand how I could have done it without going through the procedure that we all just used this week. When I do gpg --list-sigs, my new key is listed as revoked. Did I screw up on following the first set of directions? I tried putting the new key ID in the default key line of my options file, and when I try to sign someone's key, I get the message gpg: no default secret key: unusable secret key Any suggestions on what to do? Thanks Greg Avedissian Charles R. Anderson wrote: > To complete the PGP Keysigning process: > > 1. Sign All The Verified IDs On The Verified Keys > > gpg --keyserver pgp.mit.edu --recv-keys <Key_ID> > gpg --sign-key <Key_ID> > > [ Verify the fingerprint against your sheet. You probably want to select > (3) I have done very careful checking in this case, since we > met in person and verified physical photo ID's. ] > > 2. Send The Signed Keys Back Up To The Designated Keyserver > > gpg --keyserver pgp.mit.edu --send-key <Key_ID> > > Finally, once everyone has signed everyone else's keys and sent them > to the keyserver, you will want to download the signed versions once > more from the keyserver. You can do this at any time without fear of > overwritting keys--GnuPG will always merge the changes into your local > keyring (--recv-keys) or the remote keyserver (--send-keys) as > necessary. > > 3. Download the Signed Keys from The Designated Keyserver > > gpg --keyserver pgp.mit.edu --recv-key <Key_ID> > > It is a good idea to periodically re-download keys to receive new > signatures, learn of revoked keys, etc. You can tell a signature was > added by the output of --recv-keys. You can list key signatures with: > > gpg --list-sigs [<Key_ID>] > > where <Key_ID> is optional. > > You may notice some keys signed by unknown user ids. If you receive > those keys from the keyserver(s) you can build your Web Of Trust to > include people you don't know. This gets into how much you trust > people with whom you have verified keys directly to sign *other* > people's keys properly/securely. More on this later.... > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

April 23, 2004

test

by gma2004＠verizon.net

test

April 23, 2004

Re: [Wlug] PGP Keysigning

by gma2004＠verizon.net

I got as far as Really sign? And then it asked for my passphrase, but I'm not sure it really knows who I am. It has my rcn address, which is not the one I used to create the key. WTF??? What do I do if my passphrase fails? Why is my middle initial missing? Why is my key ID different from what it was when I created it, and how did I create it in 2003? when I do gpg --fingerprint, I get the key I didn't know about, the one I made this week, and one from somebody I don't know and who doesn't appear in my address book (Vincent Danen). When I do gpg --list-sigs, my new key is listed as revoked. Did I screw up on following the first set of directions? Greg Charles R. Anderson wrote: > To complete the PGP Keysigning process: > > 1. Sign All The Verified IDs On The Verified Keys > > gpg --keyserver pgp.mit.edu --recv-keys <Key_ID> > gpg --sign-key <Key_ID> > > [ Verify the fingerprint against your sheet. You probably want to select > (3) I have done very careful checking in this case, since we > met in person and verified physical photo ID's. ] > > 2. Send The Signed Keys Back Up To The Designated Keyserver > > gpg --keyserver pgp.mit.edu --send-key <Key_ID> > > Finally, once everyone has signed everyone else's keys and sent them > to the keyserver, you will want to download the signed versions once > more from the keyserver. You can do this at any time without fear of > overwritting keys--GnuPG will always merge the changes into your local > keyring (--recv-keys) or the remote keyserver (--send-keys) as > necessary. > > 3. Download the Signed Keys from The Designated Keyserver > > gpg --keyserver pgp.mit.edu --recv-key <Key_ID> > > It is a good idea to periodically re-download keys to receive new > signatures, learn of revoked keys, etc. You can tell a signature was > added by the output of --recv-keys. You can list key signatures with: > > gpg --list-sigs [<Key_ID>] > > where <Key_ID> is optional. > > You may notice some keys signed by unknown user ids. If you receive > those keys from the keyserver(s) you can build your Web Of Trust to > include people you don't know. This gets into how much you trust > people with whom you have verified keys directly to sign *other* > people's keys properly/securely. More on this later.... > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

April 23, 2004

PGP Keysigning

by Charles R. Anderson

To complete the PGP Keysigning process: 1. Sign All The Verified IDs On The Verified Keys gpg --keyserver pgp.mit.edu --recv-keys <Key_ID> gpg --sign-key <Key_ID> [ Verify the fingerprint against your sheet. You probably want to select (3) I have done very careful checking in this case, since we met in person and verified physical photo ID's. ] 2. Send The Signed Keys Back Up To The Designated Keyserver gpg --keyserver pgp.mit.edu --send-key <Key_ID> Finally, once everyone has signed everyone else's keys and sent them to the keyserver, you will want to download the signed versions once more from the keyserver. You can do this at any time without fear of overwritting keys--GnuPG will always merge the changes into your local keyring (--recv-keys) or the remote keyserver (--send-keys) as necessary. 3. Download the Signed Keys from The Designated Keyserver gpg --keyserver pgp.mit.edu --recv-key <Key_ID> It is a good idea to periodically re-download keys to receive new signatures, learn of revoked keys, etc. You can tell a signature was added by the output of --recv-keys. You can list key signatures with: gpg --list-sigs [<Key_ID>] where <Key_ID> is optional. You may notice some keys signed by unknown user ids. If you receive those keys from the keyserver(s) you can build your Web Of Trust to include people you don't know. This gets into how much you trust people with whom you have verified keys directly to sign *other* people's keys properly/securely. More on this later....

April 23, 2004

Re: [Wlug] Free systems to good home...

by Walt Sawyer

I'll take the mini towers if they haven't gone to some yet. Bring them to the May meeting. Thanks, Walt On Wed, 2004-04-21 at 18:58, Theo Van Dinter wrote: > I thought I'd throw this out and see if anyone was interested... > > I've got 3 machines just sitting around collecting dust that I'd like to > give away. They're pretty much base-bones (case, ps, mb, cpu) although > I may have some memory for the P120 and the P200 (have to check when I > get home): > > P120, Mini-Tower > P166, Full Tower > P200 Overdrive, Mini-Tower > > > If you're interested in grabbing one of these, let me know and I'll > bring it along to the meeting tomorrow night. :) [image] [image] [image] Walt Sawyer wsawyer(a)norfolk-county.com

April 23, 2004

Summer Intern Job

by Karl Hiramoto

For anyone that is interested in a programming job.. http://jobs.accusense.com/programmer-analyist-intern.html -- -- Karl Hiramoto karl at hiramoto dot org http://karl.hiramoto.org/ Mobile: 508.517.4819 Work: 978-425-2090

April 22, 2004

Free systems to good home...

by Theo Van Dinter

I thought I'd throw this out and see if anyone was interested... I've got 3 machines just sitting around collecting dust that I'd like to give away. They're pretty much base-bones (case, ps, mb, cpu) although I may have some memory for the P120 and the P200 (have to check when I get home): P120, Mini-Tower P166, Full Tower P200 Overdrive, Mini-Tower If you're interested in grabbing one of these, let me know and I'll bring it along to the meeting tomorrow night. :) -- Randomly Generated Tagline: "To his dog, every man is Napoleon, hence the constant popularity of dogs." - Susan Vick

April 21, 2004

Re: [Wlug] Reminder: WLUG Meeting

by Charles R. Anderson

On Mon, Apr 19, 2004 at 10:01:46PM -0400, Andy Stewart wrote: > This is a reminder about the upcoming WLUG meeting, to be held on Thursday, > April 22, at 7:00 PM at the usual place (the Access Grid room at WPI). > > At this meeting, we'll be having a PGP keysigning party, as described by Chuck > Anderson in an email earlier this week. I hope a few people will be there to > share how they make this work from their favorite email program. I haven't > been entirely successful with Kmail, but I'll share just the same. I've only received a few PGP keys, but there's still time left to get your key created and submitted for Thursday's keysigning party! Thursday night you'll need: 3.2 What participants should bring to the party 1. Themselves - you cannot participate virtually 2. Two forms of positive picture ID - a driver's license and passport are good 3. Key ID, Key Type, Hex Fingerprint and Key Size info (NOTE: please print out your own copy of your key to compare against my copy when you arrive.) 4. A Pen/Pencil 3.3 What Participants Should Not Bring to the Party 1. A Computer

April 21, 2004

Reminder: WLUG Meeting

by Andy Stewart

HI everybody, This is a reminder about the upcoming WLUG meeting, to be held on Thursday, April 22, at 7:00 PM at the usual place (the Access Grid room at WPI). At this meeting, we'll be having a PGP keysigning party, as described by Chuck Anderson in an email earlier this week. I hope a few people will be there to share how they make this work from their favorite email program. I haven't been entirely successful with Kmail, but I'll share just the same. Even if you don't have a PGP key, come over anyway to learn about this technology and to chat with others. I'd also be happy to relate to you the results of the "Introduction to Linux" class which I've recently finished teaching for the Chelmsford Community Education program. I'll be teaching this class again in September, and we're currently planning a much more advanced class. Also, bring along your ideas for future meetings! Afterwards, we'll venture out for pizza and beer at the newly renovated Boynton Restaurant - you won't recognize the place! See ya later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

April 20, 2004

Re: [Wlug] Linux From Scratch??

by Keith Wright

> From: Ken Jones <kjones(a)ziplink.net> > > Have any us tried to build a Linux From Scratch? I bought the book. I was disappointed in it. Its general form was: download all this stuff, type this, type this, now type this. There was not much discussion of why. > How did it go? A few minutes of excitement that I had a new book. A couple hours of paging through the book with growing disappointment at how little could be learned by reading it. Probably you could learn more by actually doing it, and more importantly, by reading the documentation and code of the various packages as you build them. I began to think that I should go through the process in order to write a couple of chapters that would explain the overall plan, but maybe somebody else is already doing that. In any case it's not my high priority project. So the book sits quietly on my shelf. > Does anyone know of a college level course which uses this as part > of its lab.? No, I don't. I don't think such a lab would be worth much unless the professor had something specific to demonstrate by assigning a problem to make some changes, e.g. run on special hardware, boot into a special purpose program. Even then, there would probably be a better way to make the point than to build everything from scratch. There's not a lot to be learned by spending days watching compiler output scroll past. -- Keith

April 19, 2004

Re: [Wlug] Linux From Scratch??

by gboyce＠badbelly.com

On Mon, 19 Apr 2004, Karl Hiramoto wrote: > just for kicks, try putting a "hello world" program in /sbin/init > sometime. make sure you have a backup & boot disk/CD though. Most bootloaders allow you to append to the kernel commandline (at least grub and lilo both do). You could run your test by doing "init=/sbin/myinit", or safe a backup copy of /sbin/init as /sbin/init.real, and booting with "init=/sbin/init.real" to recover. Of course, backups and boot disks are always a good idea.

April 19, 2004

Re: [Wlug] Linux From Scratch??

by Karl Hiramoto

Yes, I did it as some research into an embedded linux system. I setup the kernel and used busybox for base system. I also messed around with making my own /sbin/init for the embedded system that was only to have one process running. just for kicks, try putting a "hello world" program in /sbin/init sometime. make sure you have a backup & boot disk/CD though. > Have any us tried to build a Linux From Scratch? > > <http://lfs.oregonstate.edu/lfs/news.html> > > How did it go? Is there a thread on the subject? Does anyone know of a > college level course which uses this as part of its lab.? > > Ken Jones > Fitchburg, MA > > > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- Karl Hiramoto <karl(a)hiramoto.org> Work: 978-425-2090 ext 25 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.org/ AOL IM ID = KarlH420 Yahoo_IM = karl_hiramoto

April 19, 2004

RE: [Wlug] Linux From Scratch??

by Skip Gaede

Ken, I used the modules and instructions on the web site back in the 2.x - 3.x days. In the process of building all the modules, you learn a lot. I even built a Linux distro that ran on a PPC Macintosh. There's also a couple of additional projects: ALFS (automated LFS) and BLFS (Beyond LFS) that cover modules you might need after getting the base system working. Good luck, Skip -----Original Message----- From: wlug-bounces(a)mail.wlug.org [mailto:wlug-bounces@mail.wlug.org]On Behalf Of Ken Jones Sent: Saturday, April 17, 2004 9:38 AM To: wlug(a)mail.wlug.org Cc: kjones(a)ziplink.net Subject: [Wlug] Linux From Scratch?? Have any us tried to build a Linux From Scratch? <http://lfs.oregonstate.edu/lfs/news.html> How did it go? Is there a thread on the subject? Does anyone know of a college level course which uses this as part of its lab.? Ken Jones Fitchburg, MA _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

April 19, 2004

Re: [Wlug] Signed e-mails and Kmail

by Charles R. Anderson

On Sat, Apr 17, 2004 at 11:26:56PM -0400, Andy Stewart wrote: > >From the KGpgCertManager, I get an error indicating that the symbol > "initialize" was not found in libkdenetwork.so.2. Missing symbols usually indicate that the program wasn't compiled against the correct versions of your system libraries, or was compiled with different features enabled, etc. Perhaps your KMail can't use that libgpgme.so? Is there any other .so on your system that may work in place of that one? If both components (KDE Network and libgpgme.so) are stock from the distribution version SuSE 9.0, I would file a bug report with SuSE about it. If either component isn't stock, or is from a different version of SuSE than the other, then they will probably tell you it is unsupported. If you want to try to fix this yourself, you can try recompiling either component. It is probably easiest to try libgpgme.so first. rpm -qif <path-to-libgpgme.so> Download the Source RPM: shown in the output of that command and type: rpmbuild --rebuild foo.src.rpm During compilation, any errors about missing symbols should show up, or there may be "configure" output that says something about enabling/disabling certain features due to missing support in other parts of your system. Note that you may need to install several other development packages in order to compile that package, such as kdenetwork-devel or whatever SuSE's equivalent is.

April 18, 2004

Re: [Wlug] Signed e-mails and Kmail

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 17 April 2004 11:56 pm, Mike Frysinger wrote: > On Saturday 17 April 2004 11:26 pm, Andy Stewart wrote: > > I'm playing around with digital signatures in e-mail, and I have that > > working on Kmail (KDE) wnen I send the e-mail. However, when I receive a > > signed e-mail, Kmail isn't able to automatically check the validity of > > the signature (unless I sent it). > > use gpg-agent and add this to your ~/.gnupg/gpg.conf file: > keyserver x-hkp://pgp.mit.edu > keyserver-options auto-key-retrieve > > then kmail should be able to auto verify keys > -mike Hi Mike, I am using gpg-agent. I added the lines recommended by you, but I still get the same error about symbol "initialize" in kdenetwork3.so. I did restart the gpg-agent daemon. Here's my gpg.conf file in case I've made some silly mistake (attached). Thanks, Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAghL6Hl0iXDssISsRAq/gAJsGvCGCfvHupumqfqVmlWLwvPvu4gCdH+pR QL87RjPyNi3Mz4zJvt34yCw= =vIEn -----END PGP SIGNATURE-----

April 18, 2004