Discuss June 2018

discuss@lists.centos.org

93 participants
86 discussions

Questions about yum-cron
by Nicolas Kovacs 03 Jun '18

03 Jun '18

Hi, Up until now I always kept my servers up-to-date manually. Currently I'm experimenting with yum-cron to automate this process. I read through various online tutorials, and now I have a couple questions. 1. As far as I know, when editing /etc/yum/yum-cron.conf, I can only use the following value for update_cmd : update_cmd = default If I understand this correctly, 'update_cmd = security' would have no effect, since contrary to RHEL, CentOS doesn't provide the necessary metadata to operate the distinction between security updates and other updates like mere bugfixes. Please correct me if I'm wrong. 2. It looks like editing /etc/yum/yum-cron.conf affects a *daily* operation of yum-cron, whereas editing /etc/yum/yum-cron- hourly.conf provides hourly operations. The documentation is not very clear about this, and I'm a little confused here. In other words, yum-cron.conf affects /etc/cron.daily/0yum-daily.cron, and yum-cron-hourly.conf affects /etc/cron.hourly/0yum-hourly.cron. I only really need yum-cron to run once a day, which would be sufficient. That being said, I can't figure out at what time it launches. All my users are in France, so ideally the daily yum-cron should be launched somewhere between 04:00 and 05:00 AM, since updating a package like httpd would restart the corresponding processes and kick online users out. I can't seem to figure out a way to define the exact time at which the daily yum-cron is being launched, since this doesn't seem to be controlled by standard crontab. Any suggestions ? Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 1

Package security scanner for CentOS docker containers
by Traiano Welcome 03 Jun '18

03 Jun '18

Hi List, I’m looking for a command line package security scanner for CentOS docker containers. Is there any utility out there for checking alpine packages in an alpine docker container against the cve database? Tools similar to debsecan would be ideal (https://github.com/allthings/ debsecan), i.e a tool that can be launched from the host machine, will connect to a container on the host, or start up a docker image on the hosts, scan the packages and report CVEs relevant to each package. Thanks in advance, Traiano

1 0

LVM GUI in live CD
by Miguel Gonzalez 02 Jun '18

02 Jun '18

Hi, I am searching around and I can´t find any GUI LVM manager included in a Centos live CD. I am trying to resize a LVM partition in a Centos 6.9 machine with a live CD. If I need any other distro, It´s fine with me Thanks! Miguel

4 4

CentOS-announce Digest, Vol 160, Issue 1
by centos-announce-request＠centos.org 02 Jun '18

02 Jun '18

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. CEEA-2018:1774 CentOS 6 microcode_ctl Enhancement Update (Johnny Hughes) 2. CESA-2018:1777 Important CentOS 6 procps Security Update (Johnny Hughes) 3. CESA-2018:1779 Important CentOS 6 xmlrpc3 Security Update (Johnny Hughes) 4. CEEA-2018:1771 CentOS 7 linux-firmware Enhancement Update (Johnny Hughes) 5. CESA-2018:1780 Important CentOS 7 xmlrpc Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 1 Jun 2018 15:11:29 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2018:1774 CentOS 6 microcode_ctl Enhancement Update Message-ID: <20180601151129.GA48963(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2018:1774 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1774 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e931f163e9536a55e4ce801be0a99e186664f8133888edaf7ade5846824f4422 microcode_ctl-1.17-25.7.el6_9.i686.rpm x86_64: c458d93f0a6aab4ab68c11304c8c3d5dd9972bf97d497539e2459a0cca9aed0f microcode_ctl-1.17-25.7.el6_9.x86_64.rpm Source: 55c74ae1211a4790d87dcd9b4b363bd5e1c09e5cb81b4d17bfef5c9dcf7faa20 microcode_ctl-1.17-25.7.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 1 Jun 2018 15:12:08 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:1777 Important CentOS 6 procps Security Update Message-ID: <20180601151208.GA49196(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:1777 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:1777 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5088ad1f19a26726e8847982bdca51ff071b8bf9d48202f26a713052c2527785 procps-3.2.8-45.el6_9.3.i686.rpm dd01689106c323bea94b4f56f3416482629dd2ce6137921f13258e102ef960f0 procps-devel-3.2.8-45.el6_9.3.i686.rpm x86_64: 5088ad1f19a26726e8847982bdca51ff071b8bf9d48202f26a713052c2527785 procps-3.2.8-45.el6_9.3.i686.rpm ba2b604c6da10bf7d2df547760c5db6f91bef6644716c3cd708597c0a80d2179 procps-3.2.8-45.el6_9.3.x86_64.rpm dd01689106c323bea94b4f56f3416482629dd2ce6137921f13258e102ef960f0 procps-devel-3.2.8-45.el6_9.3.i686.rpm 9310f7af0fd82d64736c7b837a5ed4776418c2c45bd74e1d8df540f3916b2dfc procps-devel-3.2.8-45.el6_9.3.x86_64.rpm Source: 828effa30b5895235b5db5f2fce5c8f56525e3dbc31d49e90a12741ffc4480de procps-3.2.8-45.el6_9.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 1 Jun 2018 15:12:42 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:1779 Important CentOS 6 xmlrpc3 Security Update Message-ID: <20180601151242.GA49538(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:1779 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:1779 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8a63dd898f19ba28ff553e34cf7e3d22690e5ad769a58ba314c29382c3dddba8 xmlrpc3-client-3.0-4.17.el6_9.noarch.rpm 6bea1a7d98cccdf32c2f75de45b6a7346a6ba76381e4a13aa885a9081412fc94 xmlrpc3-client-devel-3.0-4.17.el6_9.noarch.rpm 12fa409cb17f876d5e7687d362554a64446f22731ca89d179b8a7a6b76964c2c xmlrpc3-common-3.0-4.17.el6_9.noarch.rpm d84de1c265757099ef0fcec691095f17af2c781275baf4e4cc6cc295e3e4d9cb xmlrpc3-common-devel-3.0-4.17.el6_9.noarch.rpm 1643cc58264f9a50ef79a11961d77e6c15733272db2fdca5326339f68b20a06d xmlrpc3-javadoc-3.0-4.17.el6_9.noarch.rpm 8a109d1ed6d4a054b8efbed1d25b6740d5316ab0d8407fe8fec715327f4bf26d xmlrpc3-server-3.0-4.17.el6_9.noarch.rpm d32170144a993875542024297d967cbdcbfc5348ba9e698eb86ec57ef0178d66 xmlrpc3-server-devel-3.0-4.17.el6_9.noarch.rpm x86_64: 8a63dd898f19ba28ff553e34cf7e3d22690e5ad769a58ba314c29382c3dddba8 xmlrpc3-client-3.0-4.17.el6_9.noarch.rpm 6bea1a7d98cccdf32c2f75de45b6a7346a6ba76381e4a13aa885a9081412fc94 xmlrpc3-client-devel-3.0-4.17.el6_9.noarch.rpm 12fa409cb17f876d5e7687d362554a64446f22731ca89d179b8a7a6b76964c2c xmlrpc3-common-3.0-4.17.el6_9.noarch.rpm d84de1c265757099ef0fcec691095f17af2c781275baf4e4cc6cc295e3e4d9cb xmlrpc3-common-devel-3.0-4.17.el6_9.noarch.rpm 1643cc58264f9a50ef79a11961d77e6c15733272db2fdca5326339f68b20a06d xmlrpc3-javadoc-3.0-4.17.el6_9.noarch.rpm 8a109d1ed6d4a054b8efbed1d25b6740d5316ab0d8407fe8fec715327f4bf26d xmlrpc3-server-3.0-4.17.el6_9.noarch.rpm d32170144a993875542024297d967cbdcbfc5348ba9e698eb86ec57ef0178d66 xmlrpc3-server-devel-3.0-4.17.el6_9.noarch.rpm Source: 3ffd2f90bf7ddd055de393d3344152cc0fbde63a3298cbb12a7de3e7067f895c xmlrpc3-3.0-4.17.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Fri, 1 Jun 2018 16:58:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2018:1771 CentOS 7 linux-firmware Enhancement Update Message-ID: <20180601165833.GA788(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2018:1771 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1771 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c81d039ccae2e6d9a5f8c1f63e99c0a611d489b49da73093341625ce7203fffd iwl1000-firmware-39.31.5.1-62.1.el7_5.noarch.rpm b16d77402aaaeaab2cd27bb3c702209459aa5920bbe530687ce8867521cca73e iwl100-firmware-39.31.5.1-62.1.el7_5.noarch.rpm f4c316d5b6277e5f80544ed82ece1c3c4194b3bf7074bcb046215cd2a3de80c9 iwl105-firmware-18.168.6.1-62.1.el7_5.noarch.rpm 85a977ba7de5d5a55865790deae6c0975e2a61ae73e5a976bdc5a6f28a3612dd iwl135-firmware-18.168.6.1-62.1.el7_5.noarch.rpm 85cd4cc32e5b47cb6d04a98b03f7cf53d00a41ed0054ea7eb3147f3b7ffac8da iwl2000-firmware-18.168.6.1-62.1.el7_5.noarch.rpm d347fb597ac149b5910a60b0e0f1d5a81766b639b783d8cb4e64233b63c2805c iwl2030-firmware-18.168.6.1-62.1.el7_5.noarch.rpm 270d1efa9566b37a6516957d18bcb68dbe50b261751e8f8772a4c46e62c2c152 iwl3160-firmware-22.0.7.0-62.1.el7_5.noarch.rpm c62436867e8b4fa0afa2854582c1e2ede38a25aa5c8aee63c295fb552d578d5c iwl3945-firmware-15.32.2.9-62.1.el7_5.noarch.rpm 8ae9e3a5bba2fe05c26f78cb7895fc9867d004e4147143073415bd6273bd21c3 iwl4965-firmware-228.61.2.24-62.1.el7_5.noarch.rpm c0dd3fd97833e11345b55a973f80e575c1f2f7ac34fe5b5b64925b9d2d52c652 iwl5000-firmware-8.83.5.1_1-62.1.el7_5.noarch.rpm f2f59820717d84bb272dd15ac691ae57e68a6795a971780e909860825ff5b026 iwl5150-firmware-8.24.2.2-62.1.el7_5.noarch.rpm 37333c605fd80feb72d7c64febce6aa3b60b04ca6834e67a9a4a67dd1b3e0bb0 iwl6000-firmware-9.221.4.1-62.1.el7_5.noarch.rpm 7520a3f8c51170c529bd78d0cbf39c396c1c547c206d437e9c219d34d857025d iwl6000g2a-firmware-17.168.5.3-62.1.el7_5.noarch.rpm 684282a662b33d35df0b41b2329058cad0ddc5ccbd23a904cdc47208b799714e iwl6000g2b-firmware-17.168.5.2-62.1.el7_5.noarch.rpm 9106613c00bf499321524b3095bc39106ada16f2c5c8aea7a7732ff348ae1898 iwl6050-firmware-41.28.5.1-62.1.el7_5.noarch.rpm 0c71a1311ca386916843bf4f04ba9d88bec808c810ed865a48da1b916e4d2f00 iwl7260-firmware-22.0.7.0-62.1.el7_5.noarch.rpm 9b64e88b312f001e47381e9204304611ecc08e0d1d0b83c085f1d0781a6e2af6 iwl7265-firmware-22.0.7.0-62.1.el7_5.noarch.rpm f5a93f4034dc89919815bca0c650b77ff4495a9782e7544e30064ab888caae97 linux-firmware-20180220-62.1.git6d51311.el7_5.noarch.rpm Source: 2c23b4eeb2b19505867bd7786a8cb7da21d7ecd11d3a19f9de4d3e693196fcae linux-firmware-20180220-62.1.git6d51311.el7_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Fri, 1 Jun 2018 16:59:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:1780 Important CentOS 7 xmlrpc Security Update Message-ID: <20180601165906.GA863(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:1780 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:1780 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 2bad0902c6d8582ef5bb5758c6860951f34cb646b69eda066162ed5cb83aa500 xmlrpc-client-3.1.3-9.el7_5.noarch.rpm a47c496fc4e85d23172c9fb69e236caecfd9aa8e813ff15eeab908309b203a4f xmlrpc-common-3.1.3-9.el7_5.noarch.rpm 4b0992a8b0e3c18327635bfe9a1a6f4e946eeb8c9db62aacaf16e728ae061390 xmlrpc-javadoc-3.1.3-9.el7_5.noarch.rpm ac336edfd9e783d9a98e89d517a049e98e6bacfbc4a6564d44c1778aa6b27b69 xmlrpc-server-3.1.3-9.el7_5.noarch.rpm Source: 6e330c0f41b9a2eb2b51a7de6242c122be29713ee6e9356fe739dbc52225ea84 xmlrpc-3.1.3-9.el7_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 160, Issue 1 ***********************************************

1 0

Password recovery trick not working on CentOS
by Nicolas Kovacs 01 Jun '18

01 Jun '18

Hi, I remember back in the days, there was a neat trick to recover a lost root password, or more exactly, redefine a new password for root. 1. In the bootloader, boot the system with the 'init=/bin/bash' kernel argument. 2. Remount the root partition in read-write mode: # mount -o remount,rw / 3. Set the password for root: # passwd 4. Remount the root partition in read-only mode: # mount -o remount,ro / 5. Switch off the computer. I tried this out of curiosity on a CentOS 7 sandbox machine, and this doesn't seem to work anymore. I can boot to a 'bash' console and set the password OK. But this password doesn't seem to work on the subsequent normal boot. Anybody knows why this is so? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

6 13

move LDAP service to new server
by Gary Stainburn 01 Jun '18

01 Jun '18

On my old Centos 7 server I had set up a LDAP database for user authentication by other services (the server locally uses normal PAM authenticatin). I set it up originally from a web page describing how to set up an LDAP server for use with MS Outlook clients (which never worked) Is there any (easy to follow) instructions anywhere to tell me how to back up this service and restore it onto a new one?

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2018