Discuss June 2007

discuss@lists.centos.org

280 participants
339 discussions

CentOS 3.9
by Dag Wieers 12 Jun '07

12 Jun '07

Hi, Red Hat started releasing security advisories and update packages that are part of RHEL3 U9. Still, on RHN there are no RHEL3 U9 ISO images released yet. As usual, CentOS will make available CentOS 3.9 when it is deemed ready. So there is no need to ask when it is going to be released :) Kind regards, -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]

6 7

CentOS-announce Digest, Vol 28, Issue 8
by centos-announce-request＠centos.org 11 Jun '07

11 Jun '07

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2007:0385 Moderate CentOS 3 ia64 fetchmail - security update (Pasi Pirhonen) 2. CESA-2007:0385 Moderate CentOS 4 ia64 fetchmail - security update (Pasi Pirhonen) 3. CESA-2007:0385 Moderate CentOS 3 s390(x) fetchmail - security update (Pasi Pirhonen) 4. CESA-2007:0385 Moderate CentOS 4 s390(x) fetchmail - security update (Pasi Pirhonen) 5. CESA-2007:0403 Moderate CentOS 3 i386 freetype - security update (Tru Huynh) 6. CESA-2007:0403 Moderate CentOS 3 x86_64 freetype - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Sun, 10 Jun 2007 19:18:45 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2007:0385 Moderate CentOS 3 ia64 fetchmail - security update To: centos-announce(a)centos.org Message-ID: <20070610161845.GE22723(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2007:0385 https://rhn.redhat.com/errata/RHSA-2007-0385.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/fetchmail-6.2.0-3.el3.4.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

Problems with UserDir directive on CentOS 5
by Niki Kovacs 11 Jun '07

11 Jun '07

Hi, I'm currently setting up a local LAMP server to test various apps. Starting from the out-of-the-box configuration of Apache, I test it, and it's OK: http://localhost shows Apache's default page OK in Firefox. Now I edit /etc/httpd/conf/httpd.conf and replace 'UserDir disabled' by 'UserDir public_html'. I restart Apache. Then, as a normal user (kikinovak): $ cd $ mkdir public_html I edit a basic index.html file, then put it into this directory. I open Firefox at http://localhost/~kikinovak/ ... and I get the following error message: Forbidden You don't have permission to access /~kikinovak/ on this server. Apache/2.2.3 (CentOS) Server at localhost Port 80 Q: what did I do wrong? (I've done this successfully on Slackware and Debian before) Any suggestions? Niki

4 5

(no subject)
by Craig Van Ham 11 Jun '07

11 Jun '07

2 1

Where can I find a package for gtk-gnutella?
by John Lagrue 11 Jun '07

11 Jun '07

Running CentOS 4.5. I would think this should be simple, but I can't find a package for the above. Any pointers? JDL

2 3

Dovecot .99 Bug - LF not found where expected
by John Hinton 11 Jun '07

11 Jun '07

After about three years of this, it seems I have finally gotten somewhere near to the bottom of this. The symptom: Suddenly a user cannot download their email. Checking again through SquirrelMail, I get an error which says a log was written. Going to the logs I see "imap(username): Error indexing mbox file /var/mail/username: LF not found where expected" Using Webmin's read mail module, I can see the messages. So, I move them to another account, but this is not yet the end of it. I was at first having to delete the mbox and then I'd send a test message in to recreate the mbox. But today, I tried a different tack. I opened the now empty mbox in vi and found one blank line (LF). I deleted that line and then moved the mail back in and everything was fixed. So the line was still left behind. The next time this happens, I'm going to try to delete a LF from the top of the mbox file to see if it is fixed without moving the mail. I have read several places, although this is extremely difficult to track as there seems to be a multiple from address issue for some releases.. but anyway, I did finally find that dovecot .99 has an issue with leaving behind an extra linefeed at the beginning of the mbox. Deleting this linefeed fixes the problem. Supposedly dovecot 1 has fixed this problem. I have found many reports of problems on Fedora and RedHat. Also, Debian has a closed bug report regarding this issue as they have moved forward to dovecot-1.0 and it doesn't have this bug. The issue seems to not have any relation to the mailserver, as I saw both reports of problems on at least Sendmail and Postfix. Why are we still bugged with this? Seems that this is a bug that RedHat should be aware of? The problem is it only rarely happens. I have no idea how to repeat the issue. It always seems to be an Outlook user, although that is by far the most prevalent email client in use by our users and it might just be chance. So, what to do from here? Bug report to RedHat? This is most irritating! I can't even guess how many times I've fixed these mboxes. I'm about ready to toss dovecot in the trash until 1 becomes the RH standard unless there is a fix or upgrade from Redhat. Thanks, John Hinton

10 22

tar question
by Tom Brown 10 Jun '07

10 Jun '07

Hi Using tar i normally create an archive etc and then unpack that archive, job done. But i am copying from one filesystem to another on the same host, they are 2 seperate nfs filesystems, and i wonder is it possible to use tar to do this as opposed to say rsync etc. tar -cvf /some/input/dir to/here etc ? thanks

7 7

Standard RH iptables analysis
by Al Sparks 10 Jun '07

10 Jun '07

This is a standard RedHat / CentOS firewall configuration, where I told it, through the standard RH setup GUI, that I want ssh and snmp allowed through. Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp -- anywhere anywhere udp dpt:ipp ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:snmp ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh REJECT all -- anywhere anywhere reject-with icmp-host-prohibited The way I read this, though, the first rule in the RH-Firewall-1-INPUT chain applies to all packets coming in, which it accepts. That's all protocols from "anywhere" going to "anywhere". So shouldn't the packet no longer be evaluated past that rule? I know that when I have this enabled, it's stopping packets. So I'm reading this wrong. What am I getting wrong? === Al

5 5

CentOS and Wordpress
by petevg＠gmail.com 10 Jun '07

10 Jun '07

Hi All, I am currently am responsible for maintaining a website built on Apache 2, running on some CentOS 4 (64 bit version) boxes. Thus far, the website has comprised a few HTML pages, and some dynamic pages generated by perl scripts. The CentOS install is pretty vanilla -- the only departure I've made from the default server install is to install awstats from the rpmforge repositories. This week, I tried to install Wordpress, and have run into a brick wall that several days of experimentation and deep consultation with Google have been unable to get me over. Here's the situation: I installed the mysql, mysql_server, and php packages, unpacked the Wordpress tarball into a "blog" directory, and make the necessary changes to wp-config.php. The MySQL database works just fine, and when I visit the blog directory, index.php runs and informs me that I need to surf over to install.php to complete the WordPress configuration, which is expected. But when I try to browse to install.php, Firefox gives me the option to save it, or run it locally -- it doesn't seem to want to run as a server side script, for some reason. I don't see any obvious issues with my php installation that would cause this -- /etc/httpd/conf.d/php.conf is in place, is loading module_php4, and has added a php application type to the apache setup. I did remember to restart the http daemon after installing php. I don't see any errors in the logs -- all I see in the apache logs is a GET request for install.php. The really confusing thing is that one php script -- index.php -- works just fine, while another php script -- install.php -- does not. Has anybody run into a similar problem with WordPress, or with php4 in general? It feels like I'm running afoul of some bit of overzealous security that's trying to stop php from doing Bad Things to the system, but, sans error messages, it's been difficult to figure out what bit of security might be responsible, and how I might go about coaxing CentOS into allowing me to run WordPress. And so I have come here to tap into the wisdom of the mailing list. Might anybody here have some hints as to what I might do to solve this puzzle? Thank you, -- ~PeteVG The truth does not change according to our ability to stomach it. ~ Flannery O'Connor

4 4

procmail, and the care and feeding of mailing list content received
by R P Herrold 10 Jun '07

10 Jun '07

Some threads just go on too long. Personally I think a troll has hijacked the main centos list again and is inducing food fight behaviours while that troll perfectly 'innocently' asserting that it is just respoding to all email. see: http://video.google.com/videoplay?docid=-4216011961522818645 for a discussion of the problem of 'capture' in FOSS projects. But if one loses interest in a thread, it is easy enough to tune them out: 1. Install procmail; yum knows how 2. Add a mark and drop ruleset [herrold@new .procmail]$ cat ~/.procmail/killfilerc # # mark them :0fh ^ *List-Id:.*centos\.centos\.org ^ *Subject:.*CentOS Based Linux Firewall Document *!^X-brand | formail -A "X-brand: killfile " # and dump them :0 w * ^X-brand: killfile /dev/null 3. Integrate it in mailhandling; a fragment from: /home/herrold/.procmailrc # easy drops INCLUDERC=$HOME/.procmail/killfilerc ----------------------------------- easy enough to save 'caught' pieces to a file, rather than devnull until you are certain collateral damage has not been induced; see the procmail manpage series for a full discussion. -- Russ Herrold

2 2

← Newer
1
...
21
22
23
24
25
26
27
...
34
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2007