Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Latest updated scap-security-guide signed with wrong GPG key
by cwlists 20 May '18

20 May '18

Hi, Today I tried to update my CentOS 7.5 with latest updates, but it fails to verify the signature of one of the packages: ... scap-security-guide noarch 0.1.36-9.el7.centos updates It seems like this RPM was signed with AltArch PowerPC key (see further down): Warning: /var/cache/yum/x86_64/7/updates/packages/scap-security-guide-0.1.36-9.el7.centos.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID f533f4fa: NOKEY Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 The GPG keys listed for the "CentOS-7 - Updates" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository. Failing package is: scap-security-guide-0.1.36-9.el7.centos.noarch GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 >From https://www.centos.org/keys/ ... PowerPC Key download key <https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-AltArch-7-ppc64> pub 2048R/F533F4FA 2015-11-27 CentOS AltArch SIG - PowerPC (https://wiki.centos.org/SpecialInterestGroup/AltArch) <security(a)centos.org> Key fingerprint = BAFA 3436 FC50 768E 3C3C 2E4E A963 BBDB F533 F4FA

2 1

CentOS-announce Digest, Vol 159, Issue 4
by centos-announce-request＠centos.org 20 May '18

20 May '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. CESA-2018:1414 Critical CentOS 6 firefox Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 17 May 2018 11:21:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:1414 Critical CentOS 6 firefox Security Update Message-ID: <20180517112153.GA57488(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:1414 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:1414 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 64b627a405f07f6020e029f14411afead92956ff9614a044e43f870848a78779 firefox-52.8.0-1.el6.centos.i686.rpm x86_64: 64b627a405f07f6020e029f14411afead92956ff9614a044e43f870848a78779 firefox-52.8.0-1.el6.centos.i686.rpm dc1ae5fc739793f56ac5c87ee02a0abc5bf05a59836cae86d7b7f4ed0229a250 firefox-52.8.0-1.el6.centos.x86_64.rpm Source: 95a78e1b1a133e29a33e1573f5425a490e5eb21ff7ff056d9400b7b8ee6131c9 firefox-52.8.0-1.el6.centos.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 159, Issue 4 ***********************************************

1 0

Latest CentOS does not boot, Proliant ML330 G6
by Jari Fredriksson 17 May '18

17 May '18

Hello all. I just upgraded to the latest and tried to reboot: kernel panic and dead as a brick. Luckily GRUB still works and booting the to the next option in boot menu succeeds. How can this be? This OS is assumed to be solid as a brick :) br. jarif

5 7

C 7, selinux, and rpc.gssd
by m.roth＠5-cent.us 17 May '18

17 May '18

Folks, As systems are upgraded, we're getting a ton of complaints (fortunately, we're in permissive mode) that would break everything. All of them involve rpc.gssd, and I see a number of bugs listed when I search. Note that I first saw this on a RHEL system, but now I'm seeing it on CentOS 7. I'm bringing it up here, because, given that there are multiple reported, that there's some bigger picture involving policy and rpc.gssd. I'll note that some of the reported bugs were *closed last year, or before, so it seems to me an old issue resurfaced. Example. SELinux is preventing /usr/sbin/rpc.gssd from using the block_suspend capability. mark

1 0

place of other RH sources
by Leon Fauster 17 May '18

17 May '18

Out of curiosity - does someone known where the sources of other RH products are placed? RHEL sources are going into git.centos.org but what about e.g. RH OpenStack Platform packages or others products? -- LF

2 2

Creating a bootable USB to install CentOS 7
by KM 17 May '18

17 May '18

I need to copy CentOS 7 to a USB to boot from and install on servers. I have searched and there are a lot of different pages. I wanted someone to give me some tips or current places to look for easy ways to do this. I want to create the bootable USB from my Windows 10 PC in case that matters. Any tips/ideas would be great.Thank you in advance. KM

3 3

Problem with Digikam and libgphoto2 after latest update
by Nicolas Kovacs 17 May '18

17 May '18

Hi, I have CentOS 7 with KDE on my workstation. I'm using the CR repo. I had to remove Digikam to be able to do the latest update (1 GB of updates... wow). Here's what happens when I try to reinstall it. # yum install digikam ... --> Finished Dependency Resolution Error: Package: digikam-4.10.0-6.el7.x86_64 (epel) Requires: libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit) Available: libgphoto2-2.5.2-5.el7.x86_64 (base) libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit) Installed: libgphoto2-2.5.15-1.el7.x86_64 (@cr) ~libgphoto2_port.so.12(LIBGPHOTO2_5_0)(64bit) Error: Package: digikam-4.10.0-6.el7.x86_64 (epel) Requires: libgphoto2_port.so.10()(64bit) Available: libgphoto2-2.5.2-5.el7.x86_64 (base) libgphoto2_port.so.10()(64bit) Installed: libgphoto2-2.5.15-1.el7.x86_64 (@cr) ~libgphoto2_port.so.12()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Any suggestions? Just wait until the EPEL maintainers rebuild it against the latest stuff? 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

5 8

Persisting Routes In A Routing Table Other Than The Default
by Adam Tauno Williams 16 May '18

16 May '18

I need to add persistent routes to a policy routing table. I can add rules to an IP policy table after installing NetworkManager-config- routing-rules; but I have not found how to add routes to a table other than the specific table. Manually I do a: ip route add default via 192.168.1.6 dev ens192 table pods Rules load automatically via the /etc/sysconfig/network-scripts/rules- {interface} files. Routes added to /etc/sysconfig/network- scripts/routes-{interface} are always added to the default policy. [root@aqueduct rc.d]# ip rule 0: from all lookup local 32763: from 192.168.65.0/24 lookup pods 32764: from 192.168.41.0/24 lookup pods 32765: from 192.168.43.0/24 lookup pods 32766: from all lookup main 32767: from all lookup default -- Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA

2 3

kernel-lt from ELRepo vs. GRUB: define default boot kernel
by Nicolas Kovacs 16 May '18

16 May '18

Hi, After upgrading my workstation to CentOS 7.5 (1804), I had to upgrade my kernel from vanilla to kernel-lt from ELRepo. My NVidia GeForce 210 would only work with the driver provided by NVidia, which in turn required a more recent kernel than 3.0.10. Anyway. Right now here's all the kernels that I have on my workstation: [root@alphamule:~] # rpm -qa | grep -i kernel kernel-lt-devel-4.4.129-1.el7.elrepo.x86_64 kernel-lt-devel-4.4.131-1.el7.elrepo.x86_64 kernel-lt-headers-4.4.131-1.el7.elrepo.x86_64 kernel-lt-4.4.131-1.el7.elrepo.x86_64 kernel-lt-4.4.129-1.el7.elrepo.x86_64 And here's what I'm currently running: [root@alphamule:~] # uname -r 4.4.129-1.el7.elrepo.x86_64 I have a Logitech Illuminated USB keyboard, and one of the quirks of this piece of hardware is that it's unresponsive on boot time. Meaning when GRUB displays the kernel menu, the arrow keys (or for the matter any keys) won't work. Which means the only choice I have left is either boot the default kernel in the list... or go to another office, grab a standard USB keyboard and plug it in temporarily just to choose the kernel to boot. So right now I have two kernels on my machine, the 4.4.129 and the 4.4.131. How do I configure GRUB so that on the next reboot, it defaults to the 4.4.131 kernel? I knew how to do this with LILO under Slackware, but GRUB is a very different beast. 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

4 4

The right way to deal with in-house development
by m.roth＠5-cent.us 16 May '18

16 May '18

Ok, what's the "correct" way to deal with systems developed in-house, that have their own sets up subdirectories. And why, for that matter, does running sealert give me the full path to the executable, like openjdk... but *not* the full path to the file it's trying to operate on, and I'm left going "ok, where was the file it deleted? (we're running in permissive mode - overwhelmingly, developers and subject matter experts no less than nothing about selinux). mark

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss