- WLUG - wlug.mailman3.com

Signed e-mails and Kmail

by Andy Stewart

Hi all, 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). Within Kmail, I click on Settings->Configure Kmail->Security and point to libgpgme.so in the Crypto Plugins tab. I select that plugin and activate it. I then click the "configure" button and try to start the certificate manager. >From the KGpgCertManager, I get an error indicating that the symbol "initialize" was not found in libkdenetwork.so.2. I'm running SuSE 9.0 Pro, Kmail 1.5.4, and KDE 3.1.4. I've scoured the net to no avail. Does anybody have this working in Kmail? Thanks, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

April 18, 2004

Linux From Scratch??

by Ken Jones

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

April 17, 2004

Next meeting - PGP Keysigning?

by Charles R. Anderson

Ok, I'm not sure if this will fill the meeting's entire timeslot, so feel free to come up with another discussion topic. If you want to participate in the PGP Keysigning Party, here's what you need to do. This is based on GPG Keysigning Party HOWTO (http://www.cryptnet.net/fdp/crypto/gpg-party.html) which I highly recommend you read if this is the first time you are using GPG. You'll need to do these ahead of time *before* you arrive at the meeting, preferrably on a secure, local terminal (i.e. not in a computer lab or the public library or remotely from another system, or on a system running an insecure OS). 1. Generate A Key Pair gpg --gen-key (Default values are good. I would use 2048-bit key.) 1.5 Generate a revocation certificate gpg --output revoke.asc --gen-revoke <keyid> (save this revocation certificate offline in multiple places, print it out, put it in your safe, etc.) 2. Send Public Key To Designated (pgp.mit.edu) Keyserver gpg --send-key --keyserver=pgp.mit.edu <keyid> 3. Send Public Key Info To Coordinator Please email me (cra(a)wpi.edu) the output of: gpg --fingerprint <keyid> 4. Print a paper copy of your Public Key info from Step #3 I'll collate the keys and prepare copies of the public keys for all participants to use as a check list. Example output from Step #3: pub 1024D/49BB5886 2001-04-11 Charles R. Anderson <cra(a)wpi.edu> Key fingerprint = EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 sub 2048g/B0817A13 2001-04-11 In this case, my <keyid> is 49BB5886, which is the same as the last 8 hex digits of the fingerprint. You can use your email address as <keyid> in the command if you forget your actual key id. So my full key information is: Key ID: 49BB5886 Key Type: DSA Hex Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886 Key Size: 1024 bits (The DSA key is always 1024 bits. The ElGamal Encryption key is 2048 bits in my case, but isn't needed for the keysigning party.) 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 17, 2004

Re: [Wlug] How Barbaric!

by Chris Aniszczyk

> 2.6.4! 2.6.5 came out, like almost a whole 9 days ago! Let's see these > priorities right already and upgrade this archaic, elder kernel already! I don't know about you, but I like living on the bleeding edge ;) Cheers, -- Chris Aniszczyk Gentoo Developer - http://www.gentoo.org - http://cia.navi.cx/stats/author/zx http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x274A275F

April 14, 2004

How Barbaric!

by sageman＠WPI.EDU

--- "Hello, I'm running gentoo with 2.6.4 kernel" 2.6.4! 2.6.5 came out, like almost a whole 9 days ago! Let's see these priorities right already and upgrade this archaic, elder kernel already! Yeah, that's definitely sleep-inside-spinlock checks though. Just run your favorite kernel configurator (make config, or make xconfig or something), and under "Kernel Hacking" uncheck the "sleep-inside-spinlock checking" box. Hope it helps ^_^ http://sageman.res.wpi.net

April 14, 2004

Re: [Wlug] Nvidia and 2.6.4

by Mike Frysinger

On Tuesday 13 April 2004 12:19 am, orbitz(a)ezabel.com wrote: > # CONFIG_DEBUG_KERNEL is not set > CONFIG_EARLY_PRINTK=y > CONFIG_DEBUG_SPINLOCK_SLEEP=y > # CONFIG_FRAME_POINTER is not set > > Change the SPINLOCK_SLEEP to n? yes, that should make those tracebacks 'disappear' -mike

April 13, 2004

RE: [Wlug] Next meeting - topic?

by Martin, Eric

I'm game -----Original Message----- From: Charles R. Anderson [mailto:cra@WPI.EDU] Sent: Monday, April 12, 2004 5:54 PM To: Worcester Linux Users Group Subject: Re: [Wlug] Next meeting - topic? Who wants to do a PGP Keysigning? It would involve advance preparation from everyone who would like to participate. By now I'd imagine most of you have gotten your feet wet with GnuPG :-) If not, see: http://www.wlug.org/files/pgp-slides/index.html If there is interest, please let me know in the next couple days so I can organize the procedure and send out instructions. _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

April 13, 2004

Re: [Wlug] Nvidia and 2.6.4

by orbitz＠ezabel.com

# CONFIG_DEBUG_KERNEL is not set CONFIG_EARLY_PRINTK=y CONFIG_DEBUG_SPINLOCK_SLEEP=y # CONFIG_FRAME_POINTER is not set Change the SPINLOCK_SLEEP to n? Thanks, Malcolm On Mon, 12 Apr 2004 23:59:51 -0400 Mike Frysinger <vapier(a)gentoo.org> wrote: > On Monday 12 April 2004 11:38 pm, orbitz(a)ezabel.com wrote: > > Hello, I'm running gentoo with 2.6.4 kernel and my /var/log/messages is > > getting filled up with this junk: > > known problem ... turn off sleep checks inside of kernel debug > -mike > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

April 13, 2004

Re: [Wlug] Nvidia and 2.6.4

by Mike Frysinger

On Monday 12 April 2004 11:38 pm, orbitz(a)ezabel.com wrote: > Hello, I'm running gentoo with 2.6.4 kernel and my /var/log/messages is > getting filled up with this junk: known problem ... turn off sleep checks inside of kernel debug -mike

April 13, 2004

Nvidia and 2.6.4

by orbitz＠ezabel.com

Hello, I'm running gentoo with 2.6.4 kernel and my /var/log/messages is getting filled up with this junk: Apr 12 23:16:47 sentinel Debug: sleeping function called from invalid context at mm/slab.c:1900 Apr 12 23:16:47 sentinel in_atomic():1, irqs_disabled():0 Apr 12 23:16:47 sentinel Call Trace: Apr 12 23:16:47 sentinel [<c011a1ab>] __might_sleep+0xab/0xd0 Apr 12 23:16:47 sentinel [<c013d0a6>] __kmalloc+0x96/0xa0 Apr 12 23:16:47 sentinel [<e0b7db39>] os_alloc_mem+0x5c/0x87 [nvidia] Apr 12 23:16:47 sentinel [<e0b97df0>] _nv001308rm+0x10/0x28 [nvidia] Apr 12 23:16:47 sentinel [<e0cb058d>] _nv001518rm+0x7c9/0xb34 [nvidia] Apr 12 23:16:47 sentinel [<c0109588>] common_interrupt+0x18/0x20 Apr 12 23:16:47 sentinel [<e0c34d61>] _nv002465rm+0x81/0x420 [nvidia] Apr 12 23:16:47 sentinel [<e0c34d78>] _nv002465rm+0x98/0x420 [nvidia] Apr 12 23:16:47 sentinel [<e0b8d965>] _nv001338rm+0x1d/0x24 [nvidia] Apr 12 23:16:47 sentinel [<e0b7e555>] _nv005601rm+0xd/0x34 [nvidia] Apr 12 23:16:47 sentinel [<e0b85c38>] _nv000858rm+0x300/0xe14 [nvidia] Apr 12 23:16:47 sentinel [<c0124bca>] run_timer_softirq+0x10a/0x1b0 Apr 12 23:16:47 sentinel [<c0124d5f>] do_timer+0xdf/0xf0 Apr 12 23:16:47 sentinel [<c010b16d>] do_IRQ+0xfd/0x130 Apr 12 23:16:47 sentinel [<c0109588>] common_interrupt+0x18/0x20 Apr 12 23:16:47 sentinel [<e0b81eed>] _nv002962rm+0x2c5/0x3b8 [nvidia] Apr 12 23:16:47 sentinel [<e0b9c8a9>] _nv000899rm+0x4c9/0xf70 [nvidia] Apr 12 23:16:47 sentinel [<e0b9c8bc>] _nv000899rm+0x4dc/0xf70 [nvidia] Apr 12 23:16:47 sentinel [<e0ba2df9>] _nv004363rm+0x59/0x90 [nvidia] Apr 12 23:16:47 sentinel [<e0bc05ea>] _nv005046rm+0x52/0x70 [nvidia] Apr 12 23:16:47 sentinel [<e0ba2d02>] _nv004679rm+0x1be/0x1d0 [nvidia] Apr 12 23:16:47 sentinel [<c0117fba>] wake_up_state+0x1a/0x20 Apr 12 23:16:47 sentinel [<c0126c31>] send_group_sig_info+0x31/0x60 Apr 12 23:16:47 sentinel [<c016380b>] send_sigio_to_task+0xeb/0x100 Apr 12 23:16:47 sentinel [<e0b8d7fe>] _nv001344rm+0x46/0x6c [nvidia] Apr 12 23:16:47 sentinel [<e0cb545a>] _nv001480rm+0x3a/0x7c [nvidia] Apr 12 23:16:47 sentinel [<c0163872>] send_sigio+0x52/0xf0 Apr 12 23:16:47 sentinel [<c0267b78>] get_device+0x18/0x30 Apr 12 23:16:47 sentinel [<c02ce9c7>] uhci_submit_common+0x1f7/0x2b0 Apr 12 23:16:47 sentinel [<c0117fba>] wake_up_state+0x1a/0x20 Apr 12 23:16:47 sentinel [<c0126c31>] send_group_sig_info+0x31/0x60 Apr 12 23:16:47 sentinel [<e0cf912f>] _nv000176rm+0x57/0x3ec [nvidia] Apr 12 23:16:47 sentinel [<c018c9ac>] ext3_get_block_handle+0xac/0x360 Apr 12 23:16:47 sentinel [<c0138535>] mempool_alloc+0x75/0x160 Apr 12 23:16:47 sentinel [<c011a5e0>] autoremove_wake_function+0x0/0x50 Apr 12 23:16:47 sentinel [<c0138535>] mempool_alloc+0x75/0x160 Apr 12 23:16:47 sentinel [<e0b8d965>] _nv001338rm+0x1d/0x24 [nvidia] Apr 12 23:16:47 sentinel [<e0bb2eac>] _nv005307rm+0x54/0x544 [nvidia] Apr 12 23:16:47 sentinel [<e0c6369b>] _nv001532rm+0x1f/0x28 [nvidia] Apr 12 23:16:47 sentinel [<e0c6364c>] _nv001534rm+0x20/0x28 [nvidia] Apr 12 23:16:47 sentinel [<e0c63e42>] _nv003621rm+0x1a/0x20 [nvidia] Apr 12 23:16:47 sentinel [<e0cfa708>] _nv000183rm+0x750/0x774 [nvidia] Apr 12 23:16:47 sentinel [<e0c6369b>] _nv001532rm+0x1f/0x28 [nvidia] Apr 12 23:16:47 sentinel [<e0c63e81>] _nv003619rm+0x19/0x20 [nvidia] Apr 12 23:16:47 sentinel [<e0cb29f3>] _nv003073rm+0x1b/0x30 [nvidia] Apr 12 23:16:47 sentinel [<e0cf912f>] _nv000176rm+0x57/0x3ec [nvidia] Apr 12 23:16:47 sentinel [<e0b8d7da>] _nv001344rm+0x22/0x6c [nvidia] Apr 12 23:16:47 sentinel [<e0c637db>] _nv001556rm+0x5b/0x6c [nvidia] Apr 12 23:16:47 sentinel [<e0b8d7da>] _nv001344rm+0x22/0x6c [nvidia] Apr 12 23:16:47 sentinel [<e0c637db>] _nv001556rm+0x5b/0x6c [nvidia] Apr 12 23:16:47 sentinel [<e0b8d7da>] _nv001344rm+0x22/0x6c [nvidia] Apr 12 23:16:47 sentinel [<e0c637db>] _nv001556rm+0x5b/0x6c [nvidia] Apr 12 23:16:47 sentinel [<e0c637db>] _nv001556rm+0x5b/0x6c [nvidia] Apr 12 23:16:47 sentinel [<e0c637db>] _nv001556rm+0x5b/0x6c [nvidia] Apr 12 23:16:47 sentinel [<c0117d1e>] recalc_task_prio+0x8e/0x1b0 Apr 12 23:16:47 sentinel [<e0cf912f>] _nv000176rm+0x57/0x3ec [nvidia] Apr 12 23:16:47 sentinel [<c03337f4>] kfree_skbmem+0x24/0x30 Apr 12 23:16:47 sentinel [<c033385a>] __kfree_skb+0x5a/0xc0 Apr 12 23:16:47 sentinel [<c032fc78>] sock_aio_read+0xb8/0xd0 Apr 12 23:16:47 sentinel [<c015142b>] do_sync_read+0x8b/0xc0 Apr 12 23:16:47 sentinel [<e0b9bfb1>] rm_ioctl+0x19/0x20 [nvidia] Apr 12 23:16:47 sentinel [<e0b7ba08>] nv_kern_ioctl+0x4de/0x529 [nvidia] Apr 12 23:16:47 sentinel [<e0b9a901>] _nv000865rm+0x3d/0x48 [nvidia] Apr 12 23:16:47 sentinel [<e0b7ba78>] nv_kern_isr+0x25/0x5c [nvidia] Apr 12 23:16:47 sentinel [<c0151550>] vfs_read+0xf0/0x130 Apr 12 23:16:47 sentinel [<c0163f13>] sys_ioctl+0xf3/0x2a0 Apr 12 23:16:47 sentinel [<c010941b>] syscall_call+0x7/0xb It seems pretty nvidia related, and I had this rpoblem before, but updating my kernel seems to have brought it back. Does anyone have any idea how to fix this? I suppose if worst comes to worst I can try to revert back to 2.6.2 or 3. Thanks, Malcolm

April 13, 2004