Discuss

discuss@lists.centos.org

34753 discussions

SELInux and POSTFIX
by James B. Byrne 23 Apr '14

23 Apr '14

Installed Packages Name : postfix Arch : x86_64 Epoch : 2 Version : 2.6.6 Release : 6.el6_5 Size : 9.7 M Repo : installed >From repo : updates I am seeing several of these in our maillog file after a restart of the Postfix service: Apr 23 12:48:27 inet08 setroubleshoot: SELinux is preventing /usr/libexec/postfix/smtp from 'read, write' accesses on the file 546AA6099F. For complete SELinux messages. run sealert -l b95663bb-12ce-4f34-9537-dd88a41359e5 sealert -l b95663bb-12ce-4f34-9537-dd88a41359e5 SELinux is preventing /usr/libexec/postfix/smtp from 'read, write' accesses on the file 546AA6099F. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that smtp should be allowed read write access on the 546AA6099F file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep smtp /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp grep 546AA6099F /var/log/audit/audit.log | audit2why type=AVC msg=audit(1398199187.646:29332): avc: denied { getattr } for pid=23387 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398199187.646:29333): avc: denied { read write } for pid=23387 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398199927.800:29411): avc: denied { getattr } for pid=24131 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398199927.805:29412): avc: denied { read write } for pid=24131 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398201500.778:29495): avc: denied { getattr } for pid=25406 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398201500.779:29496): avc: denied { read write } for pid=25406 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398204425.415:29681): avc: denied { getattr } for pid=26964 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398204425.419:29682): avc: denied { read write } for pid=26964 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398208625.418:29910): avc: denied { getattr } for pid=29240 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398208625.419:29911): avc: denied { read write } for pid=29240 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398212826.339:30139): avc: denied { getattr } for pid=31325 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398212826.343:30140): avc: denied { read write } for pid=31325 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398217026.114:30368): avc: denied { getattr } for pid=855 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398217026.114:30369): avc: denied { read write } for pid=855 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398221225.239:30628): avc: denied { getattr } for pid=2652 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398221225.240:30629): avc: denied { read write } for pid=2652 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398225425.850:30863): avc: denied { getattr } for pid=4556 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398225425.851:30864): avc: denied { read write } for pid=4556 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398229625.107:31116): avc: denied { getattr } for pid=6545 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398229625.108:31117): avc: denied { read write } for pid=6545 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398233825.788:31345): avc: denied { getattr } for pid=8322 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398233825.789:31346): avc: denied { read write } for pid=8322 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398238025.329:31580): avc: denied { getattr } for pid=10706 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398238025.329:31581): avc: denied { read write } for pid=10706 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398242226.269:31819): avc: denied { getattr } for pid=12510 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398242226.272:31820): avc: denied { read write } for pid=12510 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398246425.661:32081): avc: denied { getattr } for pid=14363 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398246425.663:32082): avc: denied { read write } for pid=14363 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398250626.380:32316): avc: denied { getattr } for pid=16384 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398250626.381:32317): avc: denied { read write } for pid=16384 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398254826.134:32581): avc: denied { getattr } for pid=18686 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398254826.136:32582): avc: denied { read write } for pid=18686 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398259025.251:32834): avc: denied { getattr } for pid=20593 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398259025.252:32835): avc: denied { read write } for pid=20593 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398263323.263:33063): avc: denied { getattr } for pid=23647 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398263323.263:33064): avc: denied { read write } for pid=23647 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398267592.473:33300): avc: denied { getattr } for pid=27690 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398267592.474:33301): avc: denied { read write } for pid=27690 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398271701.024:33555): avc: denied { getattr } for pid=31449 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398271701.025:33556): avc: denied { read write } for pid=31449 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398271701.025:33556): avc: denied { open } for pid=31449 comm="smtp" name="546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. type=AVC msg=audit(1398271701.025:33557): avc: denied { lock } for pid=31449 comm="smtp" path="/var/spool/postfix/active/546AA6099F" dev=dm-0 ino=395679 scontext=unconfined_u:system_r:postfix_smtp_t:s0 tcontext=unconfined_u:object_r:postfix_spool_maildrop_t:s0 tclass=file Was caused by: Missing type enforcement (TE) allow rule. You can use audit2allow to generate a loadable module to allow this access. Is this the result of something I may have done like restarting postfix or is this a real bug/error/defect/? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Re: [CentOS] Yum cannot download from local repository
by James B. Byrne 23 Apr '14

23 Apr '14

On Tue, April 22, 2014 13:54, Phoenix, Merka wrote: > > Your local file-based repo area is missing the 'mod_ssl' RPM that 'httpd' > depends on (and has requested that be updated). Because you have excluded all > the other repos where the 'mod_ssl' might be found (or perhaps they do not > have the required version matching your httpd packages), the update fails > because the dependenc(y)s cannot be downloaded. > Because of the size of the listing I did not show the entire contents of the local repo. However, mod_ssl is indeed present: ll /root/RPMS/repos/Packages total 39856 -rw-rw-r--. 1 root root 92768 Apr 21 16:15 apr-1.5.0-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 413768 Apr 21 16:15 apr-debuginfo-1.5.0-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 825424 Apr 21 16:15 apr-devel-1.5.0-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 77588 Apr 21 16:15 apr-util-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 7136 Apr 21 16:15 apr-util-dbm-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 433748 Apr 21 16:15 apr-util-debuginfo-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 489160 Apr 21 16:15 apr-util-devel-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 12216 Apr 21 16:15 apr-util-freetds-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 9068 Apr 21 16:15 apr-util-ldap-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 14904 Apr 21 16:15 apr-util-mysql-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 11084 Apr 21 16:15 apr-util-nss-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 20644 Apr 21 16:15 apr-util-odbc-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 10360 Apr 21 16:15 apr-util-openssl-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 14848 Apr 21 16:15 apr-util-pgsql-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 11408 Apr 21 16:15 apr-util-sqlite-1.5.3-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 1151252 Apr 21 16:15 httpd-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 3415444 Apr 21 16:15 httpd-debuginfo-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 186000 Apr 21 16:15 httpd-devel-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 3300912 Apr 21 16:15 httpd-manual-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 69784 Apr 21 16:15 httpd-tools-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 43412 Apr 21 16:15 mod_authnz_ldap-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 42292 Apr 21 16:15 mod_lua-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 22304 Apr 21 16:15 mod_proxy_html-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 80708 Apr 21 16:15 mod_ssl-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 1234596 Apr 21 16:15 php-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 34472 Apr 21 16:15 php-bcmath-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 2284236 Apr 21 16:15 php-cli-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 536152 Apr 21 16:15 php-common-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 40832 Apr 21 16:15 php-dba-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 20211088 Apr 21 16:15 php-debuginfo-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 519364 Apr 21 16:15 php-devel-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 1170188 Apr 21 16:15 php-embedded-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 28656 Apr 21 16:15 php-enchant-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 1197048 Apr 21 16:15 php-fpm-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 107872 Apr 21 16:15 php-gd-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 50636 Apr 21 16:15 php-imap-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 71512 Apr 21 16:15 php-intl-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 38196 Apr 21 16:15 php-ldap-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 465136 Apr 21 16:15 php-mbstring-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 82212 Apr 21 16:15 php-mysql-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 51020 Apr 21 16:15 php-odbc-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 75980 Apr 21 16:15 php-pdo-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 70844 Apr 21 16:15 php-pgsql-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 39208 Apr 21 16:15 php-process-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 28204 Apr 21 16:15 php-pspell-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 24912 Apr 21 16:15 php-recode-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 30684 Apr 21 16:15 php-snmp-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 142412 Apr 21 16:15 php-soap-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 35956 Apr 21 16:15 php-tidy-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 104684 Apr 21 16:15 php-xml-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 52796 Apr 21 16:15 php-xmlrpc-5.3.3-27.el6.x86_64.rpm -rw-rw-r--. 1 root root 1230648 Apr 21 16:15 php-zts-5.3.3-27.el6.x86_64.rpm -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Re: [CentOS] Samba4 questions
by James B. Byrne 23 Apr '14

23 Apr '14

On Tue, April 22, 2014 15:02, John R Pierce wrote: > > In Microsoft's Active Directory, you put users and systems in "OU" > (Organizational Units), and each OU can have group policies and those > policies can specify login scripts, these can do things like map network > drives for users. Presumably, Samba's implementation of AD offers a > similar facility, but I don't think the domain management tools in Samba > are anywhere near as well integrated or full featured as what you get > with a Windows Server system. >From what I have read on the subject the recommended path for Samba4 management is to install MicroSoft's Remote Server Administration Tools for Windows X package, where X is whatever version of MS-Windows you run as a domain member workstation client. Earlier forms of the software were called Windows Server Y Administrative Tools Pack where Y refers to the server version (2000, 2003, etc.) -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

CentOS-announce Digest, Vol 110, Issue 10
by centos-announce-request＠centos.org 23 Apr '14

23 Apr '14

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. CEBA-2014:0418 CentOS 6 mod_perl Update (Johnny Hughes) 2. CESA-2014:0420 Moderate CentOS 6 qemu-kvm Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 22 Apr 2014 12:51:09 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0418 CentOS 6 mod_perl Update To: centos-announce(a)centos.org Message-ID: <20140422125109.GA1429(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0418 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0418.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4316370de36fc875ae36e399a7b4cda3847431146e4857a58249275f08438f34 mod_perl-2.0.4-11.el6_5.i686.rpm d00e4be220ec8d9c26ffbf8d65469ee24f54a1d3e7ffff6dc743eed23e3d5306 mod_perl-devel-2.0.4-11.el6_5.i686.rpm x86_64: 88a1a9b239cbbc3040e667a7cb32174adf12b18a11ee1789c9f75000ef2eb484 mod_perl-2.0.4-11.el6_5.x86_64.rpm d00e4be220ec8d9c26ffbf8d65469ee24f54a1d3e7ffff6dc743eed23e3d5306 mod_perl-devel-2.0.4-11.el6_5.i686.rpm b7f0f240028c94068e85eee657867b79a18ecaba9284e0636b589d2a4cc690ba mod_perl-devel-2.0.4-11.el6_5.x86_64.rpm Source: cccf2e8adbd28e0d5bcea5ab152717c693fe5abfb158d0ec1665d1cf87afd66f mod_perl-2.0.4-11.el6_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Tue, 22 Apr 2014 19:33:34 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0420 Moderate CentOS 6 qemu-kvm Update To: centos-announce(a)centos.org Message-ID: <20140422193334.GA12774(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0420 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0420.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3d26ffa6309a56e28f76509d1e8704df500e1d3ad1c491e9badf1b13acb39407 qemu-guest-agent-0.12.1.2-2.415.el6_5.8.i686.rpm x86_64: 94318b4e741fe5fe04d9e912e13fd0e3b4049890f65dda0de62a7b5c567d6308 qemu-guest-agent-0.12.1.2-2.415.el6_5.8.x86_64.rpm 0b46e8d8ae7bad28c9735ad8da6c811ae0bd09593f8976a412ac5539abfb9a38 qemu-img-0.12.1.2-2.415.el6_5.8.x86_64.rpm ecad0afea1d719457c51f2917e0d6f00c8436cdb0a749228735742580b48433b qemu-kvm-0.12.1.2-2.415.el6_5.8.x86_64.rpm e1c095bf9d502eb27c0991b140fccdcd64c55a5cf5c5254243ce592dbed0951e qemu-kvm-tools-0.12.1.2-2.415.el6_5.8.x86_64.rpm Source: 66d7ad0ba8656f67e55f0a641a0d3e6da3b68132d2ee02b3511250b413fc9fac qemu-kvm-0.12.1.2-2.415.el6_5.8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #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 110, Issue 10 ************************************************

1 0

Starting the gotour server on CentOS 6
by Evan Rowley 23 Apr '14

23 Apr '14

Hey CentOS folks! I have an interesting issue with starting a server on a CentOS 6 KVM guest. The server (service) in particular is gotour, which is a web application created by Google and their Golang developers, intended to teach users the basics of using the Go programming langauge. When starting gotour, the program claims to be binding to port 12049, but the VM doesn't seem to be serving anything on that port. Upon checking the netstat output, I see a process bound to port 12049. It is definitley possible that the problem is with Go itself, but I'd like to rule out the possibility that something on an out-of-the-box CentOS 6 image might be preventing the server from working. Here is some of the output: [appengine@centos6-paas-dev gotour]$ gotour 2014/04/17 22:04:33 Serving content from /home/appengine/goprojects/firstproj/go/src/code.google.com/p/go-tour 2014/04/17 22:04:33 WARNING! WARNING! WARNING! I appear to be listening on an address that is not localhost. Anyone with access to this address and port will have access to this machine as the user running gotour. If you don't understand this message, hit Control-C to terminate this process. WARNING! WARNING! WARNING! 2014/04/17 22:04:34 Please open your web browser and visit http://10.10.10.205:12049 [root@centos6-paas-dev ~]# netstat -pnaevZ Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name Security Context ... tcp 0 0 10.10.10.205:12049 0.0.0.0:* LISTEN 505 224898 9331/gotour fined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 [appengine@centos6-paas-dev gotour]$ getenforce Permissive Any ideas? -- - EJR

7 10

Re: [CentOS] Samba4 questions
by Alain Péan 22 Apr '14

22 Apr '14

Le 22/04/2014 21:54, Reindl Harald a écrit : >> I think you should wait for RHEL 7 (and then CentOS 7), which will be >> >released soon (June ?). Perhaps, it well include samba4 without anything >> >to build from source > not perhaps, for sure > > samba-4.1.0-3.el7.x86_64 > samba-client-4.1.0-3.el7.x86_64 > samba-common-4.1.0-3.el7.x86_64 > samba-libs-4.1.0-3.el7.x86_64 > I notice it is "samba-common-4....", so samba 4 will be the default in RHEL 7, not samba 3.6.x ? Alain

1 0

Yum cannot download from local repository
by James B. Byrne 22 Apr '14

22 Apr '14

I have set up a local filesystem repo thus: # cat /etc/yum.repos.d/LocalFiles.repo # LocalFiles.repo # # This repo is used with rpms contained in a local filesystem repo # created with createrepo. You can use this repo and yum to install # items directly off the local disk. # # To use this repo with the other repos: # yum --enablerepo=localfiles yum --nogpgcheck <yum command> # # or to ONLY this repo, do this: # # yum --disablerepo=\* --enablerepo=localfiles <yum command> [localfiles] name=CentOS-$releasever - Local Files baseurl=file:///root/RPMS/repos/ enabled=0 gpgcheck=0 In /root/RPMS/repos/ I have this: ll /root/RPMS/repos/ total 8 drwxr-xr-x. 2 root root 4096 Apr 21 16:17 Packages drwxr-xr-x. 2 root root 4096 Apr 21 15:57 repodata And in /root/RPMS/repos/Packages I have this: ll /root/RPMS/repos/Packages/http* -rw-rw-r--. 1 root root 1151252 Apr 21 16:15 /root/RPMS/repos/Packages/httpd-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 3415444 Apr 21 16:15 /root/RPMS/repos/Packages/httpd-debuginfo-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 186000 Apr 21 16:15 /root/RPMS/repos/Packages/httpd-devel-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 3300912 Apr 21 16:15 /root/RPMS/repos/Packages/httpd-manual-2.4.9-1.el6.x86_64.rpm -rw-rw-r--. 1 root root 69784 Apr 21 16:15 /root/RPMS/repos/Packages/httpd-tools-2.4.9-1.el6.x86_64.rpm Yet when I try to install or upgrade using yum I get a download error: # yum --enablerepo=localfiles --nogpgcheck update httpd Loaded plugins: downloadonly, fastestmirror, priorities, refresh-packagekit Loading mirror speeds from cached hostfile * Webmin: download.webmin.com * base: less.cogeco.net * epel: mirror.steadfast.net * extras: centos.mirror.ca.planethoster.net * rpmforge: repoforge.mirror.constant.com * updates: centos.mirror.rafal.ca Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package httpd.x86_64 0:2.2.15-30.el6.centos will be updated --> Processing Dependency: httpd-mmn = 20051115 for package: 1:mod_ssl-2.2.15-30.el6.centos.x86_64 --> Processing Dependency: httpd = 2.2.15-30.el6.centos for package: 1:mod_ssl-2.2.15-30.el6.centos.x86_64 ---> Package httpd.x86_64 0:2.4.9-1.el6 will be an update --> Running transaction check ---> Package mod_ssl.x86_64 1:2.2.15-30.el6.centos will be updated ---> Package mod_ssl.x86_64 1:2.4.9-1.el6 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Updating: httpd x86_64 2.4.9-1.el6 localfiles 1.1 M Updating for dependencies: mod_ssl x86_64 1:2.4.9-1.el6 localfiles 79 k Transaction Summary ================================================================================ Upgrade 2 Package(s) Total download size: 1.2 M Is this ok [y/N]: y Downloading Packages: Error Downloading Packages: httpd-2.4.9-1.el6.x86_64: failure: Packages/httpd-2.4.9-1.el6.x86_64.rpm from localfiles: [Errno 256] No more mirrors to try. 1:mod_ssl-2.4.9-1.el6.x86_64: failure: Packages/mod_ssl-2.4.9-1.el6.x86_64.rpm from localfiles: [Errno 256] No more mirrors to try. Any ideas on what I am doing wrong? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Module building and signing
by Chris Pemberton 22 Apr '14

22 Apr '14

In order to get "Beats Audio" (2.1 channel sound) working on my HP k025dx laptop running CentOS 6.5, I need to re-assign some of the pins on the Intel HDA soundcard - model 92HD91BXX. This is trivial in newer distros for two reasons: 1. the 'hda-jack-retask' application compiles and runs on newer distros 2. the snd-hda-intel modules on newer distros are compiled with CONFIG_SND_HDA_RECONFIG=y Even if I could get 'hda-jack-retask' to compile, I'd still need the module built with CONFIG_SND_HDA_RECONFIG=y. So I followed the 2 wiki articles to install full kernel sources and I re-compiled the module. When loading the new module, I get the following error: FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.32-431.11.2.el6.x86_64/extra/snd-hda-intel.ko): Invalid module format I run 'file' on the new and original modules and they seem identical: /lib/modules/2.6.32-431.11.2.el6.x86_64/extra/snd-hda-intel.ko: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped /lib/modules/2.6.32-431.11.2.el6.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped My next attempt was to compile an entire kernel, and then copy the new module over to the original kernel. Inserting the module give the following: Module signed with unknown public key ksign: module signed with unknown public key - signature keyid: 3000b37e8a34083d ver=4 I googled for a fix and tried two methods of removing the module signing (neither worked): objcopy -R .note.module_sig snd-hda-intel.ko objcopy -R .module_sig snd-hda-intel.ko (I did get finally get the audio pins re-mapped, but I had to resort to using my newly-compiled kernel as well). Should kmod fix my issues? Thanks, Chris

1 0

Does anyone use tcp wrappers (hosts.allow/hosts.deny) anymore?
by Matthew Miller 22 Apr '14

22 Apr '14

Does anyone use tcp wrappers (hosts.allow/hosts.deny) anymore? And, would you care strongly if it went away (or would you just migrate to something else)? I bring this up because we are discussing dropping it from Fedora. This would be far enough in the future that it wouldn't impact RHEL 7, and therefore won't affect anyone here for Quite Some Time*, but here in the new world order of CentOS, I thought it might be useful to check with some actual downstream users. What do you think? Do you rely on hosts.allow/hosts.deny a primary security mechanism? As defense-in-depth? Do you have policies which mandate it? Your feedback appreciated. Thanks! * and the standard caveats that Fedora doesn't necessarily determine the path for RHEL apply, of course. -- Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>

26 53

nfs question
by Barbara Krasovec 22 Apr '14

22 Apr '14

Hello! We have central ldap for users, idmapd.conf configured on every machine and users' home folders on nfs, mounted by automount on several machines. After the last OS upgrade we notice that permissions on some files (not for all users) are corrupted: For example: -rw-r--r-- 1 4294967294 4294967294 45 Nov 11 21:20 hostlist drwx------ 2 4294967294 4294967294 4096 Jun 27 2012 .ssh -rw-r--r-- 1 4294967294 4294967294 0 Aug 28 2013 test -rw-r--r-- 1 4294967294 4294967294 53 Jan 6 12:44 test.sh instead of: -rw-r--r-- 1 ops001 ops 45 Nov 11 21:20 hostlist drwx------ 2 ops001 ops 4096 Jun 27 2012 .ssh -rw-r--r-- 1 ops001 ops 0 Aug 28 2013 test -rw-r--r-- 1 ops001 ops 53 Jan 6 12:44 test.sh Kernel used: 2.6.32-431.11.2.el6.x86_64 Nfs version: nfs-utils-1.2.3-39.el6.x86_64 User/group mapping works fine. Same behaviour appears when I mount the home folder manually. Any ideas? Thanks, Barbara

1 1

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