Discuss

discuss@lists.centos.org

2 participants
34758 discussions

CentOS-announce Digest, Vol 136, Issue 6
by centos-announce-request＠centos.org 29 Jun '16

29 Jun '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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-2016:1349 CentOS 7 lvm2 BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jun 2016 00:12:11 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1349 CentOS 7 lvm2 BugFix Update Message-ID: <20160629001211.GA46363(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1349 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1349.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9f8f2152738415ddef6509c16881468f8abedf7488490bfe724561ee7eb582c7 cmirror-2.02.130-5.el7_2.5.x86_64.rpm e23f39c92b83682c140324b0891d426bf538fbdc68cf7f267c2a87356816d89c device-mapper-1.02.107-5.el7_2.5.x86_64.rpm 0c3dc7d9d7957e749ad019f06e0cc1c87f3db76cb500457050ce2c3e46080b8b device-mapper-devel-1.02.107-5.el7_2.5.i686.rpm 4da48171c8f599255dd47809d5ed2cdbd23afe152c44540e4e6c41bb88cf7f6b device-mapper-devel-1.02.107-5.el7_2.5.x86_64.rpm b1f004cceca52345c14d2dec35b44d989d39003d3a0e37ae14ee08210296e157 device-mapper-event-1.02.107-5.el7_2.5.x86_64.rpm 6a8203ef009bd1dae1c2575bfaa89582a5d9b402e9a450ce3a787c22ead8f4a6 device-mapper-event-devel-1.02.107-5.el7_2.5.i686.rpm a2a822a1de226771fd00b9d6bce566def68a67b5c4ef1351f7d4e756a3d23e03 device-mapper-event-devel-1.02.107-5.el7_2.5.x86_64.rpm 44d8c251698d60f8bf82d71d774652c7743515edd9077a780bb33709303188e6 device-mapper-event-libs-1.02.107-5.el7_2.5.i686.rpm 59b65674dcab344b3d219b6961722bfd40780455bc0bce6bd02edd6dd768453c device-mapper-event-libs-1.02.107-5.el7_2.5.x86_64.rpm 8475f1a20a99c5f1d041187a531b5c5406c67bf84afb926096d11810f1a53d8e device-mapper-libs-1.02.107-5.el7_2.5.i686.rpm 4d964e6a7643010f2862791e2588e08f6011e4c656540d61d3ebe937ac9ce13a device-mapper-libs-1.02.107-5.el7_2.5.x86_64.rpm b7a90ef80f4e8ddb35257802a57c07660e1ddc7e2c4a9957edf382ff67ec1567 lvm2-2.02.130-5.el7_2.5.x86_64.rpm 65a4c81480d0efba21f0da7969a2f820d69e26934af24bf4fdb8c449a2d502dc lvm2-cluster-2.02.130-5.el7_2.5.x86_64.rpm 04d6d35438ff31602702872775f9fdc758c94d1e9656319dcfa09580ef21609d lvm2-devel-2.02.130-5.el7_2.5.i686.rpm e53af702e6143a89598e64754410bbdbb079fb3e5b657091d88f44fec28fa391 lvm2-devel-2.02.130-5.el7_2.5.x86_64.rpm abafec8cbed90c9e68a796b61235bab160be70a8d0a8290041d78c155d41804e lvm2-libs-2.02.130-5.el7_2.5.i686.rpm 6c0f6537d19eecc549c1c7adf01cdee3aa6d805b30496946fbcc73cb4b3fe582 lvm2-libs-2.02.130-5.el7_2.5.x86_64.rpm 39727f939e993c9baac491080ef3901b3d18536c3c4a7e12668bf381f15f99e9 lvm2-lockd-2.02.130-5.el7_2.5.x86_64.rpm 2f3b320f5108eef429344b89416a2fcf6e15a47e014faeff5b47c6a3ebe234a3 lvm2-python-libs-2.02.130-5.el7_2.5.x86_64.rpm 53316ba2995b27f5b7a4137817a66cd811c42c4ce286e682869d565f5bae76be lvm2-sysvinit-2.02.130-5.el7_2.5.x86_64.rpm Source: 399d8210953038b445e7ac3fc91fc13b517b11dc1a849f820f17296a27477a56 lvm2-2.02.130-5.el7_2.5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 136, Issue 6 ***********************************************

1 0

Errors on yum upgrade
by henimp＠openmail.cc 28 Jun '16

28 Jun '16

During yum upgrade a couple days ago, I saw this: Cleanup : kernel-3.10.0-229.20.1.el7.x86_64 35/64 warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.softdep: remove failed: No such file or directory warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.devname: remove failed: No such file or directory Should I be concerned about this? What could have caused it? ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

2 2

Re: [CentOS] UDP Constant IP Identification Field Fingerprinting Vulnerability
by James B. Byrne 28 Jun '16

28 Jun '16

On Mon, June 27, 2016 12:29, Gordon Messmer wrote: > On 06/26/2016 01:50 PM, James B. Byrne wrote: >> However, all I am seeking is knowledge on how to handle this using >> iptables. I am sure that this defect/anomaly has already been >> solved wherever it is an issue. Does anyone have an example on >> how to do this? > > > I think the bit you're missing is that you don't have to address every > detail that your auditors send you. You can label an item a false > positive. You can respond that you are aware, and that you don't > consider an item to be a security defect. Fingerprinting is an > excellent example thereof. As was already noted, the IP ID field is > just one of many aspects of IP networking that can be used to identify > Linux systems. If you don't address them all, addressing one is not a > useful exercise. I understand WRT false positive flagging. And that is exactly what I have done. However, the PCI DSS report piqued my interest in this matter and I thought to satisfy my curiosity. The other stuff flagged in the report seemed a little far-fetched to me. At least the explanation of why they were flagged did. As none of them affect our PCI status I have no interest in the rest. This one however I was previously unaware and so I wanted to discover more about it. Thank you for the information and especially for the references. Sincerely, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail 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

Guest's Additions Virtual CD
by raving Joker 28 Jun '16

28 Jun '16

Hello to everyone I'm a new italian member so I'm sorry if my english isn't perfect. I was thinking... Why not (in CentOS 7) insert a tab in the installation phase that can permit an automatic installation of guest's additions tools (I'm using virtualbox, but it can be applied to other platforms with a menu), a little system that reveals the guest addition's cd and if isn't inserted, displays to the user a message with informations about how insert it and do the installation automatically? Thanks for all of people that want to reply, I know that this virtualization platforms are in part in discordance with the ethical free software's mindset...but why not in centos, with proper informative messages? Good afternoon Raving

1 0

Use USB2.0 Camera with KVM based VM
by Mark LaPierre 28 Jun '16

28 Jun '16

Hey All, I've been googleing this issue for hours but I can't find a workable solution. I found a reply to a bug posting that said the USB hub on the VM defaults to USB 1.1. I see this is true when I lsusb on the CentOS 7 guest. The reply to the bug post went on to say that the problem is that the USB 2.0 camera will not work with the USB 1.1 default hub and that I should change the hub from USB 1.1 to USB 2.0. I see no way to do that. Can anyone shed some light on this? Is there a way to change the USB hub from USB 1.1 to USB 2.0 inside the VM Manager? Is there a better way to get my USB 2.0 web camera to appear in my CentOS 7 guest? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 1

Re: [CentOS] UDP Constant IP Identification Field Fingerprinting Vulnerability
by James B. Byrne 27 Jun '16

27 Jun '16

On Fri, June 24, 2016 12:24, John R Pierce wrote: > On 6/24/2016 9:20 AM, James B. Byrne wrote: >> We received a notice from our pci-dss auditors respecting this: >> >> CVE-2002-0510 The UDP implementation in Linux 2.4.x kernels keeps >> the >> IP Identification field at 0 for all non-fragmented packets, which >> could allow remote attackers to determine that a target system is >> running Linux. > > > 2.4 kernels are kinda old. kinda really really old. are you still > running CentOS 4 on PCI audited systems ?!?? > > The CVE is from 2002 and the kernel mentioned refers to the original report. Linux core team said it was a non-problem and the issue remains in the kernel found in CentOS-6.8. Possibly the one in 7. Perhaps it is still present in the development branch. However, all I am seeking is knowledge on how to handle this using iptables. I am sure that this defect/anomaly has already been solved wherever it is an issue. Does anyone have an example on how to do this? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail 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

haproxy + Apache + virtual hosts -> wrong host is displayed
by Alexander Farber 24 Jun '16

24 Jun '16

Hello, I hope my question is not off-topic here. On CentOS 7.2.1511 I have installed: haproxy-1.5.14-3.el7.x86_64 httpd-2.4.6-40.el7.centos.1.x86_64 The /etc/haproxy/haproxy.cfg binds HAProxy to ports 80 and 443 and accepts HTTPS to slova.de: defaults mode http option http-server-close option forwardfor except 127.0.0.0/8 option redispatch .... frontend public bind 144.76.184.151:80 bind 144.76.184.151:443 ssl crt /etc/pki/tls/certs/slova.de.pem reqidel ^X-Forwarded-Proto: reqidel ^X-Forwarded-For: reqadd X-Forwarded-Proto:\ https if { ssl_fc } option forwardfor default_backend apache backend apache server domain 127.0.0.1:8080 The /etc/httpd/conf/httpd.conf binds Apache to port 8080 and serves several Wordpress sites: Listen 127.0.0.1:8080 ServerName 144.76.184.151 <VirtualHost 127.0.0.1:8080> DocumentRoot /var/www/html/afarber.de ServerName afarber.de ErrorLog logs/afarber.de/error_log CustomLog logs/afarber.de/access_log common </VirtualHost> <VirtualHost 127.0.0.1:8080> DocumentRoot /var/www/html/ruhrgebietsingle.de ServerName ruhrgebietsingle.de ErrorLog logs/ruhrgebietsingle.de/error_log CustomLog logs/ruhrgebietsingle.de/access_log common </VirtualHost> <VirtualHost 127.0.0.1:8080> DocumentRoot /var/www/html/bukvy.de ServerName bukvy.de ErrorLog logs/bukvy.de/error_log CustomLog logs/bukvy.de/access_log common </VirtualHost> <VirtualHost 127.0.0.1:8080> DocumentRoot /var/www/html/slova.de ServerName slova.de ErrorLog logs/slova.de/error_log CustomLog logs/slova.de/access_log common </VirtualHost> When I open http://slova.de or https://www.slova.de they work fine. But when I try to open same URLs with "www." prepended, the browser displays http://ruhrgebietsingle.de (the 2nd site out of 4) Why does it happen? I just can not figure it out. What tool would help here to debug? Thank you Alex

1 1

UDP Constant IP Identification Field Fingerprinting Vulnerability
by James B. Byrne 24 Jun '16

24 Jun '16

We received a notice from our pci-dss auditors respecting this: CVE-2002-0510 The UDP implementation in Linux 2.4.x kernels keeps the IP Identification field at 0 for all non-fragmented packets, which could allow remote attackers to determine that a target system is running Linux. The NVD entry for which contains this note: CHANGE> [Cox changed vote from REVIEWING to NOOP] Cox> So I asked some kernel guys about this - it's not considered an issue. There are several other ways to identify Linux on the wire and people who care about this kind of thing rewrite their packets in various ways via firewall technology to trick the identifier programs. So, what packet mangling may be done in iptables to solve this without breaking udp transmission? I take it that we are talking about something in the prerouting chain but what kind of mangelling is safe? Is there an example somewhere? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail 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

CPU Compatibility Question
by listmail 23 Jun '16

23 Jun '16

Hi All, Hopefully someone with broad overview of CentOS compatibility issues can comment on this: I am evaluating a Supermicro X10SLM motherboard with an Intel E3-1231 v3 CPU. Testing with boots from Live DVDs, the CentOS 6.x family is panicking at boot time. I have tried 6.8, 6.5, and 6.3, and each one panics at slightly different points, but they all seem to fail after udev starts up (or tries to). On the other hand, I was able to boot CentOS 7.0 1511 from the Live CD. According to the compatibility chart over here: https://access.redhat.com/support/policy/intel ...anything later than 6.3 (6.4 and up) should work with the E3-12xx v3 family of processors. But those are not the results I am seeing. Does anyone have experience or commentary on this compatibility issue? Thanks, --Bill

2 2

sssd.conf file missing
by Kaplan, Andrew H. 23 Jun '16

23 Jun '16

Hello -- We are running CentOS 7.2 on a virtual machine, and we are trying to set up LDAP authentication. The ldap packages that are currently installed on the system are the following: python-sss 1.13.0-40.el7_2.4 python-sssdconfig 1.13.0-40.el7_2.4 sssd 1.13.0-40.el7_2.4 sssd-ad 1.13.0-40.el7_2.4 sssd-client 1.13.0-40.el7_2.4 sssd-common 1.13.0-40.el7_2.4 sssd-common-pac 1.13.0-40.el7_2.4 sssd-dbus 1.13.0-40.el7_2.4 sssd-ipa 1.13.0-40.el7_2.4 sssd-krb5 1.13.0-40.el7_2.4 sssd-krb5-common 1.13.0-40.el7_2.4 sssd-ldap 1.13.0-40.el7_2.4 sssd-libwbclient 1.13.0-40.el7_2.4 sssd-libwbclient-devel 1.13.0-40.el7_2.4 sssd-proxy 1.13.0-40.el7_2.4 sssd-tools 1.13.0-40.el7_2.4 I ran the following commands to set up LDAP/AD authentication: # ln -s /bin/bash /bin/PHSshell # ln -s /home /PHShome # authconfig --enablesssdauth --enablemkhomedir --enablesssd -update # chkconfig sssd on # service sssd restart Initially, I ran into problems because I had not created an sssd.conf file. Eventually I did create one, and its contents are the following: [<domain>.org] enumate = true cache_credentials = TRUE id_provider = ldap auth_provider = ldap chpass_provider = ldap ldap_uri = ldap://ldap.<domain>.org ldap_search_base = dc=<domain>,dc=org tls_reqcert = demand ldap_tls_cacert /etc/pki/tls/certs/ca-bundle.crt If there are any additions or corrections that I need to make, please let me know. I reran the service sssd restart command, and the error message that I am seeing via journalctl -xe is the following: Unit sssd.service has begun starting up. Jun 22 16:05:34 roadtest2.partners.org sssd[6384]: SSSD couldn't load the configuration database [5]: Input/output error. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: sssd.service: control process exited, code=exited status=4 Jun 22 16:05:34 roadtest2.partners.org systemd[1]: Failed to start System Security Services Daemon. -- Subject: Unit sssd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman.../systemd-devel<http://lists.freedesktop.org/mailman/listinfo/systemd-devel> -- -- Unit sssd.service has failed. -- -- The result is failed. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: Unit sssd.service entered failed state. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: sssd.service failed. Jun 22 16:05:34 roadtest2.partners.org polkitd[787]: Unregistered Authentication Agent for unix-process:6369:52587318 (system bus name :1.2287, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Any ideas? The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

2 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