From rick at linuxmafia.com Tue Aug 1 03:10:19 2006 From: rick at linuxmafia.com (Rick Moen) Date: Tue, 1 Aug 2006 03:10:19 -0700 Subject: [cAos] qmail and postfix In-Reply-To: <9F0C455F-6E01-439A-93FE-A7ED434DA1A3@runlevelzero.net> References: <4E755A27-92F1-4196-98D5-AB04870E954A@runlevelzero.net> <20060731224649.GD31132@kainx.org> <9F0C455F-6E01-439A-93FE-A7ED434DA1A3@runlevelzero.net> Message-ID: <20060801101018.GE16338@linuxmafia.com> Quoting Greg Kurtzer (gmk at runlevelzero.net): > Here are some of my reasons why postfix was put back instead of qmail: > > 1. According to my understanding of the license, we needed to get > approval from DJB. I am not a lawyer and I was not about to take the > risk of license violation without a clear written explanation about > what we are allowed to do. Since I can't afford a lawyer, I wanted to > get authorization from the author. As long as your (plural) qmail RPM or other package installs qmail exactly the way Dan wants it, e.g., with everything inside a Dan-blessed /var/qmail hierarchy, _and_ the results are basically indistinguishable from compiling and installing _unpatched_, pristine qmail-1.03.tar.gz (or earlier), then your binary package is already licensed in advance. There is no blanket permission, however, for binary patches based on patched qmail: You'd have to secure separate permission for _that_ (and it's unlikely). (I would strongly discourage using unpatched qmail 1.03, from either source or binary packages. _Patched_ qmail is respectable but, from professional experience admin'ing it at $FIRM, just not my cuppa.) Oh, reminds me: Speaking of dear old $FIRM and qmail's role there, see "Signatures" on http://linuxmafia.com/kb/Linux_PR/ . Names have been omitted to protect the guilty. -- Cheers, There are 10 kinds of people in the world, those who Rick Moen know ternary, those who don't, and those who are now rick at linuxmafia.com looking for their dictionaries. -- Ron Fabre From rick at linuxmafia.com Tue Aug 1 03:13:44 2006 From: rick at linuxmafia.com (Rick Moen) Date: Tue, 1 Aug 2006 03:13:44 -0700 Subject: [cAos] qmail and postfix In-Reply-To: <20060801101018.GE16338@linuxmafia.com> References: <4E755A27-92F1-4196-98D5-AB04870E954A@runlevelzero.net> <20060731224649.GD31132@kainx.org> <9F0C455F-6E01-439A-93FE-A7ED434DA1A3@runlevelzero.net> <20060801101018.GE16338@linuxmafia.com> Message-ID: <20060801101344.GA14981@linuxmafia.com> I wrote: > There is no blanket permission, however, for binary patches based on > patched qmail: ^^^^^^^ "packages". (It's late; I'm tired.) From gmk at runlevelzero.net Sun Aug 6 22:00:51 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Sun, 6 Aug 2006 22:00:51 -0700 Subject: [cAos] caos2 repository update Message-ID: Major update to cAos-2 including security updates. Any bugs or problems should be reported immediately. current: + SRPMS/dansguardian-2.9.7.2-1.caos.src.rpm + SRPMS/dvdisaster-0.70.1-1.caos.src.rpm + SRPMS/firefox-1.5.0.5-1.caos.src.rpm + SRPMS/fluxbox-1.0rc2-1.caos.src.rpm + SRPMS/gftp-2.0.18-2.caos.src.rpm + SRPMS/gnupg-1.4.5-1.caos.src.rpm + SRPMS/helpme-0.20020910-1.caos.src.rpm + SRPMS/horde-3.1.2-1.caos.src.rpm + SRPMS/httpd-2.0.59-1.caos.src.rpm + SRPMS/hylafax-4.3.0.5-1.src.rpm + SRPMS/lftp-3.5.2-1.caos.src.rpm + SRPMS/libtiff-3.8.2-2.caos.src.rpm + SRPMS/linux-2.6.17.7-99.caos.src.rpm + SRPMS/MySQL-4.1.21-1.caos.src.rpm + SRPMS/nagios-2.5-1.caos.src.rpm + SRPMS/openssh-4.3p2-2.caos.src.rpm + SRPMS/perl-Archive-Tar-1.29-1.caos.src.rpm + SRPMS/perl-Archive-Zip-1.16-1.caos.src.rpm + SRPMS/perl-Authen-NTLM-0.31-1.caos.src.rpm + SRPMS/perl-BerkeleyDB-0.28-1.caos.src.rpm + SRPMS/perl-Business-ISBN-1.82-1.caos.src.rpm + SRPMS/perl-Class-Loader-2.03-1.caos.src.rpm + SRPMS/perl-Class-MethodMaker-2.08-1.caos.src.rpm + SRPMS/perl-Compress-Zlib-1.41-1.caos.src.rpm + SRPMS/perl-Crypt-SmbHash-0.12-1.caos.src.rpm + SRPMS/perl-Curses-1.14-1.caos.src.rpm + SRPMS/perl-DBI-1.51-1.caos.src.rpm + SRPMS/perl-Digest-SHA1-2.11-1.caos.src.rpm + SRPMS/perl-Expect-1.17-1.caos.src.rpm + SRPMS/perl-ExtUtils-Depends-0.205-1.caos.src.rpm + SRPMS/perl-ExtUtils-PkgConfig-1.07-1.caos.src.rpm + SRPMS/perl-File-Copy-Link-0.080-1.caos.src.rpm + SRPMS/perl-HTML-Parser-3.54-1.caos.src.rpm + SRPMS/perl-HTML-Tagset-3.10-1.caos.src.rpm + SRPMS/perl-HTML-Tree-3.20-1.caos.src.rpm + SRPMS/perl-IO-Socket-Multicast-1.04-1.caos.src.rpm + SRPMS/perl-IO-Socket-SSL-0.97-1.caos.src.rpm + SRPMS/perl-IO-String-1.08-1.caos.src.rpm + SRPMS/perl-IO-Tty-1.05-1.caos.src.rpm + SRPMS/perl-Jcode-2.06-1.caos.src.rpm + SRPMS/perl-libwww-perl-5.805-2.caos.src.rpm + SRPMS/perl-MailTools-1.74-1.caos.src.rpm + SRPMS/perl-MIME-Lite-3.01-1.caos.src.rpm + SRPMS/perl-MIME-tools-5.420-1.caos.src.rpm + SRPMS/perl-Net-DNS-0.57-1.caos.src.rpm + SRPMS/perl-Net-Server-0.93-1.caos.src.rpm + SRPMS/perl-Net-Whois-IP-1.01-1.caos.src.rpm + SRPMS/perl-NTLM-1.02-1.caos.src.rpm + SRPMS/perl-Parse-RecDescent-1.94-1.caos.src.rpm + SRPMS/perl-String-CRC32-1.4-1.caos.src.rpm + SRPMS/perl-SVG-2.33-1.caos.src.rpm + SRPMS/perl-Term-Screen-1.03-1.caos.src.rpm + SRPMS/perl-Test-Manifest-1.14-1.caos.src.rpm + SRPMS/perl-Time-HiRes-1.87-1.caos.src.rpm + SRPMS/perl-Unicode-Map-0.112-1.caos.src.rpm + SRPMS/perl-Unicode-Map8-0.12-1.caos.src.rpm + SRPMS/perl-Unicode-MapUTF8-1.11-1.caos.src.rpm + SRPMS/perl-Unicode-String-2.09-1.caos.src.rpm + SRPMS/php5-5.1.4-2.caos.src.rpm + SRPMS/postfix-2.3.2-2.caos.src.rpm + SRPMS/samba-3.0.23a-1.caos.src.rpm + SRPMS/squirrelmail-1.4.7-1.caos.src.rpm + SRPMS/thunderbird-1.5.0.5-1.caos.src.rpm + SRPMS/vixie-cron-4.1-45.caos.src.rpm + SRPMS/wireshark-0.99.2-1.caos.src.rpm + SRPMS/xmms-plugin-crossfade-0.3.11-1.caos.src.rpm + SRPMS/zsh-4.3.2-1.caos.src.rpm - SRPMS/firefox-1.5.0.4-1.caos.src.rpm - SRPMS/gnupg-1.4.2-1.caos.src.rpm - SRPMS/gnupg-1.4.3-1.caos.src.rpm - SRPMS/httpd-2.0.55-11.src.rpm - SRPMS/lftp-3.1.3-1.src.rpm - SRPMS/lftp-3.2.1-1.src.rpm - SRPMS/lftp-3.3.3-1.src.rpm - SRPMS/lftp-3.3.5-1.src.rpm - SRPMS/lftp-3.4.2-1.src.rpm - SRPMS/lftp-3.4.4-1.src.rpm - SRPMS/libtiff-3.5.7-18.caos.src.rpm - SRPMS/linux-2.6.11.11-70.caos.src.rpm - SRPMS/linux-2.6.11.12-72.caos.src.rpm - SRPMS/linux-2.6.11.6-61.caos.src.rpm - SRPMS/linux-2.6.12.2-75.caos.src.rpm - SRPMS/linux-2.6.12.3-76.caos.src.rpm - SRPMS/linux-2.6.14.2-95.caos.src.rpm - SRPMS/MySQL-4.1.15-3.src.rpm - SRPMS/MySQL-4.1.20-1.caos.src.rpm - SRPMS/php5-5.1.2-7.caos.src.rpm - SRPMS/postfix-2.2.10-2.caos.src.rpm - SRPMS/samba-3.0.9-2.caos.src.rpm - SRPMS/thunderbird-1.0-2.src.rpm - SRPMS/thunderbird-1.0.2-5.src.rpm - SRPMS/thunderbird-1.0.6-5.src.rpm - SRPMS/vixie-cron-4.1-33.src.rpm stable: + SRPMS/firefox-1.5.0.5-1.caos.src.rpm + SRPMS/fluxbox-1.0rc2-1.caos.src.rpm + SRPMS/gftp-2.0.18-2.caos.src.rpm + SRPMS/gnupg-1.4.5-1.caos.src.rpm + SRPMS/helpme-0.20020910-1.caos.src.rpm + SRPMS/httpd-2.0.59-1.caos.src.rpm + SRPMS/hylafax-4.3.0.5-1.src.rpm + SRPMS/lftp-3.5.2-1.caos.src.rpm + SRPMS/libtiff-3.8.2-2.caos.src.rpm + SRPMS/linux-2.6.17.7-99.caos.src.rpm + SRPMS/MySQL-4.1.21-1.caos.src.rpm + SRPMS/perl-Authen-NTLM-0.31-1.caos.src.rpm + SRPMS/perl-Crypt-SmbHash-0.12-1.caos.src.rpm + SRPMS/perl-Jcode-2.06-1.caos.src.rpm + SRPMS/perl-NTLM-1.02-1.caos.src.rpm + SRPMS/perl-Unicode-Map-0.112-1.caos.src.rpm + SRPMS/perl-Unicode-Map8-0.12-1.caos.src.rpm + SRPMS/perl-Unicode-MapUTF8-1.11-1.caos.src.rpm + SRPMS/perl-Unicode-String-2.09-1.caos.src.rpm + SRPMS/php5-5.1.4-2.caos.src.rpm + SRPMS/postfix-2.3.2-2.caos.src.rpm + SRPMS/samba-3.0.23a-1.caos.src.rpm + SRPMS/thunderbird-1.5.0.5-1.caos.src.rpm + SRPMS/vixie-cron-4.1-45.caos.src.rpm + SRPMS/wireshark-0.99.2-1.caos.src.rpm + SRPMS/zsh-4.3.2-1.caos.src.rpm - SRPMS/firefox-1.5.0.4-1.caos.src.rpm - SRPMS/gnupg-1.4.2-1.caos.src.rpm - SRPMS/httpd-2.0.55-11.src.rpm - SRPMS/lftp-3.1.3-1.src.rpm - SRPMS/libtiff-3.5.7-18.caos.src.rpm - SRPMS/linux-2.6.11.6-61.caos.src.rpm - SRPMS/MySQL-4.1.15-3.src.rpm - SRPMS/php5-5.1.2-7.caos.src.rpm - SRPMS/postfix-2.2.10-2.caos.src.rpm - SRPMS/samba-3.0.9-2.caos.src.rpm - SRPMS/thunderbird-1.0-2.src.rpm - SRPMS/vixie-cron-4.1-33.src.rpm -- Greg Kurtzer gmk at runlevelzero.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20060806/0944616f/attachment.html From gmk at runlevelzero.net Mon Aug 7 08:58:52 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Mon, 7 Aug 2006 08:58:52 -0700 Subject: [cAos] caos-3 alphas posted Message-ID: <596FCB95-B6A0-4B51-B5E4-78158260B17B@runlevelzero.net> I have some alpha versions of caos-3 posted. I am looking for testers and people wanting to package and maintain ports to take a look at the caos-ports system (which will mostly be used for high performance computing packages). Otherwise, caos-3 is a very capable server operating system with a very strong emphasis on security and efficiency. For example using sidekick, it is possible to setup a running email, httpd, firewall, and NAT'ing system in about 1 minute. cAos-3 uses all of the known command line standards as what people have come to love from caos, but it also contains an entirely new system initialization subsystem that replaces the older style initscripts. This was to promote a safer, more efficient boot/shutdown while remaining backwards compatible with the RH style initscripts subsystem and command line interface. The caos-ports system can be utilized as simply as: # cd /usr/src/cports/programs # cd openmpi/[version] # make install # make clean # export COMPILERS=pathscale # make install # make clean # export COMPILERS=pgi # make install This will build 3 different versions of openmpi and make them all available to the enviornment modules architecture so users can then just type: 'module load openmpi/[version]-gcc' or subsitute gcc for whatever compiler suite that it was built with. And lastly caos-3 also has the new "Perceus" cluster management solution built in (the next generation of Warewulf). Please feel free to test drive the new caos-3 OS and download the ISO from: http://caos.caosity.org/testing/caos-3.0-0.alpha3.i386.iso Be aware that this is designed to be a server oriented system, and servers aren't dual boot. Thus this installer will non-interactively wipe out your entire disk when you type the "install" command. -- Greg Kurtzer gmk at runlevelzero.net From mej at caosity.org Mon Aug 7 13:27:09 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 7 Aug 2006 16:27:09 -0400 Subject: [cAos] Webmin/Usermin Vulnerability Message-ID: <20060807202708.GA9761@kainx.org> Though we don't have an official caos package for webmin or usermin, I know there's a package in users/aedinsf/ and that a lot of people use these tools. If you're one of those people, please note the following: http://www.kb.cert.org/vuls/id/999601 If AedinSF (or any other packager) would like to update, please do. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Even if it takes forever to win your heart and your love and your devotion, I know it's going to be worth the wait." -- Amy Grant, "Say You'll Be Mine" From benjamin at py-soft.co.uk Mon Aug 7 14:33:17 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 07 Aug 2006 22:33:17 +0100 Subject: [cAos] qmail and postfix In-Reply-To: <4E755A27-92F1-4196-98D5-AB04870E954A@runlevelzero.net> References: <4E755A27-92F1-4196-98D5-AB04870E954A@runlevelzero.net> Message-ID: <44D7B19D.7020808@py-soft.co.uk> Greg Kurtzer wrote: > I have decided to package Postfix as the default MTA. Does this one support TLS and saslauth? Ben From gmk at runlevelzero.net Mon Aug 7 14:49:41 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Mon, 7 Aug 2006 14:49:41 -0700 Subject: [cAos] qmail and postfix In-Reply-To: References: <4E755A27-92F1-4196-98D5-AB04870E954A@runlevelzero.net> <44D7B19D.7020808@py-soft.co.uk> Message-ID: <6BBC9725-ECE2-4C8C-8024-65E742F241E5@runlevelzero.net> TLS is there, but not enabled by default in the config file (this is a future feature to have a sidekick option to enable/disable this). I didn't build against SASL2 yet as it is still dependent on the cyrus-sasl package which has not been imported yet. It is on the TODO list though. ;) On Aug 7, 2006, at 2:48 PM, Greg Kurtzer wrote: > TLS is there, but not enabled by default in the config file (this > is a future feature to have a sidekick option to enable/disable this). > > I didn't build against SASL2 yet as it is still dependent on the > cyrus-sasl package which has not been imported yet. It is on the > TODO list though. ;) > -- Greg Kurtzer gmk at runlevelzero.net From gmk at runlevelzero.net Wed Aug 9 08:25:37 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Wed, 9 Aug 2006 08:25:37 -0700 Subject: [cAos] caos2 repository update Message-ID: <73592D50-0A1B-4414-8117-99504E1FF117@runlevelzero.net> current: + SRPMS/Autodia-2.03-1.caos.src.rpm + SRPMS/clamav-0.88.3-2.caos.src.rpm + SRPMS/dhcp-3.0.4-1.caos.src.rpm + SRPMS/qemu-0.8.2-1.caos.src.rpm - SRPMS/dhcp-3.0.1-13.caos.src.rpm - SRPMS/dhcp-3.0.3-14.caos.src.rpm stable: + SRPMS/Autodia-2.03-1.caos.src.rpm + SRPMS/dhcp-3.0.4-1.caos.src.rpm - SRPMS/dhcp-3.0.1-13.caos.src.rpm -- Greg Kurtzer gmk at runlevelzero.net From baucom at msg.ucsf.edu Wed Aug 9 14:15:56 2006 From: baucom at msg.ucsf.edu (Albion Baucom) Date: Wed, 9 Aug 2006 14:15:56 -0700 Subject: [cAos] New Kernel + nVidia In-Reply-To: <73592D50-0A1B-4414-8117-99504E1FF117@runlevelzero.net> References: <73592D50-0A1B-4414-8117-99504E1FF117@runlevelzero.net> Message-ID: <1ED0B5A5-AC1B-4037-9E10-7EE718E83985@msg.ucsf.edu> I just updated to the new kernel (inux-2.6.17.7-99) and tried to install the newest nVidia driver (NVIDIA-Linux-x86-1.0-8762-pkg1.run). The driver build failed because the file /lib/modules/2.6.17.7-99.caos/build/arch/i386/Makefile could not find the file /lib/modules/2.6.17.7-99.caos/build/arch/i386/Makefile.cpu I created an empty file named Makefile.cpu (evidently for adding local compile options), and the driver built fine. The line that fails in the Makefile is 38: #CPU-specific tuning. Anything which can be shared with UML should go here. include $(srctree)/arch/i386/Makefile.cpu Makefile.cpu is evidently not included by default. Just thought this might be of use for future users who might encounter this build error. Or maybe I did something wrong? Albion From mej at caosity.org Wed Aug 9 16:31:29 2006 From: mej at caosity.org (Michael Jennings) Date: Wed, 9 Aug 2006 19:31:29 -0400 Subject: [cAos] New Kernel + nVidia In-Reply-To: <1ED0B5A5-AC1B-4037-9E10-7EE718E83985@msg.ucsf.edu> References: <73592D50-0A1B-4414-8117-99504E1FF117@runlevelzero.net> <1ED0B5A5-AC1B-4037-9E10-7EE718E83985@msg.ucsf.edu> Message-ID: <20060809233129.GS31225@kainx.org> On Wednesday, 09 August 2006, at 14:15:56 (-0700), Albion Baucom wrote: > I just updated to the new kernel (inux-2.6.17.7-99) and tried to > install the newest nVidia driver > (NVIDIA-Linux-x86-1.0-8762-pkg1.run). > > The driver build failed because the file > > /lib/modules/2.6.17.7-99.caos/build/arch/i386/Makefile > > could not find the file > > /lib/modules/2.6.17.7-99.caos/build/arch/i386/Makefile.cpu This is a known issue. My previous attempt at a fix obviously failed, and I have not yet been able to track down the reason. Looking at the spec file, I can't find the fix I made, so it's possible I never actually checked it in. :-( Please file a bug on our bugtracker (bugs.caosity.org) so I won't forget. :-) Thanks, Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Love, like a road that never ends. How it leads me back again to heartache, I don't understand." -- Peter Cetera and Amy Grant, "Next Time I Fall" From JScoggins at lbl.gov Thu Aug 10 09:53:10 2006 From: JScoggins at lbl.gov (Jackie Scoggins) Date: Thu, 10 Aug 2006 09:53:10 -0700 Subject: [cAos] New Kernel + nVidia In-Reply-To: <1ED0B5A5-AC1B-4037-9E10-7EE718E83985@msg.ucsf.edu> References: <73592D50-0A1B-4414-8117-99504E1FF117@runlevelzero.net> <1ED0B5A5-AC1B-4037-9E10-7EE718E83985@msg.ucsf.edu> Message-ID: Hello, This is not in response to your question. I am curious if I know you or not. Did you ever work for NAS? Jackie ----- Original Message ----- From: Albion Baucom Date: Wednesday, August 9, 2006 2:16 pm Subject: [cAos] New Kernel + nVidia To: Community Assembled OS > I just updated to the new kernel (inux-2.6.17.7-99) and tried to > install the newest nVidia driver (NVIDIA-Linux-x86-1.0-8762-pkg1.run). > > The driver build failed because the file > > /lib/modules/2.6.17.7-99.caos/build/arch/i386/Makefile > > could not find the file > > /lib/modules/2.6.17.7-99.caos/build/arch/i386/Makefile.cpu > > I created an empty file named Makefile.cpu (evidently for adding > local compile options), and the driver built fine. > > The line that fails in the Makefile is 38: > > #CPU-specific tuning. Anything which can be shared with UML should > go > here. > include $(srctree)/arch/i386/Makefile.cpu > > Makefile.cpu is evidently not included by default. > > Just thought this might be of use for future users who might > encounter this build error. Or maybe I did something wrong? > > Albion > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > From iank at mac.com Thu Aug 10 10:56:00 2006 From: iank at mac.com (Ian Kaufman) Date: Thu, 10 Aug 2006 10:56:00 -0700 Subject: [cAos] New Kernel + nVidia Message-ID: <189971.1155232560129.JavaMail.iank@mac.com> Gee Jackie, what's up with that? ;) Ian From martyn at theendofhistether.org.uk Wed Aug 9 04:41:21 2006 From: martyn at theendofhistether.org.uk (Martyn) Date: Wed, 09 Aug 2006 12:41:21 +0100 Subject: [cAos] caos2 repository update In-Reply-To: References: Message-ID: <44D9C9E1.9060707@theendofhistether.org.uk> Hi all/Greg I haven't had a chance to look into this yet, but there does seem to be some kind of issue with vixie-cron. I have an entry like the following : * * * * * /etc/ppp/checknet.sh Which was running perfectly on an older rev, and after a yum update just isn't being called. I'll do some more checking but I'm rushed off my feet at the moment, if anyone could confirm or say it's definitely something local to me, that'd be great. Thanks Martyn Ranyard (Joran) Greg Kurtzer wrote: > Major update to cAos-2 including security updates. Any bugs or > problems should be reported immediately. > > > current: > + SRPMS/dansguardian-2.9.7.2-1.caos.src.rpm > + SRPMS/dvdisaster-0.70.1-1.caos.src.rpm > + SRPMS/firefox-1.5.0.5-1.caos.src.rpm > + SRPMS/fluxbox-1.0rc2-1.caos.src.rpm > + SRPMS/gftp-2.0.18-2.caos.src.rpm > + SRPMS/gnupg-1.4.5-1.caos.src.rpm > + SRPMS/helpme-0.20020910-1.caos.src.rpm > + SRPMS/horde-3.1.2-1.caos.src.rpm > + SRPMS/httpd-2.0.59-1.caos.src.rpm > + SRPMS/hylafax-4.3.0.5-1.src.rpm > + SRPMS/lftp-3.5.2-1.caos.src.rpm > + SRPMS/libtiff-3.8.2-2.caos.src.rpm > + SRPMS/linux-2.6.17.7-99.caos.src.rpm > + SRPMS/MySQL-4.1.21-1.caos.src.rpm > + SRPMS/nagios-2.5-1.caos.src.rpm > + SRPMS/openssh-4.3p2-2.caos.src.rpm > + SRPMS/perl-Archive-Tar-1.29-1.caos.src.rpm > + SRPMS/perl-Archive-Zip-1.16-1.caos.src.rpm > + SRPMS/perl-Authen-NTLM-0.31-1.caos.src.rpm > + SRPMS/perl-BerkeleyDB-0.28-1.caos.src.rpm > + SRPMS/perl-Business-ISBN-1.82-1.caos.src.rpm > + SRPMS/perl-Class-Loader-2.03-1.caos.src.rpm > + SRPMS/perl-Class-MethodMaker-2.08-1.caos.src.rpm > + SRPMS/perl-Compress-Zlib-1.41-1.caos.src.rpm > + SRPMS/perl-Crypt-SmbHash-0.12-1.caos.src.rpm > + SRPMS/perl-Curses-1.14-1.caos.src.rpm > + SRPMS/perl-DBI-1.51-1.caos.src.rpm > + SRPMS/perl-Digest-SHA1-2.11-1.caos.src.rpm > + SRPMS/perl-Expect-1.17-1.caos.src.rpm > + SRPMS/perl-ExtUtils-Depends-0.205-1.caos.src.rpm > + SRPMS/perl-ExtUtils-PkgConfig-1.07-1.caos.src.rpm > + SRPMS/perl-File-Copy-Link-0.080-1.caos.src.rpm > + SRPMS/perl-HTML-Parser-3.54-1.caos.src.rpm > + SRPMS/perl-HTML-Tagset-3.10-1.caos.src.rpm > + SRPMS/perl-HTML-Tree-3.20-1.caos.src.rpm > + SRPMS/perl-IO-Socket-Multicast-1.04-1.caos.src.rpm > + SRPMS/perl-IO-Socket-SSL-0.97-1.caos.src.rpm > + SRPMS/perl-IO-String-1.08-1.caos.src.rpm > + SRPMS/perl-IO-Tty-1.05-1.caos.src.rpm > + SRPMS/perl-Jcode-2.06-1.caos.src.rpm > + SRPMS/perl-libwww-perl-5.805-2.caos.src.rpm > + SRPMS/perl-MailTools-1.74-1.caos.src.rpm > + SRPMS/perl-MIME-Lite-3.01-1.caos.src.rpm > + SRPMS/perl-MIME-tools-5.420-1.caos.src.rpm > + SRPMS/perl-Net-DNS-0.57-1.caos.src.rpm > + SRPMS/perl-Net-Server-0.93-1.caos.src.rpm > + SRPMS/perl-Net-Whois-IP-1.01-1.caos.src.rpm > + SRPMS/perl-NTLM-1.02-1.caos.src.rpm > + SRPMS/perl-Parse-RecDescent-1.94-1.caos.src.rpm > + SRPMS/perl-String-CRC32-1.4-1.caos.src.rpm > + SRPMS/perl-SVG-2.33-1.caos.src.rpm > + SRPMS/perl-Term-Screen-1.03-1.caos.src.rpm > + SRPMS/perl-Test-Manifest-1.14-1.caos.src.rpm > + SRPMS/perl-Time-HiRes-1.87-1.caos.src.rpm > + SRPMS/perl-Unicode-Map-0.112-1.caos.src.rpm > + SRPMS/perl-Unicode-Map8-0.12-1.caos.src.rpm > + SRPMS/perl-Unicode-MapUTF8-1.11-1.caos.src.rpm > + SRPMS/perl-Unicode-String-2.09-1.caos.src.rpm > + SRPMS/php5-5.1.4-2.caos.src.rpm > + SRPMS/postfix-2.3.2-2.caos.src.rpm > + SRPMS/samba-3.0.23a-1.caos.src.rpm > + SRPMS/squirrelmail-1.4.7-1.caos.src.rpm > + SRPMS/thunderbird-1.5.0.5-1.caos.src.rpm > + SRPMS/vixie-cron-4.1-45.caos.src.rpm > + SRPMS/wireshark-0.99.2-1.caos.src.rpm > + SRPMS/xmms-plugin-crossfade-0.3.11-1.caos.src.rpm > + SRPMS/zsh-4.3.2-1.caos.src.rpm > - SRPMS/firefox-1.5.0.4-1.caos.src.rpm > - SRPMS/gnupg-1.4.2-1.caos.src.rpm > - SRPMS/gnupg-1.4.3-1.caos.src.rpm > - SRPMS/httpd-2.0.55-11.src.rpm > - SRPMS/lftp-3.1.3-1.src.rpm > - SRPMS/lftp-3.2.1-1.src.rpm > - SRPMS/lftp-3.3.3-1.src.rpm > - SRPMS/lftp-3.3.5-1.src.rpm > - SRPMS/lftp-3.4.2-1.src.rpm > - SRPMS/lftp-3.4.4-1.src.rpm > - SRPMS/libtiff-3.5.7-18.caos.src.rpm > - SRPMS/linux-2.6.11.11-70.caos.src.rpm > - SRPMS/linux-2.6.11.12-72.caos.src.rpm > - SRPMS/linux-2.6.11.6-61.caos.src.rpm > - SRPMS/linux-2.6.12.2-75.caos.src.rpm > - SRPMS/linux-2.6.12.3-76.caos.src.rpm > - SRPMS/linux-2.6.14.2-95.caos.src.rpm > - SRPMS/MySQL-4.1.15-3.src.rpm > - SRPMS/MySQL-4.1.20-1.caos.src.rpm > - SRPMS/php5-5.1.2-7.caos.src.rpm > - SRPMS/postfix-2.2.10-2.caos.src.rpm > - SRPMS/samba-3.0.9-2.caos.src.rpm > - SRPMS/thunderbird-1.0-2.src.rpm > - SRPMS/thunderbird-1.0.2-5.src.rpm > - SRPMS/thunderbird-1.0.6-5.src.rpm > - SRPMS/vixie-cron-4.1-33.src.rpm > > stable: > + SRPMS/firefox-1.5.0.5-1.caos.src.rpm > + SRPMS/fluxbox-1.0rc2-1.caos.src.rpm > + SRPMS/gftp-2.0.18-2.caos.src.rpm > + SRPMS/gnupg-1.4.5-1.caos.src.rpm > + SRPMS/helpme-0.20020910-1.caos.src.rpm > + SRPMS/httpd-2.0.59-1.caos.src.rpm > + SRPMS/hylafax-4.3.0.5-1.src.rpm > + SRPMS/lftp-3.5.2-1.caos.src.rpm > + SRPMS/libtiff-3.8.2-2.caos.src.rpm > + SRPMS/linux-2.6.17.7-99.caos.src.rpm > + SRPMS/MySQL-4.1.21-1.caos.src.rpm > + SRPMS/perl-Authen-NTLM-0.31-1.caos.src.rpm > + SRPMS/perl-Crypt-SmbHash-0.12-1.caos.src.rpm > + SRPMS/perl-Jcode-2.06-1.caos.src.rpm > + SRPMS/perl-NTLM-1.02-1.caos.src.rpm > + SRPMS/perl-Unicode-Map-0.112-1.caos.src.rpm > + SRPMS/perl-Unicode-Map8-0.12-1.caos.src.rpm > + SRPMS/perl-Unicode-MapUTF8-1.11-1.caos.src.rpm > + SRPMS/perl-Unicode-String-2.09-1.caos.src.rpm > + SRPMS/php5-5.1.4-2.caos.src.rpm > + SRPMS/postfix-2.3.2-2.caos.src.rpm > + SRPMS/samba-3.0.23a-1.caos.src.rpm > + SRPMS/thunderbird-1.5.0.5-1.caos.src.rpm > + SRPMS/vixie-cron-4.1-45.caos.src.rpm > + SRPMS/wireshark-0.99.2-1.caos.src.rpm > + SRPMS/zsh-4.3.2-1.caos.src.rpm > - SRPMS/firefox-1.5.0.4-1.caos.src.rpm > - SRPMS/gnupg-1.4.2-1.caos.src.rpm > - SRPMS/httpd-2.0.55-11.src.rpm > - SRPMS/lftp-3.1.3-1.src.rpm > - SRPMS/libtiff-3.5.7-18.caos.src.rpm > - SRPMS/linux-2.6.11.6-61.caos.src.rpm > - SRPMS/MySQL-4.1.15-3.src.rpm > - SRPMS/php5-5.1.2-7.caos.src.rpm > - SRPMS/postfix-2.2.10-2.caos.src.rpm > - SRPMS/samba-3.0.9-2.caos.src.rpm > - SRPMS/thunderbird-1.0-2.src.rpm > - SRPMS/vixie-cron-4.1-33.src.rpm > > -- > Greg Kurtzer > gmk at runlevelzero.net > > > > ------------------------------------------------------------------------ > > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20060809/573969e3/attachment.html From martyn at theendofhistether.org.uk Mon Aug 14 03:15:21 2006 From: martyn at theendofhistether.org.uk (Martyn) Date: Mon, 14 Aug 2006 11:15:21 +0100 Subject: [cAos] [cAos-devel] caos2 repository update In-Reply-To: <44D9C9E1.9060707@theendofhistether.org.uk> References: <44D9C9E1.9060707@theendofhistether.org.uk> Message-ID: <44E04D39.9040203@theendofhistether.org.uk> Issue confirmed on multiple machines, please can we revert back or fix and move forward. Cron scripts to fire every minute (possibly others too) do not fire at all with new vixie-cron. -- Martyn Martyn wrote: > Hi all/Greg > > I haven't had a chance to look into this yet, but there does seem to > be some kind of issue with vixie-cron. > > I have an entry like the following : > * * * * * /etc/ppp/checknet.sh > > Which was running perfectly on an older rev, and after a yum update > just isn't being called. > > I'll do some more checking but I'm rushed off my feet at the moment, > if anyone could confirm or say it's definitely something local to me, > that'd be great. > > Thanks > > Martyn Ranyard (Joran) From martyn at theendofhistether.org.uk Mon Aug 14 03:17:33 2006 From: martyn at theendofhistether.org.uk (Martyn) Date: Mon, 14 Aug 2006 11:17:33 +0100 Subject: [cAos] [cAos-devel] caos2 repository update In-Reply-To: <44E04D39.9040203@theendofhistether.org.uk> References: <44D9C9E1.9060707@theendofhistether.org.uk> <44E04D39.9040203@theendofhistether.org.uk> Message-ID: <44E04DBD.6060903@theendofhistether.org.uk> Hehe, trust me to send before checking the cvs checkins. Greg, can we get the new vixie in asap as current is cronless at present :-) Martyn wrote: >Issue confirmed on multiple machines, please can we revert back or fix >and move forward. > >Cron scripts to fire every minute (possibly others too) do not fire at >all with new vixie-cron. > >-- >Martyn > From mej at caosity.org Mon Aug 14 08:22:36 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 14 Aug 2006 11:22:36 -0400 Subject: [cAos] [cAos-devel] caos2 repository update In-Reply-To: <44E04D39.9040203@theendofhistether.org.uk> References: <44D9C9E1.9060707@theendofhistether.org.uk> <44E04D39.9040203@theendofhistether.org.uk> Message-ID: <20060814152236.GB25877@kainx.org> On Monday, 14 August 2006, at 11:15:21 (+0100), Martyn wrote: > Issue confirmed on multiple machines, please can we revert back or > fix and move forward. > > Cron scripts to fire every minute (possibly others too) do not fire > at all with new vixie-cron. Patience, Grasshopper. :-) The problem was a bad PAM module (loginuid.so) in /etc/pam.d/crond. I've already committed the fix, and you should be able to "yum install" (or "yum upgrade") it now, at least with the testing repo. If you're antsy, remove that line from the PAM config or do this: rpm -Uvh http://mirror.caosity.org/cAos-2/ext/autobuilder/i386/vixie-cron-4.1-46.caos.i386.rpm Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Saying 'no' to something is actually much more powerful than saying 'yes.'" -- Tom Hanks on "Charlie Rose" From martin.hardie at gmail.com Fri Aug 18 04:51:17 2006 From: martin.hardie at gmail.com (martin hardie) Date: Fri, 18 Aug 2006 13:51:17 +0200 Subject: [cAos] [cAos-devel] caos2 repository update In-Reply-To: <20060814152236.GB25877@kainx.org> References: <44D9C9E1.9060707@theendofhistether.org.uk> <44E04D39.9040203@theendofhistether.org.uk> <20060814152236.GB25877@kainx.org> Message-ID: <7ff9538b0608180451l15f47c11s31bb85ead3862ce0@mail.gmail.com> poke to all im alive just without connection in my new house watchout aussieman lives in caos On 8/14/06, Michael Jennings wrote: > > On Monday, 14 August 2006, at 11:15:21 (+0100), > Martyn wrote: > > > Issue confirmed on multiple machines, please can we revert back or > > fix and move forward. > > > > Cron scripts to fire every minute (possibly others too) do not fire > > at all with new vixie-cron. > > Patience, Grasshopper. :-) > > The problem was a bad PAM module (loginuid.so) in /etc/pam.d/crond. > I've already committed the fix, and you should be able to "yum > install" (or "yum upgrade") it now, at least with the testing repo. > > If you're antsy, remove that line from the PAM config or do this: > > rpm -Uvh > http://mirror.caosity.org/cAos-2/ext/autobuilder/i386/vixie-cron-4.1-46.caos.i386.rpm > > Michael > > -- > Michael Jennings (a.k.a. KainX) http://www.kainx.org/ > n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) > ----------------------------------------------------------------------- > "Saying 'no' to something is actually much more powerful than saying > 'yes.'" -- Tom Hanks on "Charlie Rose" > _______________________________________________ > cAos-devel mailing list > cAos-devel at caosity.org > http://lists.caosity.org/mailman/listinfo/caos-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20060818/7e0eca7c/attachment.html From martin.hardie at gmail.com Fri Aug 18 05:04:26 2006 From: martin.hardie at gmail.com (martin hardie) Date: Fri, 18 Aug 2006 14:04:26 +0200 Subject: [cAos] Fwd: Eterm license violation and non-free In-Reply-To: <20060818101135.87734.qmail@web86808.mail.ukl.yahoo.com> References: <20060818101135.87734.qmail@web86808.mail.ukl.yahoo.com> Message-ID: <7ff9538b0608180504p3755d67y421477aa23a8d9ff@mail.gmail.com> this is the stupdity of free software an its logic go Kainx you tell em theyre fucked aussieman ---------- Forwarded message ---------- From: bob marlet Date: Aug 18, 2006 12:11 PM Subject: Eterm license violation and non-free To: debian-legal at lists.debian.org hi, Eterm was removed from debian testing because a problem of license : there is a "cannot be sold for profit" in some source file. is it possible to include Eterm in non-free? see http://lists.debian.org/debian-legal/2006/03/msg00572.html "cannot be sold for profit" is ok with non-free? we need to have Eterm in etch, please can you solve this problem thank you p5.vert.ukl.yahoo.com uncompressed/chunked Fri Aug 18 09:34:02 GMT 2006 ___________________________________________________________________________ D?couvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/R?ponses pour partager vos connaissances, vos opinions et vos exp?riences. http://fr.answers.yahoo.com -- To UNSUBSCRIBE, email to debian-legal-REQUEST at lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20060818/27bf0222/attachment.html From weigelt at metux.de Fri Aug 18 08:43:45 2006 From: weigelt at metux.de (Enrico Weigelt) Date: Fri, 18 Aug 2006 17:43:45 +0200 Subject: [cAos] Announce: Comprehensive Source Database makes Distributor's and Sysop's life easier Message-ID: <200608181543.k7IFhjLV005621@metux.de> Announcing the Comprehensive Source Database Project ------------------------------------------------------ ==> What's it all about ? The CSDB project provides an uniform database with dozens of packages, their releases and tarball locations. Using this database, package maintainers and self-building sysops do not need to keep track of tarball urls by their own. They simply query the database by package name and canonical version number. CSDB also provides an simple URL redirector which provides an canonical URL for accessing certain package+version tarball and kicks you to an random download URL. This for example allows automatic buildsystems to ==> How does it work ? Lots of crawlers scan websites and ftp servers of many projects and feed in the found tarball URLs into our database. While feeding in, the data is brought into an strictly canonical form. We've got several classes of data objects: * packages -> identifier, description, ... * per package: releases -> canonical version, upstream version, ... * per release: src_url -> source-format, url, ... Users can access this database via various interfaces, ie. + Human-readble user interface: http://sourcefarm.metux.de/webfront/?show=world + Various robot interfaces: http://wiki.metux.de/public/SourceFarm/robots The robot interfaces are for automated systems, ie. system builders. For example, the URL redirector provides an uniform URL syntax for fetching an tarball of some given package in some given (canonical) version. It does an database lookup and kicks the client to the actual URL. Package maintainers can simply use these URLs instead of the actual ones and so don't have to cope with individual release URLs anymore. ==> How can I contribute ? Contributions are always welcomed :) Please join our mailinglist oss-qm-discuss at metux.de by writing "subscribe oss-qm" to majordomo at metux.de. You may freely use the wiki at http://sourcefarm.metux.de but please always drop not to the maillist if you wrote something. ===> Further stuff: [ ] How CSDB was born http://www.metux.de/articles/oss/csdb/how-csdb-was-born [ ] CSDB Website http://sourcefarm.metux.de/ ---------------------------------------------------------------------- The OSS-QM Project - Comprehensive Source Database Official contact: oss-qm-discuss at metux.de Website: http://sourcefarm.metux.de/ Maintainer: Enrico Weigelt, metux IT service Infrastructure: metux IT service - http://www.metux.de ---------------------------------------------------------------------- From rick at linuxmafia.com Fri Aug 18 15:30:27 2006 From: rick at linuxmafia.com (Rick Moen) Date: Fri, 18 Aug 2006 15:30:27 -0700 Subject: [cAos] Fwd: Eterm license violation and non-free In-Reply-To: <7ff9538b0608180504p3755d67y421477aa23a8d9ff@mail.gmail.com> References: <20060818101135.87734.qmail@web86808.mail.ukl.yahoo.com> <7ff9538b0608180504p3755d67y421477aa23a8d9ff@mail.gmail.com> Message-ID: <20060818223027.GZ26972@linuxmafia.com> Quoting martin hardie (martin.hardie at gmail.com): > this is the stupdity of free software an its logic > > go Kainx you tell em theyre fucked Michael Jennings himself is a BSD-licensing fan, as are most of the other authors. (I do see at least one third-party file under LGPL.) It looks like the problematic modules are command.[ch], 1992 copyright notice by "John Bovey, University of Kent at Canterbury, and netdisp.[ch], 1996 copyright notice by Chuck Blake . -- Cheers, "Heedless of grammar, they all cried 'It's him!'" Rick Moen -- R.H. Barham, _Misadventure at Margate_ rick at linuxmafia.com From gmk at runlevelzero.net Fri Aug 18 22:02:25 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Fri, 18 Aug 2006 22:02:25 -0700 Subject: [cAos] caos2 repository update Message-ID: current: + SRPMS/clamav-0.88.4-1.caos.src.rpm + SRPMS/curl-7.15.5-1.caos.src.rpm + SRPMS/encfs-1.3.1-1.caos.src.rpm + SRPMS/endeavour-2.7.1-1.caos.src.rpm + SRPMS/freeciv-2.0.8-6.caos.src.rpm + SRPMS/freetype-2.2.1-1.caos.src.rpm + SRPMS/fslint-2.16-1.caos.src.rpm + SRPMS/horde-3.1.3-1.caos.src.rpm + SRPMS/ImageMagick-6.2.9-1.caos.src.rpm + SRPMS/imp-4.1.3-1.caos.src.rpm + SRPMS/lftp-3.5.4-1.caos.src.rpm + SRPMS/linux-2.6.17.8-101.caos.src.rpm + SRPMS/mantis-1.0.5-1.caos.src.rpm + SRPMS/mutt-1.5.13-1.caos.src.rpm + SRPMS/perl-Compress-Zlib-1.41-2.caos.src.rpm + SRPMS/perl-Convert-BinHex-1.119-1.caos.src.rpm + SRPMS/perl-Net-DNS-0.57-2.caos.src.rpm + SRPMS/perl-Net-IP-1.25-1.caos.src.rpm + SRPMS/php5-5.1.4-3.caos.src.rpm + SRPMS/samba-3.0.23b-1.caos.src.rpm + SRPMS/scribus-1.3.3.3-1.caos.src.rpm + SRPMS/SDL-1.2.10-2.caos.src.rpm + SRPMS/seamonkey-1.0.3-1.caos.src.rpm + SRPMS/spamassassin-3.1.4-1.caos.src.rpm + SRPMS/squirrelmail-1.4.8-1.caos.src.rpm + SRPMS/unionfs-1.3-1.caos.src.rpm + SRPMS/vixie-cron-4.1-46.caos.src.rpm + SRPMS/xar-1.3-1.src.rpm + SRPMS/xdebug-2.0.0-0.beta5.1.caos.src.rpm + SRPMS/xorg-x11-6.8.2-5.caos.src.rpm - SRPMS/clamav-0.83-1.caos.src.rpm - SRPMS/clamav-0.87-1.caos.src.rpm - SRPMS/clamav-0.87.1-1.caos.src.rpm - SRPMS/clamav-0.88-1.caos.src.rpm - SRPMS/clamav-0.88.1-1.caos.src.rpm - SRPMS/clamav-0.88.2-1.caos.src.rpm - SRPMS/encfs-1.3.0-1.caos.src.rpm - SRPMS/fuse-2.2-2.caos.src.rpm - SRPMS/fuse-2.4.0-1.caos.src.rpm - SRPMS/fuse-2.5.1-1.caos.src.rpm - SRPMS/fuse-2.5.1-2.caos.src.rpm - SRPMS/lftp-3.5.2-1.caos.src.rpm - SRPMS/linux-2.6.17.7-99.caos.src.rpm - SRPMS/mantis-1.0.0a1-1.caos.src.rpm - SRPMS/ndiswrapper-1.2-2.caos.src.rpm - SRPMS/perl-Compress-Zlib-1.41-1.caos.src.rpm - SRPMS/perl-Net-DNS-0.57-1.caos.src.rpm - SRPMS/php5-5.1.4-2.caos.src.rpm - SRPMS/samba-3.0.23a-1.caos.src.rpm - SRPMS/vixie-cron-4.1-45.caos.src.rpm - SRPMS/xorg-x11-6.8.2-4.caos.src.rpm stable: + SRPMS/clamav-0.88.3-2.caos.src.rpm + SRPMS/encfs-1.3.1-1.caos.src.rpm + SRPMS/fuse-2.5.3-2.caos.src.rpm + SRPMS/lftp-3.5.4-1.caos.src.rpm + SRPMS/linux-2.6.17.8-101.caos.src.rpm + SRPMS/mantis-1.0.5-1.caos.src.rpm + SRPMS/ndiswrapper-1.14-1.caos.src.rpm + SRPMS/perl-Convert-BinHex-1.119-1.caos.src.rpm + SRPMS/perl-Net-IP-1.25-1.caos.src.rpm + SRPMS/php5-5.1.4-3.caos.src.rpm + SRPMS/samba-3.0.23b-1.caos.src.rpm + SRPMS/seamonkey-1.0.3-1.caos.src.rpm + SRPMS/unionfs-1.3-1.caos.src.rpm + SRPMS/vixie-cron-4.1-46.caos.src.rpm + SRPMS/xar-1.3-1.src.rpm + SRPMS/xdebug-2.0.0-0.beta5.1.caos.src.rpm + SRPMS/xorg-x11-6.8.2-5.caos.src.rpm - SRPMS/clamav-0.83-1.caos.src.rpm - SRPMS/encfs-1.3.0-1.caos.src.rpm - SRPMS/fuse-2.2-2.caos.src.rpm - SRPMS/lftp-3.5.2-1.caos.src.rpm - SRPMS/linux-2.6.17.7-99.caos.src.rpm - SRPMS/mantis-1.0.0a1-1.caos.src.rpm - SRPMS/ndiswrapper-1.2-2.caos.src.rpm - SRPMS/php5-5.1.4-2.caos.src.rpm - SRPMS/samba-3.0.23a-1.caos.src.rpm - SRPMS/vixie-cron-4.1-45.caos.src.rpm - SRPMS/xorg-x11-6.8.2-4.caos.src.rpm -- Greg Kurtzer gmk at runlevelzero.net From gmk at runlevelzero.net Sat Aug 19 21:50:27 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Sat, 19 Aug 2006 21:50:27 -0700 Subject: [cAos] caos-2 repository update Message-ID: current: + SRPMS/php-4.4.4-1.caos.src.rpm + SRPMS/php5-5.1.5-1.caos.src.rpm - SRPMS/php-4.3.9-6.caos.src.rpm - SRPMS/php5-5.1.4-3.caos.src.rpm stable: + SRPMS/php-4.4.4-1.caos.src.rpm + SRPMS/php5-5.1.5-1.caos.src.rpm - SRPMS/php-4.3.9-6.caos.src.rpm - SRPMS/php5-5.1.4-3.caos.src.rpm -- Greg Kurtzer gmk at runlevelzero.net From mej at caosity.org Tue Aug 22 13:56:49 2006 From: mej at caosity.org (Michael Jennings) Date: Tue, 22 Aug 2006 16:56:49 -0400 Subject: [cAos] Fwd: Eterm license violation and non-free In-Reply-To: <20060818223027.GZ26972@linuxmafia.com> References: <20060818101135.87734.qmail@web86808.mail.ukl.yahoo.com> <7ff9538b0608180504p3755d67y421477aa23a8d9ff@mail.gmail.com> <20060818223027.GZ26972@linuxmafia.com> Message-ID: <20060822205649.GA10666@kainx.org> On Friday, 18 August 2006, at 15:30:27 (-0700), Rick Moen wrote: > Michael Jennings himself is a BSD-licensing fan, as are most of the > other authors. (I do see at least one third-party file under LGPL.) > > It looks like the problematic modules are command.[ch], 1992 > copyright notice by "John Bovey, University of Kent at Canterbury, > and netdisp.[ch], 1996 copyright notice by Chuck Blake > . I've just released 0.9.4 which resolves this issue. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "With all the security bugs in JavaScript and all the pages that use it, a lot of sites are best viewed with telnet www.something.com 80" -- Darren Embry From benjamin at py-soft.co.uk Mon Aug 28 08:12:12 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 16:12:12 +0100 Subject: [cAos] cAos-2 logrotate problem. Message-ID: <44F307CC.4080505@py-soft.co.uk> My server runs cAos-2 and the logging daemon regularly falls over. I believe that I have isolated this to when logrotate runs; after no messages are logged from httpd or in messages, maillog etc and it appears the post rotate scripts aren't running. I have tried upgrading the kernel and httpd to: linux-smp-2.6.17.8-101.caos httpd-2.0.59-1.caos But the problem remains. The logging daemon and logrotate versions are: sysklogd-1.4.1-30 logrotate-3.7-4.1.caos I have just uninstalled and reinstalled these two. There's plenty of space on /var/log: # df /var/log Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol05 190403 20611 159962 12% /var/log Mount options: /dev/mapper/VolGroup00-LogVol05 on /var/log type ext3 (rw,noexec,nosuid,nodev) Forcing logrotate to run gives: # /usr/sbin/logrotate --force /etc/logrotate.conf error: error running shared postrotate script for /var/log/httpd/*log error: error running shared postrotate script for /var/log/mailman/bounce /var/log/mailman/digest /var/log/mailman/error /var/log/mailman/post /var/log/mailman/smtp /var/log/mailman/smtp-failure /var/log/mailman/qrunner /var/log/mailman/locks /var/log/mailman/fromusenet /var/log/mailman/subscribe /var/log/mailman/vette error: error running prerotate script, leaving old log in place error: error running shared postrotate script for /var/log/messages /var/log/secure /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron Any ideas why the post rotate scripts are failing? Entries from /etc/logrotate.d: # cat httpd /var/log/httpd/*log { missingok notifempty sharedscripts postrotate /bin/kill -HUP `cat /var/run/httpd.pid 2>/dev/null` 2> /dev/null || true endscript } # cat syslog /var/log/messages /var/log/secure /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron { sharedscripts postrotate /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null || true endscript } I'm no longer running cAos on my desktop so haven't been able to reproduce this... Any ideas? :-/ Ben From benjamin at py-soft.co.uk Mon Aug 28 09:01:40 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 17:01:40 +0100 Subject: [cAos] cAos-2 logrotate problem. In-Reply-To: <44F307CC.4080505@py-soft.co.uk> References: <44F307CC.4080505@py-soft.co.uk> Message-ID: <44F31364.6060402@py-soft.co.uk> Benjamin Donnachie wrote: > My server runs cAos-2 and the logging daemon regularly falls over. I > believe that I have isolated this to when logrotate runs; after no > messages are logged from httpd or in messages, maillog etc and it > appears the post rotate scripts aren't running. Ah! Mystery finally solved... /tmp was mounted as noexec! Ben From mej at caosity.org Mon Aug 28 10:16:42 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 28 Aug 2006 13:16:42 -0400 Subject: [cAos] cAos-2 logrotate problem. In-Reply-To: <44F31364.6060402@py-soft.co.uk> References: <44F307CC.4080505@py-soft.co.uk> <44F31364.6060402@py-soft.co.uk> Message-ID: <20060828171642.GG18668@kainx.org> On Monday, 28 August 2006, at 17:01:40 (+0100), Benjamin Donnachie wrote: > Ah! Mystery finally solved... /tmp was mounted as noexec! It's not unreasonable to mount /tmp with "noexec" for security reasons. This is definitely something we should fix. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Backstreet Boys? Why would you wanna do that? Didn't you see New Kids on the Block? Don't you know how this movie's gonna end? I wanna know who's gonna be the 'bad' Backstreet Boy. Who's gonna get Britney Spears pregnant?" -- Chris Rock, 1999 MTV VMA From benjamin at py-soft.co.uk Mon Aug 28 10:20:49 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 18:20:49 +0100 Subject: [cAos] cAos-2 logrotate problem. In-Reply-To: <20060828171642.GG18668@kainx.org> References: <44F307CC.4080505@py-soft.co.uk> <44F31364.6060402@py-soft.co.uk> <20060828171642.GG18668@kainx.org> Message-ID: <44F325F1.6050402@py-soft.co.uk> Michael Jennings wrote: > It's not unreasonable to mount /tmp with "noexec" for security > reasons. This is definitely something we should fix. I'm now using a separate directory and edited /etc/cron.daily/logrotate to make TMPDIR point to it. Ben From mej at caosity.org Mon Aug 28 10:57:40 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 28 Aug 2006 13:57:40 -0400 Subject: [cAos] cAos-2 logrotate problem. In-Reply-To: <44F325F1.6050402@py-soft.co.uk> References: <44F307CC.4080505@py-soft.co.uk> <44F31364.6060402@py-soft.co.uk> <20060828171642.GG18668@kainx.org> <44F325F1.6050402@py-soft.co.uk> Message-ID: <20060828175740.GH18668@kainx.org> On Monday, 28 August 2006, at 18:20:49 (+0100), Benjamin Donnachie wrote: > I'm now using a separate directory and edited > /etc/cron.daily/logrotate to make TMPDIR point to it. Maybe I'm wrong, but it seems to me that temporary scripts created as root during the running of a privileged program should be created and run in the most secure way possible. That, to me, means not assuming /tmp or /var/tmp is executable, but rather passing the script instructions directly to /bin/sh. Perhaps even through a pipe with no temporary files needed. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Was your bad playing today due to ignorance or apathy?" "I don't know, and I don't care." -- Frank Layden and Jeff Wilkins, Utah Jazz Coach and Forward, respectively From benjamin at py-soft.co.uk Mon Aug 28 11:04:47 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 19:04:47 +0100 Subject: [cAos] cAos-2 logrotate problem. In-Reply-To: <20060828175740.GH18668@kainx.org> References: <44F307CC.4080505@py-soft.co.uk> <44F31364.6060402@py-soft.co.uk> <20060828171642.GG18668@kainx.org> <44F325F1.6050402@py-soft.co.uk> <20060828175740.GH18668@kainx.org> Message-ID: <44F3303F.1000009@py-soft.co.uk> Michael Jennings wrote: > Maybe I'm wrong, but it seems to me that temporary scripts created as > root during the running of a privileged program should be created and > run in the most secure way possible. That, to me, means not assuming > /tmp or /var/tmp is executable, but rather passing the script > instructions directly to /bin/sh. Perhaps even through a pipe with no > temporary files needed. Agreed! But I guess that RedHat didn't feel that way... If I get time, I'll take a look at the source... but I suspect that you'll probably get round to it before me! :) Take care, Ben From slaton at berkeley.edu Mon Aug 28 11:24:42 2006 From: slaton at berkeley.edu (slaton) Date: Mon, 28 Aug 2006 11:24:42 -0700 (PDT) Subject: [cAos] grsec utils for new kernels? Message-ID: Hi, I noticed the new kernel from 'stable' (2.6.17.8-101) has grsec rolled in. Looking forward to playing with that. :) Not seeing the configuration utility (gradm) or file hierarchy (/etc/grsec) though. Didn't see anything in the various repos, am i missing it or should i just roll my own here? (easily done since it's a separate download from grsecurity.org). thanks slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu From gmk at runlevelzero.net Mon Aug 28 11:41:01 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Mon, 28 Aug 2006 11:41:01 -0700 Subject: [cAos] grsec utils for new kernels? In-Reply-To: References: Message-ID: <42846DF4-D34C-41DE-9BE9-96225694CCBB@runlevelzero.net> gradm has been imported and can be found in the testing repository. I will be promoting it to the current and stable repositories this evening. If you get a chance to test it, let me know how it goes please. Thanks! On Aug 28, 2006, at 11:24 AM, slaton wrote: > Hi, > > I noticed the new kernel from 'stable' (2.6.17.8-101) has grsec > rolled in. > Looking forward to playing with that. :) Not seeing the configuration > utility (gradm) or file hierarchy (/etc/grsec) though. Didn't see > anything > in the various repos, am i missing it or should i just roll my own > here? > (easily done since it's a separate download from grsecurity.org). > > thanks > slaton > > Slaton Lipscomb > Nogales Lab, Howard Hughes Medical Institute > http://cryoem.berkeley.edu > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos -- Greg Kurtzer gmk at runlevelzero.net From rick at linuxmafia.com Mon Aug 28 11:42:26 2006 From: rick at linuxmafia.com (Rick Moen) Date: Mon, 28 Aug 2006 11:42:26 -0700 Subject: [cAos] cAos-2 logrotate problem. In-Reply-To: <20060828171642.GG18668@kainx.org> References: <44F307CC.4080505@py-soft.co.uk> <44F31364.6060402@py-soft.co.uk> <20060828171642.GG18668@kainx.org> Message-ID: <20060828184225.GQ26972@linuxmafia.com> Quoting Michael Jennings (mej at caosity.org): > It's not unreasonable to mount /tmp with "noexec" for security > reasons. This is definitely something we should fix. Man, I wish more distro maintainers thought the way you do, on these matters! FWIW, _lots_ of present-day distros suffer mild-to-moderate breakage if /tmp is mounted noexec. So, I'll applaud wildly if you go on a mission to classify as a bug any dependency on executable bits in /tmp, but you might have picked quite a long row to hoe. From astevens at gravitypark.com Mon Aug 28 12:13:24 2006 From: astevens at gravitypark.com (Arthur A. Stevens) Date: Mon, 28 Aug 2006 12:13:24 -0700 Subject: [cAos] grsec utils for new kernels? References: <42846DF4-D34C-41DE-9BE9-96225694CCBB@runlevelzero.net> Message-ID: <000a01c6cad6$0a7faf30$6600a8c0@astevens> Yea!, Been waiting on that one ;) I will play with it tonight. I can do a caos3 package of it if you need. Good work! Arthur ----- Original Message ----- From: "Greg Kurtzer" To: "Community Assembled OS" Sent: Monday, August 28, 2006 11:41 AM Subject: Re: [cAos] grsec utils for new kernels? > gradm has been imported and can be found in the testing repository. I > will be promoting it to the current and stable repositories this > evening. If you get a chance to test it, let me know how it goes please. > > Thanks! > > On Aug 28, 2006, at 11:24 AM, slaton wrote: > >> Hi, >> >> I noticed the new kernel from 'stable' (2.6.17.8-101) has grsec >> rolled in. >> Looking forward to playing with that. :) Not seeing the configuration >> utility (gradm) or file hierarchy (/etc/grsec) though. Didn't see >> anything >> in the various repos, am i missing it or should i just roll my own >> here? >> (easily done since it's a separate download from grsecurity.org). >> >> thanks >> slaton >> >> Slaton Lipscomb >> Nogales Lab, Howard Hughes Medical Institute >> http://cryoem.berkeley.edu >> _______________________________________________ >> cAos mailing list >> cAos at caosity.org >> http://lists.caosity.org/mailman/listinfo/caos > > -- > Greg Kurtzer > gmk at runlevelzero.net > > > > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > From gmk at runlevelzero.net Mon Aug 28 12:36:34 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Mon, 28 Aug 2006 12:36:34 -0700 Subject: [cAos] grsec utils for new kernels? In-Reply-To: <000a01c6cad6$0a7faf30$6600a8c0@astevens> References: <42846DF4-D34C-41DE-9BE9-96225694CCBB@runlevelzero.net> <000a01c6cad6$0a7faf30$6600a8c0@astevens> Message-ID: <37C791CD-DDA0-45BD-A92E-76C145D8117F@runlevelzero.net> caos3 package of gradm is already done :) Use GRAB to get it with alpha5 or newer: # grab upgrade We need to create some default policies and configurations. I also haven't yet integrated with the sysinit subsystem. On Aug 28, 2006, at 12:13 PM, Arthur A. Stevens wrote: > Yea!, Been waiting on that one ;) > > I will play with it tonight. I can do a caos3 package of it if you > need. > > Good work! > > Arthur > > > ----- Original Message ----- > From: "Greg Kurtzer" > To: "Community Assembled OS" > Sent: Monday, August 28, 2006 11:41 AM > Subject: Re: [cAos] grsec utils for new kernels? > > >> gradm has been imported and can be found in the testing repository. I >> will be promoting it to the current and stable repositories this >> evening. If you get a chance to test it, let me know how it goes >> please. >> >> Thanks! >> >> On Aug 28, 2006, at 11:24 AM, slaton wrote: >> >>> Hi, >>> >>> I noticed the new kernel from 'stable' (2.6.17.8-101) has grsec >>> rolled in. >>> Looking forward to playing with that. :) Not seeing the >>> configuration >>> utility (gradm) or file hierarchy (/etc/grsec) though. Didn't see >>> anything >>> in the various repos, am i missing it or should i just roll my own >>> here? >>> (easily done since it's a separate download from grsecurity.org). >>> >>> thanks >>> slaton >>> >>> Slaton Lipscomb >>> Nogales Lab, Howard Hughes Medical Institute >>> http://cryoem.berkeley.edu >>> _______________________________________________ >>> cAos mailing list >>> cAos at caosity.org >>> http://lists.caosity.org/mailman/listinfo/caos >> >> -- >> Greg Kurtzer >> gmk at runlevelzero.net >> >> >> >> _______________________________________________ >> cAos mailing list >> cAos at caosity.org >> http://lists.caosity.org/mailman/listinfo/caos >> > > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos -- Greg Kurtzer gmk at runlevelzero.net From benjamin at py-soft.co.uk Mon Aug 28 13:16:32 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 21:16:32 +0100 Subject: [cAos] grsec utils for new kernels? In-Reply-To: <37C791CD-DDA0-45BD-A92E-76C145D8117F@runlevelzero.net> References: <42846DF4-D34C-41DE-9BE9-96225694CCBB@runlevelzero.net> <000a01c6cad6$0a7faf30$6600a8c0@astevens> <37C791CD-DDA0-45BD-A92E-76C145D8117F@runlevelzero.net> Message-ID: <44F34F20.5050203@py-soft.co.uk> Greg Kurtzer wrote: > We need to create some default policies and configurations. I also > haven't yet integrated with the sysinit subsystem. I'm ready to upgrade when you do! :-) Ben From benjamin at py-soft.co.uk Mon Aug 28 13:17:30 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 21:17:30 +0100 Subject: [cAos] cAos-2 logrotate problem. In-Reply-To: <20060828184225.GQ26972@linuxmafia.com> References: <44F307CC.4080505@py-soft.co.uk> <44F31364.6060402@py-soft.co.uk> <20060828171642.GG18668@kainx.org> <20060828184225.GQ26972@linuxmafia.com> Message-ID: <44F34F5A.1070400@py-soft.co.uk> Rick Moen wrote: > Man, I wish more distro maintainers thought the way you do, on these > matters! FWIW, _lots_ of present-day distros suffer mild-to-moderate > breakage if /tmp is mounted noexec. So, I'll applaud wildly if you go > on a mission to classify as a bug any dependency on executable bits in > /tmp, but you might have picked quite a long row to hoe. I mounted /tmp as noexec on my server a few months ago and so far only logrotate has broken. So fingers crossed... :) Ben From gmk at runlevelzero.net Mon Aug 28 13:52:19 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Mon, 28 Aug 2006 13:52:19 -0700 Subject: [cAos] grsec utils for new kernels? In-Reply-To: <44F34F20.5050203@py-soft.co.uk> References: <42846DF4-D34C-41DE-9BE9-96225694CCBB@runlevelzero.net> <000a01c6cad6$0a7faf30$6600a8c0@astevens> <37C791CD-DDA0-45BD-A92E-76C145D8117F@runlevelzero.net> <44F34F20.5050203@py-soft.co.uk> Message-ID: Now actually is a good time to provide comments, feedback, fixes and feature requests for caos-3. Please test the ISO at: http://linux.caosity.org/testing/caos-3.0-0.alpha6.i386.iso It will overtake your disk, so use dedicated hardware or a VM instance (there is a known bug right now with Vmware-Server). With GRAB, the system has the capability of keeping itself updated, thus there are already some people using it on testing and lightweight production (but not critical) systems. Also, if anyone is interested we need people that want to contribute some time to documentation of caos-3. Please email me directly if anyone on this list is interested. Have fun, and please send comments! :) Greg On Aug 28, 2006, at 1:16 PM, Benjamin Donnachie wrote: > Greg Kurtzer wrote: >> We need to create some default policies and configurations. I also >> haven't yet integrated with the sysinit subsystem. > > I'm ready to upgrade when you do! :-) > > Ben > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos -- Greg Kurtzer gmk at runlevelzero.net From benjamin at py-soft.co.uk Mon Aug 28 14:34:03 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 22:34:03 +0100 Subject: [cAos] Postfix plea! Message-ID: <44F3614B.6000605@py-soft.co.uk> Is it possible to compile postfix with support for both cyrus and dovecot SASL libraries? I use cyrus-imap (Admittedly, mainly for sieve) and hence use cyrus SASL, but I understand that most people would probably want to avoid it. I have just tried compiling postfix with support for both, but it's bombed out because I don't have the dovecot libraries installed. I haven't got a cAos devel machine at the moment and I'm reluctant to fiddle further on a live server. However, if support can be added, I'd be incredibly grateful! :) Ben From benjamin at py-soft.co.uk Mon Aug 28 14:46:21 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 22:46:21 +0100 Subject: [cAos] Postfix plea! In-Reply-To: <44F3614B.6000605@py-soft.co.uk> References: <44F3614B.6000605@py-soft.co.uk> Message-ID: <44F3642D.5020207@py-soft.co.uk> Benjamin Donnachie wrote: > Is it possible to compile postfix with support for both cyrus and > dovecot SASL libraries? >From my experiments, it would appear that compiling it with support cyrus SASL automatically includes dovecot: #/usr/sbin/postconf -a cyrus dovecot Could we please (pretty please!) do this for cAos? Perhaps with dovecot as the default? Take care, Ben From benjamin at py-soft.co.uk Mon Aug 28 14:56:30 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 22:56:30 +0100 Subject: [cAos] grsec utils for new kernels? In-Reply-To: References: <42846DF4-D34C-41DE-9BE9-96225694CCBB@runlevelzero.net> <000a01c6cad6$0a7faf30$6600a8c0@astevens> <37C791CD-DDA0-45BD-A92E-76C145D8117F@runlevelzero.net> <44F34F20.5050203@py-soft.co.uk> Message-ID: <44F3668E.2080006@py-soft.co.uk> Greg Kurtzer wrote: > Now actually is a good time to provide comments, feedback, fixes and > feature requests for caos-3. Please test the ISO at: > > http://linux.caosity.org/testing/caos-3.0-0.alpha6.i386.iso It's taking a very long time to download... :-/ Ben From benjamin at py-soft.co.uk Mon Aug 28 15:18:07 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 28 Aug 2006 23:18:07 +0100 Subject: [cAos] grsec utils for new kernels? In-Reply-To: <44F3668E.2080006@py-soft.co.uk> References: <42846DF4-D34C-41DE-9BE9-96225694CCBB@runlevelzero.net> <000a01c6cad6$0a7faf30$6600a8c0@astevens> <37C791CD-DDA0-45BD-A92E-76C145D8117F@runlevelzero.net> <44F34F20.5050203@py-soft.co.uk> <44F3668E.2080006@py-soft.co.uk> Message-ID: <44F36B9F.3050205@py-soft.co.uk> Benjamin Donnachie wrote: > It's taking a very long time to download... :-/ Now installing under qemu... Think I'll leave it to get on with it while I sleep. Ben From mej at caosity.org Mon Aug 28 16:47:00 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 28 Aug 2006 19:47:00 -0400 Subject: [cAos] Postfix plea! In-Reply-To: <44F3642D.5020207@py-soft.co.uk> References: <44F3614B.6000605@py-soft.co.uk> <44F3642D.5020207@py-soft.co.uk> Message-ID: <20060828234700.GI18668@kainx.org> On Monday, 28 August 2006, at 22:46:21 (+0100), Benjamin Donnachie wrote: > #/usr/sbin/postconf -a > cyrus > dovecot > > Could we please (pretty please!) do this for cAos? Perhaps with dovecot > as the default? The library support was there, but the server/client were not enabled. I've fixed that in postfix 2.3.3-2.caos. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "To err is human; to really louse things up requires Microsoft products." -- Alexander Pope, slightly paraphrased From astevens at gravitypark.com Mon Aug 28 17:15:28 2006 From: astevens at gravitypark.com (Arthur A. Stevens) Date: Mon, 28 Aug 2006 17:15:28 -0700 Subject: [cAos] grsec utils for new kernels? References: <42846DF4-D34C-41DE-9BE9-96225694CCBB@runlevelzero.net><000a01c6cad6$0a7faf30$6600a8c0@astevens> <37C791CD-DDA0-45BD-A92E-76C145D8117F@runlevelzero.net> Message-ID: <002201c6cb00$3bd6a8c0$6600a8c0@astevens> I can get with you this week on the default policies, etc. I have been meaning to do so, not just drop patches on you. :) Running alpha6 here with a few tweaks. Been doing some stuff that OF's the current vanila kernel and we seem ok. Stuff like that speaks for itself. This is definately going to be a serious conteder for the ISP market once people start playing with it more. Arthur ----- Original Message ----- From: "Greg Kurtzer" To: "Community Assembled OS" Sent: Monday, August 28, 2006 12:36 PM Subject: Re: [cAos] grsec utils for new kernels? > caos3 package of gradm is already done :) > > Use GRAB to get it with alpha5 or newer: > > # grab upgrade > > We need to create some default policies and configurations. I also > haven't yet integrated with the sysinit subsystem. > > > On Aug 28, 2006, at 12:13 PM, Arthur A. Stevens wrote: > >> Yea!, Been waiting on that one ;) >> >> I will play with it tonight. I can do a caos3 package of it if you >> need. >> >> Good work! >> >> Arthur >> >> >> ----- Original Message ----- >> From: "Greg Kurtzer" >> To: "Community Assembled OS" >> Sent: Monday, August 28, 2006 11:41 AM >> Subject: Re: [cAos] grsec utils for new kernels? >> >> >>> gradm has been imported and can be found in the testing repository. I >>> will be promoting it to the current and stable repositories this >>> evening. If you get a chance to test it, let me know how it goes >>> please. >>> >>> Thanks! >>> >>> On Aug 28, 2006, at 11:24 AM, slaton wrote: >>> >>>> Hi, >>>> >>>> I noticed the new kernel from 'stable' (2.6.17.8-101) has grsec >>>> rolled in. >>>> Looking forward to playing with that. :) Not seeing the >>>> configuration >>>> utility (gradm) or file hierarchy (/etc/grsec) though. Didn't see >>>> anything >>>> in the various repos, am i missing it or should i just roll my own >>>> here? >>>> (easily done since it's a separate download from grsecurity.org). >>>> >>>> thanks >>>> slaton >>>> >>>> Slaton Lipscomb >>>> Nogales Lab, Howard Hughes Medical Institute >>>> http://cryoem.berkeley.edu >>>> _______________________________________________ >>>> cAos mailing list >>>> cAos at caosity.org >>>> http://lists.caosity.org/mailman/listinfo/caos >>> >>> -- >>> Greg Kurtzer >>> gmk at runlevelzero.net >>> >>> >>> >>> _______________________________________________ >>> cAos mailing list >>> cAos at caosity.org >>> http://lists.caosity.org/mailman/listinfo/caos >>> >> >> _______________________________________________ >> cAos mailing list >> cAos at caosity.org >> http://lists.caosity.org/mailman/listinfo/caos > > -- > Greg Kurtzer > gmk at runlevelzero.net > > > > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > From mej at caosity.org Mon Aug 28 20:18:15 2006 From: mej at caosity.org (Michael Jennings) Date: Mon, 28 Aug 2006 23:18:15 -0400 Subject: [cAos] cAos-2 logrotate problem. In-Reply-To: <20060828184225.GQ26972@linuxmafia.com> References: <44F307CC.4080505@py-soft.co.uk> <44F31364.6060402@py-soft.co.uk> <20060828171642.GG18668@kainx.org> <20060828184225.GQ26972@linuxmafia.com> Message-ID: <20060829031815.GK18668@kainx.org> On Monday, 28 August 2006, at 11:42:26 (-0700), Rick Moen wrote: > Man, I wish more distro maintainers thought the way you do, on these > matters! FWIW, _lots_ of present-day distros suffer > mild-to-moderate breakage if /tmp is mounted noexec. So, I'll > applaud wildly if you go on a mission to classify as a bug any > dependency on executable bits in /tmp, but you might have picked > quite a long row to hoe. Possibly, but it's something I have done myself. There are advantages to being both a programmer and a sysadmin, like the ability to see both sides of many coins, security being a particularly sticky one. Programmers need temp space that's writeable, but sysadmins need temp space that's not a free-for-all. There's not always a simple solution, but in this case it seems pretty straight-forward. No reason that I can see not to treat it as a bug and fix it. Michael PS: If you think noexec for /tmp sucks, try /var sometime! :-) -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "If everything is coming your way, you're in the wrong lane." -- fortune From jedev at visarc.com Tue Aug 29 05:12:17 2006 From: jedev at visarc.com (Jack de Valpine) Date: Tue, 29 Aug 2006 08:12:17 -0400 Subject: [cAos] grsec utils for new kernels? Message-ID: <44F42F21.5070906@visarc.com> Hi All, I am a cAos newbie. I just installed cAos-2 yesterday. Once the system was up and running I used yum to get the latest smp kernel (linux-smp-2.6.17.8-101.caos). Now I am getting log messages from grsec. I am not familiar with this tool, though I understand it is a kernel security mechanism. I also understand that the admin tools are not included. Quite honestly, I really just want to turn this off so I do not need to worry if it impacts other things I am trying to setup mainly a test warewulf system. Where can I get the admin tools? What is the simplest way to just turn off grsec? Thanks in advance for your time. -Jack de valpine -- # Jack de Valpine # president # # visarc incorporated # http://www.visarc.com # # channeling technology for superior design and construction From mej at caosity.org Tue Aug 29 10:58:18 2006 From: mej at caosity.org (Michael Jennings) Date: Tue, 29 Aug 2006 13:58:18 -0400 Subject: [cAos] grsec utils for new kernels? In-Reply-To: <44F42F21.5070906@visarc.com> References: <44F42F21.5070906@visarc.com> Message-ID: <20060829175818.GC10666@kainx.org> On Tuesday, 29 August 2006, at 08:12:17 (-0400), Jack de Valpine wrote: > I am a cAos newbie. I just installed cAos-2 yesterday. Once the > system was up and running I used yum to get the latest smp kernel > (linux-smp-2.6.17.8-101.caos). Now I am getting log messages from > grsec. I am not familiar with this tool, though I understand it is > a kernel security mechanism. I also understand that the admin tools > are not included. The admin tools are userspace, not kernelspace. "yum install gradm" should do the trick. > Quite honestly, I really just want to turn this off so I do not need > to worry if it impacts other things I am trying to setup mainly a > test warewulf system. Where can I get the admin tools? What is the > simplest way to just turn off grsec? Use sysctl.conf and set the options you don't want to 0 instead of 1: # GRSecurity options kernel.grsecurity.audit_ipc = 0 kernel.grsecurity.audit_mount = 1 kernel.grsecurity.chroot_caps = 1 kernel.grsecurity.chroot_deny_chmod = 1 kernel.grsecurity.chroot_deny_chroot = 1 kernel.grsecurity.chroot_deny_fchdir = 1 kernel.grsecurity.chroot_deny_mknod = 1 kernel.grsecurity.chroot_deny_mount = 1 kernel.grsecurity.chroot_deny_pivot = 1 kernel.grsecurity.chroot_deny_shmat = 1 kernel.grsecurity.chroot_deny_sysctl = 1 kernel.grsecurity.chroot_deny_unix = 1 kernel.grsecurity.chroot_enforce_chdir = 1 kernel.grsecurity.chroot_execlog = 1 kernel.grsecurity.chroot_findtask = 1 kernel.grsecurity.chroot_restrict_nice = 1 kernel.grsecurity.destroy_unused_shm = 1 kernel.grsecurity.disable_modules = 0 kernel.grsecurity.dmesg = 1 kernel.grsecurity.execve_limiting = 1 kernel.grsecurity.fifo_restrictions = 1 kernel.grsecurity.forkfail_logging = 1 kernel.grsecurity.linking_restrictions = 1 kernel.grsecurity.rand_pids = 1 kernel.grsecurity.resource_logging = 1 kernel.grsecurity.signal_logging = 1 kernel.grsecurity.timechange_logging = 1 kernel.grsecurity.tpe = 0 kernel.grsecurity.tpe_gid = 99 kernel.grsecurity.tpe_restrict_all = 0 Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "To live on as we have is to leave behind joy, and love, and companionship, because we know it to be transitory, of the moment. We know it will turn to ash." -- Lorien, Babylon Five From jedev at visarc.com Tue Aug 29 11:22:23 2006 From: jedev at visarc.com (Jack de Valpine) Date: Tue, 29 Aug 2006 14:22:23 -0400 Subject: [cAos] grsec utils for new kernels? In-Reply-To: <20060829175818.GC10666@kainx.org> References: <44F42F21.5070906@visarc.com> <20060829175818.GC10666@kainx.org> Message-ID: <44F485DF.6090704@visarc.com> Hi Michael, Thanks for the reply. I tried to get gradm as you indicated but yum did not retrieve anything. I am using whatever the default repositories are for caos-2. What repository do I need to add to obtain this? Thanks, -Jack Michael Jennings wrote: > On Tuesday, 29 August 2006, at 08:12:17 (-0400), > Jack de Valpine wrote: > > >> I am a cAos newbie. I just installed cAos-2 yesterday. Once the >> system was up and running I used yum to get the latest smp kernel >> (linux-smp-2.6.17.8-101.caos). Now I am getting log messages from >> grsec. I am not familiar with this tool, though I understand it is >> a kernel security mechanism. I also understand that the admin tools >> are not included. >> > > The admin tools are userspace, not kernelspace. "yum install gradm" > should do the trick. > > >> Quite honestly, I really just want to turn this off so I do not need >> to worry if it impacts other things I am trying to setup mainly a >> test warewulf system. Where can I get the admin tools? What is the >> simplest way to just turn off grsec? >> > > Use sysctl.conf and set the options you don't want to 0 instead of 1: > > # GRSecurity options > kernel.grsecurity.audit_ipc = 0 > kernel.grsecurity.audit_mount = 1 > kernel.grsecurity.chroot_caps = 1 > kernel.grsecurity.chroot_deny_chmod = 1 > kernel.grsecurity.chroot_deny_chroot = 1 > kernel.grsecurity.chroot_deny_fchdir = 1 > kernel.grsecurity.chroot_deny_mknod = 1 > kernel.grsecurity.chroot_deny_mount = 1 > kernel.grsecurity.chroot_deny_pivot = 1 > kernel.grsecurity.chroot_deny_shmat = 1 > kernel.grsecurity.chroot_deny_sysctl = 1 > kernel.grsecurity.chroot_deny_unix = 1 > kernel.grsecurity.chroot_enforce_chdir = 1 > kernel.grsecurity.chroot_execlog = 1 > kernel.grsecurity.chroot_findtask = 1 > kernel.grsecurity.chroot_restrict_nice = 1 > kernel.grsecurity.destroy_unused_shm = 1 > kernel.grsecurity.disable_modules = 0 > kernel.grsecurity.dmesg = 1 > kernel.grsecurity.execve_limiting = 1 > kernel.grsecurity.fifo_restrictions = 1 > kernel.grsecurity.forkfail_logging = 1 > kernel.grsecurity.linking_restrictions = 1 > kernel.grsecurity.rand_pids = 1 > kernel.grsecurity.resource_logging = 1 > kernel.grsecurity.signal_logging = 1 > kernel.grsecurity.timechange_logging = 1 > kernel.grsecurity.tpe = 0 > kernel.grsecurity.tpe_gid = 99 > kernel.grsecurity.tpe_restrict_all = 0 > > Michael > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20060829/89fca5bc/attachment.html From mej at caosity.org Tue Aug 29 12:17:26 2006 From: mej at caosity.org (Michael Jennings) Date: Tue, 29 Aug 2006 15:17:26 -0400 Subject: [cAos] grsec utils for new kernels? In-Reply-To: <44F485DF.6090704@visarc.com> References: <44F42F21.5070906@visarc.com> <20060829175818.GC10666@kainx.org> <44F485DF.6090704@visarc.com> Message-ID: <20060829191726.GE10666@kainx.org> On Tuesday, 29 August 2006, at 14:22:23 (-0400), Jack de Valpine wrote: > Thanks for the reply. I tried to get gradm as you indicated but yum > did not retrieve anything. I am using whatever the default > repositories are for caos-2. What repository do I need to add to > obtain this? Try "testing" or annoy...er, I mean, politely ping Greg to push to current/stable. :-) Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "You don't know what you have until your Everything is gone. You need someone to show you how to live again." -- Blessid Union of Souls, "I Want to Be There" From slaton at berkeley.edu Tue Aug 29 13:26:42 2006 From: slaton at berkeley.edu (slaton) Date: Tue, 29 Aug 2006 13:26:42 -0700 (PDT) Subject: [cAos] grsec utils for new kernels? In-Reply-To: <20060829191726.GE10666@kainx.org> References: <44F42F21.5070906@visarc.com> <20060829175818.GC10666@kainx.org> <44F485DF.6090704@visarc.com> <20060829191726.GE10666@kainx.org> Message-ID: Btw the version of gradm in stable has one of the testing kernels as a dependency. Is this for real or should we just get it from http/ftp and install with --nodeps? thanks slaton Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu On Tue, 29 Aug 2006, Michael Jennings wrote: > On Tuesday, 29 August 2006, at 14:22:23 (-0400), > Jack de Valpine wrote: > > > Thanks for the reply. I tried to get gradm as you indicated but yum > > did not retrieve anything. I am using whatever the default > > repositories are for caos-2. What repository do I need to add to > > obtain this? > > Try "testing" or annoy...er, I mean, politely ping Greg to push to > current/stable. :-) > > Michael From mej at caosity.org Tue Aug 29 13:29:56 2006 From: mej at caosity.org (Michael Jennings) Date: Tue, 29 Aug 2006 16:29:56 -0400 Subject: [cAos] grsec utils for new kernels? In-Reply-To: References: <44F42F21.5070906@visarc.com> <20060829175818.GC10666@kainx.org> <44F485DF.6090704@visarc.com> <20060829191726.GE10666@kainx.org> Message-ID: <20060829202956.GG10666@kainx.org> On Tuesday, 29 August 2006, at 13:26:42 (-0700), slaton wrote: > Btw the version of gradm in stable has one of the testing kernels as > a dependency. Is this for real or should we just get it from > http/ftp and install with --nodeps? It depends on "kernel-grsec" version 2.1.9 or better which was probably not listed in the Provides: for the older kernels. If you're sure your kernel has grsec 2.1.9, --nodeps should be safe. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Only those whose lives are brief can imagine that love is eternal. You should embrace that remarkable illusion. It may be the greatest gift your race has ever received." -- Lorien, Babylon Five From slaton at berkeley.edu Tue Aug 29 13:37:44 2006 From: slaton at berkeley.edu (slaton) Date: Tue, 29 Aug 2006 13:37:44 -0700 (PDT) Subject: [cAos] grsec utils for new kernels? In-Reply-To: <20060829202956.GG10666@kainx.org> References: <44F42F21.5070906@visarc.com> <20060829175818.GC10666@kainx.org> <44F485DF.6090704@visarc.com> <20060829191726.GE10666@kainx.org> <20060829202956.GG10666@kainx.org> Message-ID: Thanks KainX. Obviously i meant "the version of gradm in testing"... but you figured that out already. :) slaton On Tue, 29 Aug 2006, Michael Jennings wrote: > On Tuesday, 29 August 2006, at 13:26:42 (-0700), > slaton wrote: > > > Btw the version of gradm in stable has one of the testing kernels as > > a dependency. Is this for real or should we just get it from > > http/ftp and install with --nodeps? > > It depends on "kernel-grsec" version 2.1.9 or better which was > probably not listed in the Provides: for the older kernels. If you're > sure your kernel has grsec 2.1.9, --nodeps should be safe. > > Michael > > -- > Michael Jennings (a.k.a. KainX) http://www.kainx.org/ > n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) > ----------------------------------------------------------------------- > "Only those whose lives are brief can imagine that love is eternal. > You should embrace that remarkable illusion. It may be the greatest > gift your race has ever received." -- Lorien, Babylon Five > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://lists.caosity.org/mailman/listinfo/caos > From slaton at berkeley.edu Tue Aug 29 16:19:28 2006 From: slaton at berkeley.edu (slaton) Date: Tue, 29 Aug 2006 16:19:28 -0700 (PDT) Subject: [cAos] Some conflicts installing recent x86_64 updates Message-ID: Having conflicts updating libtiff and xorg-x11-libs on x86_64 platform. What's the best way to deal with these? These both happen to be packages where i have installed both 32-bit and 64-bit versions. I have tried both standard (x86_64) core repo and a core32 repo (which is usually enabled=0) with baseurl http://mirror.caosity.org/cAos-2/core/i386 I was guessing i needed to install both 32-bit and 64-bit updates simultaneously to avoid triggering the conflict, but i don't know how to specify that on one yum command. thanks slaton recent xorg-x11-libs update: Transaction Check Error: file /usr/X11R6/lib/X11/locale/iso8859-2/Compose from install of xorg-x11-libs-6.8.2-5.caos conflicts with file from package xorg-x11-libs-6.8.2-4.caos file /usr/X11R6/lib/X11/locale/iso8859-3/Compose from install of xorg-x11-libs-6.8.2-5.caos conflicts with file from package xorg-x11-libs-6.8.2-4.caos file /usr/X11R6/lib/X11/locale/iso8859-9/Compose from install of xorg-x11-libs-6.8.2-5.caos conflicts with file from package xorg-x11-libs-6.8.2-4.caos file /usr/X11R6/lib/X11/locale/iso8859-9e/Compose from install of xorg-x11-libs-6.8.2-5.caos conflicts with file from package xorg-x11-libs-6.8.2-4.caos recent libtiff update: Transaction Check Error: file /usr/share/man/man1/fax2ps.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/fax2tiff.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/gif2tiff.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/pal2rgb.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/ppm2tiff.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/ras2tiff.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/rgb2ycbcr.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/sgi2tiff.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/thumbnail.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiff2bw.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiff2ps.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiff2rgba.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffcmp.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffcp.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffdither.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffdump.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffgt.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffinfo.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffmedian.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffsplit.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos file /usr/share/man/man1/tiffsv.1.gz from install of libtiff-3.8.2-2.caos conflicts with file from package libtiff-3.5.7-18.caos Slaton Lipscomb Nogales Lab, Howard Hughes Medical Institute http://cryoem.berkeley.edu From mej at caosity.org Tue Aug 29 20:50:05 2006 From: mej at caosity.org (Michael Jennings) Date: Tue, 29 Aug 2006 23:50:05 -0400 Subject: [cAos] Some conflicts installing recent x86_64 updates In-Reply-To: References: Message-ID: <20060830035005.GB12212@kainx.org> On Tuesday, 29 August 2006, at 16:19:28 (-0700), slaton wrote: > Having conflicts updating libtiff and xorg-x11-libs on x86_64 > platform. What's the best way to deal with these? I cannot reproduce this on IA-32, and I do not have access to an x86_64 box I can test on. I'm betting this is related to multi-lib, but I can't say for sure. > I was guessing i needed to install both 32-bit and 64-bit updates > simultaneously to avoid triggering the conflict, but i don't know > how to specify that on one yum command. Can you try "yum install xorg-x11-libs.i386 xorg-x11-libs.x86_64" and something similar for libtiff? Also, do you have "exactarch" set to 1 in your yum.conf? This is the part where I get to say "I told you so" to all the multilib fans I tried to convince were crazy back before even FC1 came out. ;-) Multilib is bad bad bad bad bad. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Nowadays they say you need a special chip to put in the TV so kids can't watch this and that. In my day, we didn't need a chip. My mom was the chip. End of story." -- Ray Charles From gmk at runlevelzero.net Tue Aug 29 21:57:09 2006 From: gmk at runlevelzero.net (Greg Kurtzer) Date: Tue, 29 Aug 2006 21:57:09 -0700 Subject: [cAos] caos2 repository update Message-ID: <47DD2AC6-5FC0-4D85-B7B4-CBAEC8197BB5@runlevelzero.net> current: + SRPMS/cdk-5.0-1.caos.src.rpm + SRPMS/Eterm-0.9.4-1.src.rpm + SRPMS/gradm-2.1.9-0.200608201448.1.caos.src.rpm + SRPMS/jabberd-2.0-0.s11.10.caos.src.rpm + SRPMS/libast-0.7.1-0.20060818.src.rpm + SRPMS/linux-2.6.17.11-102.caos.src.rpm + SRPMS/php5-5.1.6-1.caos.src.rpm + SRPMS/planner-0.13-5.src.rpm + SRPMS/postfix-2.3.3-2.caos.src.rpm + SRPMS/rssh-2.3.2-1.caos.src.rpm + SRPMS/squirrelmail-1.4.8-2.caos.src.rpm + SRPMS/tikiwiki-1.9.4-3.caos.src.rpm + SRPMS/wireshark-0.99.3a-1.caos.src.rpm + SRPMS/yaml-0.0.1-1.caos.src.rpm - SRPMS/ethereal-0.10.11-1.caos.src.rpm - SRPMS/ethereal-0.10.12-1.caos.src.rpm - SRPMS/linux-2.6.17.8-101.caos.src.rpm - SRPMS/php5-5.1.5-1.caos.src.rpm - SRPMS/postfix-2.3.2-2.caos.src.rpm - SRPMS/squirrelmail-1.4.4-3.caos.src.rpm - SRPMS/squirrelmail-1.4.7-1.caos.src.rpm - SRPMS/squirrelmail-1.4.8-1.caos.src.rpm - SRPMS/tikiwiki-1.9.0-1.caos.src.rpm - SRPMS/tikiwiki-1.9.0-3.caos.src.rpm - SRPMS/tikiwiki-1.9.0-4.caos.src.rpm - SRPMS/tikiwiki-1.9.1-2.caos.src.rpm - SRPMS/tikiwiki-1.9.1.1-2.caos.src.rpm - SRPMS/tikiwiki-1.9.1.1-3.caos.src.rpm stable: + SRPMS/cdk-5.0-1.caos.src.rpm + SRPMS/gradm-2.1.9-0.200608201448.1.caos.src.rpm + SRPMS/jabberd-2.0-0.s11.10.caos.src.rpm + SRPMS/linux-2.6.17.11-102.caos.src.rpm + SRPMS/php5-5.1.6-1.caos.src.rpm + SRPMS/postfix-2.3.3-2.caos.src.rpm + SRPMS/rssh-2.3.2-1.caos.src.rpm + SRPMS/squirrelmail-1.4.8-2.caos.src.rpm + SRPMS/tikiwiki-1.9.4-3.caos.src.rpm + SRPMS/yaml-0.0.1-1.caos.src.rpm - SRPMS/ethereal-0.10.11-1.caos.src.rpm - SRPMS/linux-2.6.17.8-101.caos.src.rpm - SRPMS/php5-5.1.5-1.caos.src.rpm - SRPMS/postfix-2.3.2-2.caos.src.rpm - SRPMS/squirrelmail-1.4.4-3.caos.src.rpm - SRPMS/tikiwiki-1.9.0-1.caos.src.rpm -- Greg Kurtzer gmk at runlevelzero.net From benjamin at py-soft.co.uk Wed Aug 30 04:12:57 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Wed, 30 Aug 2006 12:12:57 +0100 Subject: [cAos] Postfix plea! Message-ID: Michael Jennings wrote: >The library support was there, but the server/client were not >enabled. I've fixed that in postfix 2.3.3-2.caos. Excellent stuff! I tried 2.3.2-2.caos from stable, but it wasn't happy. When I get back I'll try the new version. Take care, -- Benjamin From slaton at berkeley.edu Wed Aug 30 10:48:56 2006 From: slaton at berkeley.edu (slaton) Date: Wed, 30 Aug 2006 10:48:56 -0700 (PDT) Subject: [cAos] Some conflicts installing recent x86_64 updates In-Reply-To: <20060830035005.GB12212@kainx.org> References: <20060830035005.GB12212@kainx.org> Message-ID: > Can you try "yum install xorg-x11-libs.i386 xorg-x11-libs.x86_64" and > something similar for libtiff? that worked. i'd forgotten the syntax for specifying rpm architecture with yum, thx. > Also, do you have "exactarch" set to 1 in your yum.conf? yes. thanks slaton From benjamin at py-soft.co.uk Wed Aug 30 12:04:39 2006 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Wed, 30 Aug 2006 20:04:39 +0100 Subject: [cAos] Postfix plea! In-Reply-To: References: Message-ID: <44F5E147.1040704@py-soft.co.uk> Benjamin Donnachie wrote: > Excellent stuff! I tried 2.3.2-2.caos from stable, but it wasn't happy. > When I get back I'll try the new version. Unfortunately, 2.3.3-2.caos doesn't support TLS :-( Ben From slaton at berkeley.edu Wed Aug 30 19:18:12 2006 From: slaton at berkeley.edu (slaton) Date: Wed, 30 Aug 2006 19:18:12 -0700 (PDT) Subject: [cAos] grsec utils for new kernels? In-Reply-To: <20060829175818.GC10666@kainx.org> References: <44F42F21.5070906@visarc.com> <20060829175818.GC10666@kainx.org> Message-ID: KainX, is that the default ruleset, if no entries are in sysctl.conf? thanks slaton > # GRSecurity options > kernel.grsecurity.audit_ipc = 0 > kernel.grsecurity.audit_mount = 1 > kernel.grsecurity.chroot_caps = 1 > kernel.grsecurity.chroot_deny_chmod = 1 > kernel.grsecurity.chroot_deny_chroot = 1 > kernel.grsecurity.chroot_deny_fchdir = 1 > kernel.grsecurity.chroot_deny_mknod = 1 > kernel.grsecurity.chroot_deny_mount = 1 > kernel.grsecurity.chroot_deny_pivot = 1 > kernel.grsecurity.chroot_deny_shmat = 1 > kernel.grsecurity.chroot_deny_sysctl = 1 > kernel.grsecurity.chroot_deny_unix = 1 > kernel.grsecurity.chroot_enforce_chdir = 1 > kernel.grsecurity.chroot_execlog = 1 > kernel.grsecurity.chroot_findtask = 1 > kernel.grsecurity.chroot_restrict_nice = 1 > kernel.grsecurity.destroy_unused_shm = 1 > kernel.grsecurity.disable_modules = 0 > kernel.grsecurity.dmesg = 1 > kernel.grsecurity.execve_limiting = 1 > kernel.grsecurity.fifo_restrictions = 1 > kernel.grsecurity.forkfail_logging = 1 > kernel.grsecurity.linking_restrictions = 1 > kernel.grsecurity.rand_pids = 1 > kernel.grsecurity.resource_logging = 1 > kernel.grsecurity.signal_logging = 1 > kernel.grsecurity.timechange_logging = 1 > kernel.grsecurity.tpe = 0 > kernel.grsecurity.tpe_gid = 99 > kernel.grsecurity.tpe_restrict_all = 0 From mej at caosity.org Wed Aug 30 19:22:24 2006 From: mej at caosity.org (Michael Jennings) Date: Wed, 30 Aug 2006 22:22:24 -0400 Subject: [cAos] grsec utils for new kernels? In-Reply-To: References: <44F42F21.5070906@visarc.com> <20060829175818.GC10666@kainx.org> Message-ID: <20060831022224.GN12212@kainx.org> On Wednesday, 30 August 2006, at 19:18:12 (-0700), slaton wrote: > KainX, is that the default ruleset, if no entries are in sysctl.conf? If it's not exactly the same, it's pretty darn close. :) Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "There's just something about debugging with a buggy debugger that reeks of rotten luck...."