Discuss

discuss@lists.centos.org

34753 discussions

USB drive detected, but nothing gets mounted.
by MHR 24 Aug '08

24 Aug '08

I have a brand new, unaltered (as yet) 4Gb USB flash drive from Micro Center that does not get automounted when I plug it into my 5.2 desktop (home or work). It shows up in lsusb, and I can mount it manually, so why would it not mount automatically? Note that when I plug in other flash drives on the same machine before and after, they all get automounted as usual. Curious.... mhr

6 10

Crash recovery
by ABBAS KHAN 23 Aug '08

23 Aug '08

While playing with the graphic card drivers, I broke up the system and now I've a kernel panic with not syncing error. I did backup the system with mondorescue but I forgot to write the iso image files to the DVD rom. Can I burn the ISO file in rescue mode or in CentOS livecd environment? Already tried in the LiveCD env, but, as soon as I eject the live CD to put a blank DVD, the system halts ! Are there any other options available? Please advise.

3 5

CentOS 5.2 + SELinux + Apache/PHP + Postfix
by Art Age Software 23 Aug '08

23 Aug '08

Hi All, I'm running CentOS 5.2 with SELinux in enforcing mode (default targeted policy). The server hosts a PHP web app that sends mail. I'm getting the following errors (see end of message) in my selinux audit.log file every time the app sends an email. The email always seems to get sent successfully, despite the log messages. However, they do concern me and I would like to understand what they mean and why they occur. The first set of messages seems to relate to postfix being denied attempts to create/read/write a temporary file in Apache's context. In the second set, it seems to postdrop is attempting to do something with apache's error log file. Can anyone help make sense of this? I know I can create policy rules to allow these actions. But I don't want to do that without understanding the implications. For reference, audit2allow suggests the following policy additions: #============= postfix_postdrop_t ============== allow postfix_postdrop_t httpd_log_t:file getattr; #============= system_mail_t ============== allow system_mail_t httpd_t:file read; allow system_mail_t httpd_tmp_t:file { read write }; Any help greatly appreciated. Thanks! Sam ------------------------------------------------------------------------------------------- type=AVC msg=audit(1219458556.400:16996): avc: denied { read write } for pid=xxxxx comm="sendmail" path=2F746D702F2E7863616368652E302E302E313236373935383634322E6C6F636B202864656C6574656429 dev=dm-1 ino=xxxxx scontext=user_u:system_r:system_mail_t:s0 tcontext=user_u:object_r:httpd_tmp_t:s0 tclass=file type=AVC msg=audit(1219458556.400:16996): avc: denied { read write } for pid=xxxxx comm="sendmail" path=2F746D702F2E7863616368652E302E312E3534383639343233352E6C6F636B202864656C6574656429 dev=dm-1 ino=xxxxx scontext=user_u:system_r:system_mail_t:s0 tcontext=user_u:object_r:httpd_tmp_t:s0 tclass=file type=AVC msg=audit(1219458556.400:16996): avc: denied { read write } for pid=xxxxx comm="sendmail" path=2F746D702F2E7863616368652E302E322E313236323334313837332E6C6F636B202864656C6574656429 dev=dm-1 ino=xxxxx scontext=user_u:system_r:system_mail_t:s0 tcontext=user_u:object_r:httpd_tmp_t:s0 tclass=file type=AVC msg=audit(1219458556.400:16996): avc: denied { read write } for pid=xxxxx comm="sendmail" path=2F746D702F2E7863616368652E302E332E32313137303238332E6C6F636B202864656C6574656429 dev=dm-1 ino=xxxxx scontext=user_u:system_r:system_mail_t:s0 tcontext=user_u:object_r:httpd_tmp_t:s0 tclass=file type=AVC msg=audit(1219458556.400:16996): avc: denied { read } for pid=xxxxx comm="sendmail" path="eventpoll:[xxxxx]" dev=eventpollfs ino=xxxxx scontext=user_u:system_r:system_mail_t:s0 tcontext=user_u:system_r:httpd_t:s0 tclass=file type=SYSCALL msg=audit(1219458556.400:16996): arch=c000003e syscall=59 success=yes exit=0 a0=e04360 a1=e043e0 a2=e031a0 a3=3 items=0 ppid=xxxxx pid=xxxxx auid=xxx uid=xxx gid=xxx euid=xxx suid=xxx fsuid=xxx egid=xxx sgid=xxx fsgid=xxx tty=(none) ses=1363 comm="sendmail" exe="/usr/sbin/sendmail.postfix" subj=user_u:system_r:system_mail_t:s0 key=(null) type=AVC msg=audit(1219458556.410:16997): avc: denied { getattr } for pid=xxxxx comm="postdrop" path="/var/log/httpd/error_log" dev=dm-4 ino=xxxxx scontext=user_u:system_r:postfix_postdrop_t:s0 tcontext=user_u:object_r:httpd_log_t:s0 tclass=file type=SYSCALL msg=audit(1219458556.410:16997): arch=c000003e syscall=5 success=no exit=-13 a0=2 a1=7fffd0dbfa70 a2=7fffd0dbfa70 a3=0 items=0 ppid=xxxxx pid=xxxxx auid=xxx uid=xxx gid=xxx euid=xxx suid=xxx fsuid=xxx egid=xxx sgid=xxx fsgid=xxx tty=(none) ses=1363 comm="postdrop" exe="/usr/sbin/postdrop" subj=user_u:system_r:postfix_postdrop_t:s0 key=(null) -------------------------------------------------------------------------------------------

2 1

CentOS-announce Digest, Vol 42, Issue 6
by centos-announce-request＠centos.org 23 Aug '08

23 Aug '08

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-2008:0855 Critical CentOS 5 x86_64 openssh Update (Karanbir Singh) 2. CESA-2008:0855 Critical CentOS 5 i386 openssh Update (Karanbir Singh) 3. CentOS position on systems intrusion at Red Hat (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Fri, 22 Aug 2008 21:45:22 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0855 Critical CentOS 5 x86_64 openssh Update To: centos-announce(a)centos.org Message-ID: <20080822204522.GA21052(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2008:0855 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0855.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 161c953e8c1c47c09542020837e9920b openssh-4.3p2-26.el5_2.1.x86_64.rpm 12b02fb6e6d1e8354539cd4cba304803 openssh-askpass-4.3p2-26.el5_2.1.x86_64.rpm c281a62dc3c21f1225ea309757b755d1 openssh-clients-4.3p2-26.el5_2.1.x86_64.rpm 01b3486f17ecb4adc7c59074525b7fd9 openssh-server-4.3p2-26.el5_2.1.x86_64.rpm Source: 278cfb304350f3604fb64ebaee3f1b77 openssh-4.3p2-26.el5_2.1.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Fri, 22 Aug 2008 21:45:22 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2008:0855 Critical CentOS 5 i386 openssh Update To: centos-announce(a)centos.org Message-ID: <20080822204522.GA21035(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2008:0855 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0855.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: d45c32890088d835ce8bc4a569173775 openssh-4.3p2-26.el5_2.1.i386.rpm 7f8194567e7797d834c22090d9c55b69 openssh-askpass-4.3p2-26.el5_2.1.i386.rpm c145d732591711659b5fe756a4e9a085 openssh-clients-4.3p2-26.el5_2.1.i386.rpm 2b1fdc9b245f2c8cd873ea7f8e3b900c openssh-server-4.3p2-26.el5_2.1.i386.rpm Source: 278cfb304350f3604fb64ebaee3f1b77 openssh-4.3p2-26.el5_2.1.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Fri, 22 Aug 2008 23:15:29 +0100 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CentOS position on systems intrusion at Red Hat To: CentOS-Announce <centos-announce(a)centos.org>, CentOS mailing list <centos(a)centos.org> Message-ID: <48AF3A81.3090903(a)centos.org> Content-Type: text/plain; charset=ISO-8859-1 Earlier in the day today Red Hat made an announcement [1] that there had been an intrusion into some of their computer systems last week. In the same announcement they mention that some of the packages for OpenSSH on RHEL-4 ( i386 and x86_64 ) as well as RHEL-5 ( x86_64 ) were signed by the intruder. In their announcement they also clarified that they were confident that none of these, potentially compromised, packages made their way into or through RHN to client and customer machines. As a security measure a script [3] was made available along with a semi-detailed description of the issue [2]. We take security issues very seriously, and as soon as we were made aware of the situation I undertook a complete audit of the entire CentOS4/5 Build and Signing infrastructure. We can now assure everyone that no compromise has taken place anywhere within the CentOS Infrastructure. Our entire setup is located behind multiple firewalls, and only accessible from a very small number of places, by only a few people. Also included in this audit were all entry points to the build services, signing machines, primary release machines and connectivity between all these hosts. Since OpenSSH is a critical component of any Linux machine, we considered it essential to audit the last two released package sets ( openssh-4.3p2-26.el5.src.rpm, openssh-4.3p2-26.el5_2.1.src.rpm ). I have just finished this code audit, and can assure everyone that there is no compromised code included in either of these packages. A similar check is also being done for the CentOS-4 sources. Packages released today, by upstream, ( based on : openssh-4.3p2-26.el5_2.1.src.rpm, openssh-3.9p1-11.el4_7.src.rpm ) address two issues. Firstly they contain a fix for http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4752 . And secondly, in the remote event that someone had indeed got compromised packages via RHN, their packages would get updated to a known good state. We wanted to get these packages out right away to address the first issue, and also to cover users converting non updated RHEL installs to CentOS in the next few weeks/months. Release of these packages into the mirror.centos.org network does *not* imply that CentOS users are affected by the intrusion at Red Hat. Finally, while we feel confident that there is no possibility of this compromise having been passed onto the CentOS userbase, we still encourage users to verify their packages independently using whatever resources they might have available. -- [1]: https://rhn.redhat.com/errata/RHSA-2008-0855.html [2]: http://www.redhat.com/security/data/openssh-blacklist.html [3]: https://www.redhat.com/security/data/openssh-blacklist-1.0.sh :Its important to note that this script *only* checks for packages built within Red Hat, and will *not* be a reliable source of verification on CentOS since we rebuild from sources, using no Red Hat binary. -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 42, Issue 6 **********************************************

1 0

Adding new Hard disk to server with RAID-5
by Lunix1618 23 Aug '08

23 Aug '08

Hi all, I have Dell 2950 III with RAID-5 installed and managed by hardware Raid controller, I also use LVM when install CentOS. Now I get more 03 Hard disk and I would like to add it in to the running system. My question is: 1) if new hard disks add in to the machine, I have to rebuild the RAID volume with RAID management (raid controller) and the volume will be expanded, but is that make any problem to LVM at OS level ? 2) if (1's) answer is YES, what I need to do to prevent trouble occur ? If any one exprience or know the place can help me start pls share. Sorry for the dumb question but I never did this before as a newbie Linux admin - I am 'handmade' former....Windows admin Thanks for your help. regards.

2 1

Re: [CentOS] OT: Google Earth, v.4.3.7284.3916 (beta) on CentOS 5.2 (32 bit) (SOLVED)
by Lanny Marcus 23 Aug '08

23 Aug '08

On Fri, Aug 22, 2008 at 8:00 PM, Lanny Marcus <lmmailinglists(a)gmail.com> wrote: > On Fri, Aug 22, 2008 at 6:49 PM, Lanny Marcus <lmmailinglists(a)gmail.com> wrote: >> On Fri, Aug 22, 2008 at 3:48 PM, MHR <mhullrich(a)gmail.com> wrote: >>> On Fri, Aug 22, 2008 at 11:22 AM, Lanny Marcus <lmmailinglists(a)gmail.com> wrote: >>>> The version of Google Earth I installed last December was working >>>> great this morning. Then, I decided to update to the latest version >>>> and when I tried to do that with yum, I didn't have the right name for >>>> the package (now, I think it may be "google-earth"), so I downloaded >>>> the file (GoogleEarthLinux.bin) and installed with "sh >>>> GoogleEarthLinux.bin" The latest version is now installed and I can >>>> launch it, without any problem, but, it does not seem to >>>> work......... :-) >> >>> Where did you get this? >> >> Mark: I got it from google.com I have google among my yum >> repositories, but I couldn't remember what the package was called, so >> I >> couldn't "yum update" and I downloaded and installed their file, but >> it won't go. It isn't getting any date from the Google Earth servers. >> That >> worked perfectly, with the older version I had been using. Lanny >> > > I tried to install google-earth with yum but either that isn't the > name of the package or it is not available in the Google repository. > Then, I did some reading on the Google site. Question: How do I > determine whether or not the CPU in this box (I think it's an Intel > Celeron 2.6 GHz) supports SSE2 or not? I suspect the CPU does *not* > support SSE2. Posting some information below: > >>Hi Folks, > >>After taking a peek and looking at some of the issues in this thread: > >>http://groups.google.com/group/earth-linux/browse_thread/thread/b2a5e... > >>I thought you guys deserved an update. The long and short of it is >>that Google Earth 4.3 only works in Linux on machines with processors >>that support SSE2. This means a P4, A64, or greater is now required. I >>too was sad to see my little Athlon XP-M machine unable to run 4.3 >>with all of it's beautiful sunlight and atmosphere effects. > >>However, I'd like to let you know that we're aware of this and we're >>looking into getting 4.2 available for you folks! > >>Thanks for your patience, >>ERR <snip> SOLVED. I went back to the previous version of Google Earth for Linux. It must be that the Celeron CPU does *not* support SSE2. Previous version works great. :-) Google Earth 4.2.0205.5730 Build Date Nov 13 2007 Build Time 17:50:46 Renderer OpenGL Operating System Linux (2.6.18.1) Video Driver Tungsten Graphics, Inc Max Texture Size 2048x2048 Server kh.google.com User

1 0

CentOS position on systems intrusion at Red Hat
by Karanbir Singh 22 Aug '08

22 Aug '08

Earlier in the day today Red Hat made an announcement [1] that there had been an intrusion into some of their computer systems last week. In the same announcement they mention that some of the packages for OpenSSH on RHEL-4 ( i386 and x86_64 ) as well as RHEL-5 ( x86_64 ) were signed by the intruder. In their announcement they also clarified that they were confident that none of these, potentially compromised, packages made their way into or through RHN to client and customer machines. As a security measure a script [3] was made available along with a semi-detailed description of the issue [2]. We take security issues very seriously, and as soon as we were made aware of the situation I undertook a complete audit of the entire CentOS4/5 Build and Signing infrastructure. We can now assure everyone that no compromise has taken place anywhere within the CentOS Infrastructure. Our entire setup is located behind multiple firewalls, and only accessible from a very small number of places, by only a few people. Also included in this audit were all entry points to the build services, signing machines, primary release machines and connectivity between all these hosts. Since OpenSSH is a critical component of any Linux machine, we considered it essential to audit the last two released package sets ( openssh-4.3p2-26.el5.src.rpm, openssh-4.3p2-26.el5_2.1.src.rpm ). I have just finished this code audit, and can assure everyone that there is no compromised code included in either of these packages. A similar check is also being done for the CentOS-4 sources. Packages released today, by upstream, ( based on : openssh-4.3p2-26.el5_2.1.src.rpm, openssh-3.9p1-11.el4_7.src.rpm ) address two issues. Firstly they contain a fix for http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4752 . And secondly, in the remote event that someone had indeed got compromised packages via RHN, their packages would get updated to a known good state. We wanted to get these packages out right away to address the first issue, and also to cover users converting non updated RHEL installs to CentOS in the next few weeks/months. Release of these packages into the mirror.centos.org network does *not* imply that CentOS users are affected by the intrusion at Red Hat. Finally, while we feel confident that there is no possibility of this compromise having been passed onto the CentOS userbase, we still encourage users to verify their packages independently using whatever resources they might have available. -- [1]: https://rhn.redhat.com/errata/RHSA-2008-0855.html [2]: http://www.redhat.com/security/data/openssh-blacklist.html [3]: https://www.redhat.com/security/data/openssh-blacklist-1.0.sh :Its important to note that this script *only* checks for packages built within Red Hat, and will *not* be a reliable source of verification on CentOS since we rebuild from sources, using no Red Hat binary. -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net

1 0

Is there a way to save the routing table permanently?
by ABBAS KHAN 22 Aug '08

22 Aug '08

I'm adding the default gateway to the route through "route add default gw 10.10.10.10" which is also shown in "route -n" but the problem is that as soon as I restart the network through /etc/init.d/network restart; the route sets to default one...! SO, my question is there any way to save the modified route permanently by hardcoding the changes? Thanks.

13 24

Yum Issues with Dev groups
by Joseph L. Casale 22 Aug '08

22 Aug '08

Just my luck, None of my CentOS systems or my Fedora systems can #yum groupinstall "Development Tools" "Development Libraries"? Both are having dep issues? Is that a coincidence, or what's going on? The CentOS boxes all complain: --> Processing Dependency: glibc-common = 2.5-18.el5_1.1 for package: glibc Error: No Package Matching glibc.i686 jlc

4 12

Disk quotas for Sendmail
by Jussi Hirvi 22 Aug '08

22 Aug '08

Hi, CentOS 5.x, Sendmail 8.13.8. I would like to start using disk quotas on my Sendmail server, and optimally they should be configurable by user or group. How can this be done? (I tried to google, but no success.) - Jussi -- Jussi Hirvi * Green Spot Topeliuksenkatu 15 C * 00250 Helsinki * Finland Tel. & fax +358 9 493 981 * Mobile +358 40 771 2098 (only sms) jussi.hirvi(a)greenspot.fi * http://www.greenspot.fi

9 18

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss