- Discuss - lists.centos.org

how to run CentOS 8.2 under new WSL2?
by Dev Linux 18 Aug '20

18 Aug '20

I want to run CentOS 8.2 (2004) under Windows 10 Pro (2004) that comes with WSL2 1. Is there a list of steps anywhere, that would help me download what I need, and get CentOS 8.2 running under WSL2? 2. What would I need to download? (need direct URL - there are so many options for CentOS 8.2 , I am confused) 3. What steps would I need to take to get this running locally on my Windows 10 machine? Notes: ==> I don't want to run any existing CentOS available in the Windows store, I want to roll my own ==> I don't want to run CentOS 8.2 under VirtualBox or any other virtualization technology, just WSL2 ==> I don't want to download any .zip from a previous release that is not CentOS 8.2, ideally would like to be self-sufficient and gain the knowledge on how to do this myself. --- If anyone has actually done this with CentOS 8.2 and WSL2 and has it working swimingly, please reply, would love to get this up and running for a higher level of productivity, scripting and automation on my Windows dev box.

2 1

Installing devtoolset-6 on CentOS 8
by Eric Gervais-Despres 18 Aug '20

18 Aug '20

Has anybody tried (and succeeded) to get gcc 6.3.1 (or devtoolset-6) to work on CentOS 8? In the Animation and Visual Effect industry, gcc 6.3.1 is still the current recommended compiler (see www.vfxplatform.com) and is required to build many plugins. Unfortunately, it is not a "minimum requirement"... It is THE requirement. So I tried to get it from the vault: -- sudo dnf config-manager --add-repo= http://vault.centos.org/7.6.1810/sclo/x86_64/rh/ sudo dnf install devtoolset-6 -- but I get these messages: -- Error: Problem: package devtoolset-6-6.1-1.el7.x86_64 requires devtoolset-6-runtime, but none of the providers can be installed conflicting requests nothing provides policycoreutils-python needed by devtoolset-6-runtime-6.1-1.el7.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages -- All options fail. I hate having to install something not officially supported anymore, but still officially required for many current software. Thank you. -- *Éric Gervais-Després* President 4270 St-Laurent #300 Montréal, Qc, Canada, H2W 1Z3 +1-514-705-4946 *www.ngeniousstudio.com <http://www.ngeniousstudio.com>*

2 1

Replacement for KMail V1
by Gary Stainburn 17 Aug '20

17 Aug '20

Last week my trusty Fedora 9 file and print server failed on me. Not bad for 12 years trusty service. I have now replaced it with a C7 server and found that lots have changed in those 12 years. Thankfully many things haven't, named-chroot, dhcpd, etc pretty much copied across and Samba wasn't a major rewrite. However I feel like my right arm has been chopped off. My work life revolves around my emails which were in KMail version 1.x. My first thought was to move to the current KMail which is version 4.x. The problem is that it's cr*p. It appears to be the same as V1, but just more up to date - perfect. Unfortunately it is so slow that it is completely unusable, even on a brand new server. As a GUI it is unusable, and functionally fails with connections time out etc. Some research has found that KMail was stuffed as far back as V2 when they moved to using an embedded MYSQL engine to drive it. What I would really like is advice on how to make KMail V4 usable. As I doubt that is possible can anyone please recommend a decent email client with good keyboard short-cuts and filtering processes. I am currently limping along using Thunderbird but I find the lack of useful keystroke functions (such as next unread message, next folder with an unread message) annoying. Having to move my hand from keyboard to mouse is more exercise than I'm used to.

3 2

Samba rpms now available from Storage SIG
by Anoop C S 17 Aug '20

17 Aug '20

Hi all, This is to announce the availability of Samba(and CTDB) rpms from Storage SIG[1] on CentOS 7 and 8. Visit Samba's CentOS Storage SIG wiki page[2] for more details on installation steps. [1] https://wiki.centos.org/SpecialInterestGroup/Storage [2] https://wiki.centos.org/SpecialInterestGroup/Storage/Samba Regards, Anoop C S.

2 3

Teo En Ming's Learning Achievements on 14 August 2020 Friday
by Turritopsis Dohrnii Teo En Ming 15 Aug '20

15 Aug '20

Subject: Teo En Ming's Learning Achievements on 14 August 2020 Friday [1] Activate Cisco AnyConnect SSL VPN License on Cisco ASA 5506-X Firewall Today I discovered that the base license for Cisco ASA 5506-X Firewall only allows maximum 2 SSL VPN users. I had to login to https://www.cisco.com/go/license, assign the PAK/token to the serial number of Cisco ASA 5506-X firewall and perform a license request to Cisco. After receiving the Product Authorization Key from Cisco, I had to activate it on the Cisco ASA 5506-X firewall using the following CLI commands: enable config t activation-key 12345678 12345678 12345678 12345678 12345678 The number of AnyConnect Premium Peers has been increased from 2 to 50 after license activation. [2] Configuring NIC teaming/bonding on CentOS 8.2 (2004) Linux Server Today I had to configure NIC teaming/bonding on CentOS 8.2 (2004) Linux Server. The server hardware is Dell PowerEdge R640 with 2x 10GE NIC ports and 6x 1GE NIC ports. NIC teaming/bonding was configured using 2x 10GE NIC ports. All I had to do is to follow the following reference guide. Reference Guide: How to Configure NIC Teaming on CentOS 8 / RHEL 8 Link: https://www.linuxtechi.com/configure-nic-teaming-centos-8-rhel-8/ In my situation, the network interfaces used in the NIC teaming/bonding are eno1 and eno2. Both are 10 Gigabit per second. -- -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

3 2

Dumb Centos 8 DNF mirror question...
by Tom Bishop 14 Aug '20

14 Aug '20

I have several Centos 8 machines that I update and every now and again I will go through and update all of them and one of them will get a slow mirror, like downloading the kernel at 50kb etc. With the newer version I am unable to figure out how to force it to update the mirror list and hopefully change to a faster mirror. I have searched but must not be using the right verbiage since I am unable to find the easy solution to dump the mirrors and re-select. Thanks :)

2 2

After update to 8 (2004) ... system is unbootable - UEFI Secure boot
by Leon Fauster 13 Aug '20

13 Aug '20

Hi all, I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). Installed kernels are kernel-4.18.0-147.5.1.el8_1.x86_64 kernel-4.18.0-147.8.1.el8_1.x86_64 kernel-4.18.0-193.6.3.el8_2.x86_64 Unfortunately I can not boot into the latest kernel-4.18.0-193.6.3.el8_2.x86_64. After grub2 screen I only see following line: EFI stub: UEFI Secure Boot is enabled Booting into the older kernel is still possible. The above line appears and after that the normal kernel output scrolls over the screen (rhgb quiet disabled). Is the new kernel correctly signed? What can I do? -- Thanks Leon

3 7

kvm & external snapshots
by Gregory P. Ennis 13 Aug '20

13 Aug '20

Everyone, I am trying to create external snapshots of a kvm guest machine and have not been able to do so. In accordance with : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… I have used the command line : snapshot-create-as --diskspec vda,snapshot=external,file=/u4/guest/MaBa- clone/test.snap.img--domain MaBa-clone --name MaBa-clone_snap --description "Snap before 9Aug2020" This command line gives me the error : error: unsupported configuration: disk 'vda' must use snapshot mode 'internal' Is it possible to perform an external snapshot of a kvm guest? Greg Ennis

2 1

[Sharing] CentOS 8.2 (2004) Linux Server is Compatible with Dell PowerEdge R640 1U Server
by Turritopsis Dohrnii Teo En Ming 13 Aug '20

13 Aug '20

Subject: [Sharing] CentOS 8.2 (2004) Linux Server is Compatible with Dell PowerEdge R640 1U Server Good day from Singapore, I have just installed CentOS 8.2 (2004) Linux Server on Dell PowerEdge R640 1U Server for "Donald Trump and Xi Jinping Investment Company LLP" (fictitious/fictional company name used) in Singapore on 11 August 2020 Tuesday. I can confirm that CentOS 8.2 (2004) is compatible with Dell PowerEdge R640. The hardware specifications of Dell PowerEdge R640 are: (1) Processor: Intel Xeon Silver 4210R CPU @ 2.40 GHz (10 cores, 20 threads) (2) 128 GB DDR4-2400 RAM (8 pieces of 16 GB RAM, all 8 slots filled up) (3) PERC H740P Mini RAID Controller (4) 2 units of 960 GB SATA 6 Gbps SSD in RAID 1 configuration (5) Network Ports: 4 x 1 GbE 2 x 10 GbE + 2 x 1 GbE Just sharing only. -- -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 and refugee seeking attempts at the United Nations Refugee Agency Bangkok (21 Mar 2017), in Taiwan (5 Aug 2019) and Australia (25 Dec 2019 to 9 Jan 2020): [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

2 3

Testing
by Turritopsis Dohrnii Teo En Ming 13 Aug '20

13 Aug '20

Testing

1 0

Docker swarm service misconfigured in FirewallD / CentOS 7
by Nicolas Kovacs 13 Aug '20

13 Aug '20

Hi, I'm currently fiddling with Docker Swarm on three sandbox servers running CentOS 7. Unfortunately I couldn't get even the most basic configuration running. After some experimenting and investigating, it turns out there's a problem with FirewallD. Here's what I did first on every single node. # firewall-cmd --permanent --add-service=docker-swarm # firewall-cmd --reload I launched a simple web service like this: # docker service create --name web -p 80:80 nginx My three nodes appear correctly with 'docker node ls'. >From here, I should be able to open the Nginx default web page in a web browser using any node's hostname. But nothing happens. No page is loaded. On a whim, I turned off FirewallD, and suddenly everything worked as expected. Now here's the list of ports that have to be open on every single node for Docker Swarm to work: * 2376/tcp * 2377/tcp * 7946/tcp * 7946/udp * 4789/udp And here's what docker-swarm.xml looks like under CentOS 7: # cat /usr/lib/firewalld/services/docker-swarm.xml <?xml version="1.0" encoding="utf-8"?> <service> <short>Docker integrated swarm mode</short> <description>Natively managed cluster of Docker Engines (>=1.12.0), where you deploy services.</description> <port port="2377" protocol="tcp"/> <port port="7946" protocol="tcp"/> <port port="7946" protocol="udp"/> <port port="4789" protocol="udp"/> <protocol value="esp"/> </service> So it looks like TCP port 2376 was forgotten in that service definition. I opened it up manually on every node: # firewall-cmd --permanent --add-port=2376/tcp # firewall-cmd --reload And now Docker Swarm works correctly. Cheers from the sunny South of France, Niki Kovacs -- 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 Mob. : 06 51 80 12 12

2 1

NFSroot over wifi in CentOS 7 - graceful shutdown problem
by Dmitry E. Mikhailov 13 Aug '20

13 Aug '20

Hi, I've got a task to have a small number of laptops netboot Linux over WiFi. The kernel is loaded off the USB stick of cource, it's off topic for now. The WPA-supplicant daemon is started early by dracut off initrd. It works. Mostly. The problem is that upon shutdown systemd terminates all the processes FIRST and unmounts filesystems NEXT. Guess what? Upon termination, wpa-supplicant brings the wireless interface down and the system hangs being unable to unmount now-defunct NFSroot. There were some discussions regarding similar matter and there's even the RH Errata: https://access.redhat.com/errata/RHBA-2018:2447 But I'm woking on a fully updated CentOS Linux release 7.8.2003 and nevertheless I've got the problem. I don't have rights to see the BZ. https://bugzilla.redhat.com/show_bug.cgi?id=1593649 I'm deciding to use a quick and dirty hack to do a totally ungraceful shutdown/reboot: https://unix.stackexchange.com/questions/533307/systemd-fails-to-umount-man… Any better ideas? Best regards, Dmitry Mikhailov.

2 2

Install OpenVAS on CentOS Linux release 8.2.2004 (Core)
by Kaushal Shriyan 12 Aug '20

12 Aug '20

Hi, I am running CentOS Linux release 8.2.2004 (Core). Are there any instructions to install OpenVAS for CentOS Linux release 8.2.2004 (Core)? Thanks in advance and I look forward to hearing from you. Best Regards, Kaushal

4 6

Re: [CentOS] systemd syslog.target
by ctcard 11 Aug '20

11 Aug '20

Thanks Simon,I think my question got a bit lost amongst all the grub issues - does anyone else have information about whether any references to syslog.target in systemd unit files can be removed?ChrisSent from Samsung Mobile on O2 -------- Original message -------- From: Simon Matter via CentOS <centos(a)centos.org> Date: 31/07/2020 10:02 (GMT+00:00) To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] systemd syslog.target Hi,>> I've noticed that there are several systemd unit files in CentOS 7 and 8> with the optionAfter=syslog.targetin the [Unit] section, but since systemd> version 198 syslog.target has not existed.I deduce from this that> "After=syslog.target" is ignored by systemd and can therefore be removed.> Is this correct? I am writing some systemd unit files for our own services> which previously used init.d scripts, so I want to ensure I'm not causing> problems by omitting "After=syslog.target"ChrisSent from Samsung Mobile on> O2Interesting, there is really no syslog.target on either CentOS 7 or 8. Butif a service needs classic syslog, shouldn't it have another After=instead?Simon_______________________________________________CentOS mailing listCentOS@centos.orghttps://lists.centos.org/mailman/listinfo/centos

2 1

Docker container isolation not working in CentOS 7
by Nicolas Kovacs 11 Aug '20

11 Aug '20

Hi, I've decided to use these summer holidays to wrap my head around Docker and its quirks. Spent the last couple weeks working through a Udemy tutorial and a thick book about Docker, and I have Docker CE installed on two machines: * my workstation running OpenSUSE Leap 15.1 * a public sandbox server running CentOS 7 I'm currently fiddling with custom networks and container isolation, and it looks like I discovered a bug or at least an inconsistency in CentOS. Maybe the gurus among you have an explanation for this. Sorry if this is a bit long, but I try to be as clear as possible. OpenSUSE Leap 15.1 ------------------ For demonstration purposes on how things *should* be, I'm starting two Nginx containers named "webserver1" and "webserver2": $ docker run -dit --name webserver1 nginx $ docker run -dit --name webserver2 nginx These two containers have the respective 172.17.0.2 and 172.17.0.3 IP addresses: $ docker network inspect bridge | grep -i ipv4address "IPv4Address": "172.17.0.2/16", "IPv4Address": "172.17.0.3/16", The "webserver1" container has the 172.17.0.2 IP address: $ docker exec -it webserver1 hostname -I 172.17.0.2 Since "webserver1" and "webserver2" are both on the "bridge" network, they can communicate with each other: $ docker exec -it webserver1 curl -m 5 http://172.17.0.3 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... Now I'm creating the custom "blog" network: $ docker network create blog $ docker network ls NETWORK ID NAME DRIVER SCOPE e02e6fc654c6 blog bridge local 3ea6f28134ba bridge bridge local 8d2b8dfe5352 host host local 0bd337e274c2 none null local I'm starting a third container named "webserver3" and assign it to the new "blog" network: $ docker run -dit --name webserver3 --network blog nginx This new container is in a whole new network segment: $ docker network inspect blog | grep -i ipv4address "IPv4Address": "172.20.0.2/16", As is to be expected, it can't communicate with the other two containers: $ docker exec -it webserver3 curl -m 5 http://172.17.0.2 curl: (28) Connection timed out after 5001 milliseconds $ docker exec -it webserver3 curl -m 5 http://172.17.0.3 curl: (28) Connection timed out after 5001 milliseconds So far so good. CentOS 7 -------- Now let's repeat the exact same experiment on a server running CentOS 7. First, create two containers on the default "bridge" network and check if they can communicate with each other: $ docker run -dit --name webserver1 nginx $ docker run -dit --name webserver2 nginx $ docker network inspect bridge | grep -i ipv4address "IPv4Address": "172.17.0.3/16", "IPv4Address": "172.17.0.2/16", $ docker exec -it webserver1 hostname -I 172.17.0.2 $ docker exec -it webserver1 curl -m 5 http://172.17.0.3 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... Now create a custom "blog" network and start a third container assigned to that network: $ docker network create blog $ docker network ls | grep blog 0571c80fef1b blog bridge local $ docker run -dit --name webserver3 --network blog nginx $ docker network inspect blog | grep -i ipv4address "IPv4Address": "172.19.0.2/16", $ docker exec -it webserver3 hostname -I 172.19.0.2 Now IN THEORY "webserver3" shouldn't be able to communicate with the "webserver1" and "webserver2" containers. But here's what happens IN PRACTICE (and only on CentOS 7): $ docker exec -it webserver3 curl -m 5 http://172.17.0.2 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... $ docker exec -it webserver3 curl -m 5 http://172.17.0.3 <!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> ... As far as I'm concerned, it looks like a bug, it walks like a bug and it quacks like a bug. Any remarks and/or suggestions? Cheers from the sunny South of France, 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 Mob. : 06 51 80 12 12

3 4

CentOS8 pxeboot Error setting up software source
by Satish Patel 10 Aug '20

10 Aug '20

Folks, Last month i have setup PXE server using CentOS8-1-1911 release and everything was working fine so today i thought let me upgrade it to CentOS8-2-2004 so i just did rsync and updated all packages but after that it started throwing following error during pxe installation Installation source (Error setting up software source) I have check logs and i can see its setting correct source which is my apache server also networking looks good. I can ping server from a kickstart client, i have tried to give multiple repo manually but still have the same error. I am using this repo, let me know if this is wrong place http://mirror.liquidtelecom.com/centos/8.1.1911/BaseOS/x86_64/os/ Is this a bug or something which i am not aware of?

1 0

ZFS fails with latest C8 kernel
by Robert G (Doc) Savage 10 Aug '20

10 Aug '20

As if last weekend's UEFI debacle wasn't bad enough, it now seems the latest C8 kernel (4.18.0-193.14.2) is incompatible with the current ZFSOnLinux packages (0.8.4-1). When booted to the latest kernel, ZFS is inaccessible on my C8 storage server. When I back off to the prior kernel (4.18.0-193.6.3), all is well. If a local ZFS system is unavailable to the C8 kernel support folks, I'll be happy to assist them by volunteering my system as a lab rat. --Doc Savage Fairview Heights, IL

4 3

python problem
by Chuck Campbell 09 Aug '20

09 Aug '20

Question for the list: I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance tests, I believe the processor is actually spending measurable time in the throttled condition. I have installed lmsensors, and am monitoring temps as frequently as the reported throttling occurs, but I never see any high cpu temps. I see them vary, based on load, but never high enough to be alarmed, or to be throttled. I did a lot of googling, and I see some intel issues in some lenovo laptops, and a potential fix. I did the following: dnf copr enable abn/throttled dnf install -y throttled but I get this output: Error: Problem: conflicting requests - nothing provides python3-configparser needed by throttled0.7-1.x86_64 I have no guess what to do about this. Thanks, -chuck -- ACCEL Services, Inc.| Specialists in Gravity, Magnetics | (713)993-0671 ph. | and Integrated Interpretation | (713)993-0608 fax 448 W. 19th St. #325| Since 1992 | (713)306-5794 cell Houston, TX, 77008 | Chuck Campbell | campbell(a)accelinc.com | President & Senior Geoscientist | "Integration means more than having all the maps at the same scale!"

3 2

python problem while trying to fix a separate issue
by Chuck Campbell 09 Aug '20

09 Aug '20

Question for the list: I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance tests, I believe the processor is actually spending measurable time in the throttled condition. I have installed lmsensors, and am monitoring temps as frequently as the reported throttling occurs, but I never see any high cpu temps. I see them vary, based on load, but never high enough to be alarmed, or to be throttled. I did a lot of googling, and I see some intel issues in some lenovo laptops, and a potential fix. I did the following: dnf copr enable abn/throttled dnf install -y throttled but I get this output: Error: Problem: conflicting requests - nothing provides python3-configparser needed by throttled0.7-1.x86_64 I have no guess what to do about this. Thanks, -chuck -- campbell(a)accelinc.com | President & Senior Geoscientist | "Integration means more than having all the maps at the same scale!"

1 0

erroneous cpu thermal throttling / actually a python3 question
by Chuck Campbell 09 Aug '20

09 Aug '20

I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance tests, I believe the processor is actually spending measurable time in the throttled condition. I have installed lmsensors, and am monitoring temps as frequently as the reported throttling occurs, but I never see any high cpu temps. I see them vary, based on load, but never high enough to be alarmed, or to be throttled. I did a lot of googling, and I see some intel issues in some lenovo laptops, and a potential fix. I did the following: dnf copr enable abn/throttled dnf install -y throttled but I get this output: Error: Problem: conflicting requests - nothing provides python3-configparser needed by throttled0.7-1.x86_64 I have no guess what to do about this. --

1 0

Fixing grub/shim issue Centos 7
by david 09 Aug '20

09 Aug '20

After trying several paths, some suggested on this list, here's my results. 1) Fixing a unbootable system wasn't practical in my case. Fortunately, all my systems can be rebuilt from scratch. 2) When I was lucky enough to catch an updated system before reboot, backing out the defective updates wasn't possible. Yum said there were no prior versions. 3) The most reliable method I found for Centos 7 was: - Re=install from scratch (luckily, my data files were safe and restorable) - Before running any updates, apply the fix suggested by Redhat and exclude updates to grub2, shim and mokutil. - Without the above 'exclude', the system became unbootable after a yum update even though the corrected versions of shim should have been loaded. The system I'm dealing with is Centos 7. I can easily rebuild it from scratch and test stuff without losing crucial data, if it would helpful. 4) I haven't experimented yet with centos 8 because the hardware is remote and requires me to get a friend involved to help. My local hardware is not supported by Centos 8, so it will remain on Centos 7 until I replace the hardware or switch to a different Linux. David

16 35

CentOS-announce Digest, Vol 186, Issue 1
by centos-announce-request＠centos.org 08 Aug '20

08 Aug '20

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-2020:3350 CentOS 7 systemd BugFix Update (Johnny Hughes) 2. CEBA-2020:1212 CentOS 7 rdma-core BugFix Update (Johnny Hughes) 3. CEBA-2020:3356 CentOS 7 sos BugFix Update (Johnny Hughes) 4. CESA-2020:3285 Important CentOS 7 postgresql-jdbc Security Update (Johnny Hughes) 5. CEBA-2020:3351 CentOS 7 nfs-utils BugFix Update (Johnny Hughes) 6. CESA-2020:3281 Important CentOS 7 libvncserver Security Update (Johnny Hughes) 7. CESA-2020:2969 Important CentOS 7 java-11-openjdk Security Update (Johnny Hughes) 8. CESA-2020:2968 Important CentOS 7 java-1.8.0-openjdk Security Update (Johnny Hughes) 9. CESA-2020:2985 Important CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) 10. CESA-2020:3284 Important CentOS 6 postgresql-jdbc Security Update (Johnny Hughes) 11. CESA-2020:3345 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 12. CESA-2020:3233 Important CentOS 6 firefox Security Update (Johnny Hughes) 13. CESA-2020:3344 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 14. CESA-2020:3253 Important CentOS 7 firefox Security Update (Johnny Hughes) 15. CEBA-2020:3348 CentOS 7 curl BugFix Update (Johnny Hughes) 16. CEBA-2020:3349 CentOS 7 sssd BugFix Update (Johnny Hughes) 17. CEBA-2020:3352 CentOS 7 libguestfs BugFix Update (Johnny Hughes) 18. CEBA-2020:3354 CentOS 7 libreswan BugFix Update (Johnny Hughes) 19. CEBA-2020:3355 CentOS 7 subscription-manage BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 7 Aug 2020 12:27:08 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:3350 CentOS 7 systemd BugFix Update Message-ID: <20200807122708.GA2116(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:3350 Upstream details at : https://access.redhat.com/errata/RHBA-2020:3350 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c567d8148be4cbbafb0f443c59fb2faec08483cd81f6ca84f010769451162bf5 libgudev1-219-73.el7_8.9.i686.rpm 33a6b4dedff36d3e14d23f9c5d527972b7707fe0dddad579d58663bd60d50005 libgudev1-219-73.el7_8.9.x86_64.rpm b0426ebf17b9b4f5889144f4d51f1a3fea6ec62d0facfb2630b6c07e1e7b8ac3 libgudev1-devel-219-73.el7_8.9.i686.rpm 1f21f6edf5678e5cbcec7d36af46c56df5dc80378213a76f50009b6b07080936 libgudev1-devel-219-73.el7_8.9.x86_64.rpm e2400ded564b4fd9fba8a744b818b7a2152a78efd85aa025f543f0c5e0f03fcd systemd-219-73.el7_8.9.x86_64.rpm de1dda0a139a4ae86e40604d17ecb33aef4a38156a3c3195942a8bbc13388666 systemd-devel-219-73.el7_8.9.i686.rpm 2a1e7cd453de4133f5700b5d596fba9afce8541aa58c4734da107a1ddc6c4e5c systemd-devel-219-73.el7_8.9.x86_64.rpm a42801b204c3b4178b62c54619c071aafa4532d836a93adf2c556daa932b51ae systemd-journal-gateway-219-73.el7_8.9.x86_64.rpm 27c0a7ced50251de61d4cbe4fb6b1942ae72e5ad332ece9a2a666c11fdc0093c systemd-libs-219-73.el7_8.9.i686.rpm ede8f86313c99b59cd91ef1d7bad7890e8eeffe043f61abf47012c44dc5c99c3 systemd-libs-219-73.el7_8.9.x86_64.rpm 07871f43c991e7eaca16f9eaf67151714434f77e0f892a1b424feee9442a94f2 systemd-networkd-219-73.el7_8.9.x86_64.rpm 7d97385cd5463074fd2446fd28706d355c3d2e7866b33484d39c4a49ee775f4d systemd-python-219-73.el7_8.9.x86_64.rpm 56e2c1a59a1a0d1394c8a47fa1cc4e233c7d8317a4b397c5464a70483b58aa82 systemd-resolved-219-73.el7_8.9.i686.rpm 9a180f5dc35c1b73775523bde31e65ba2263517d97afe6cd183f03bb96484dfe systemd-resolved-219-73.el7_8.9.x86_64.rpm 70bc0c186f63275107428c1b61f7d08f23d3d38c939b94c110c8186a503fd5a4 systemd-sysv-219-73.el7_8.9.x86_64.rpm Source: 0bb3b645abfb9222b27117583c76623f5ac783168a2b2eaf8e68b7b076ca61b5 systemd-219-73.el7_8.9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 7 Aug 2020 12:27:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:1212 CentOS 7 rdma-core BugFix Update Message-ID: <20200807122746.GA2424(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:1212 Upstream details at : https://access.redhat.com/errata/RHBA-2020:1212 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 48b31125348c316305a75dfd8882d953f7108fd4a634c736fc55c3eac43a62ee ibacm-22.4-4.el7_8.x86_64.rpm 225973fb73009f0848d7cebd95ee7f9c1e5a859acfba4e51a3982538de576df1 iwpmd-22.4-4.el7_8.x86_64.rpm 156b5bc36a7da8aee5f3055bf08ab9ac21ec19434b37062327863ddd9f4d56bf libibumad-22.4-4.el7_8.i686.rpm 404f2b30ca26abda9b338ccf044bdeca636c83c7845702d2b548b166beb4574c libibumad-22.4-4.el7_8.x86_64.rpm 1e070781f4f1e1b05b369d3995f059d0a06df2a0deb2d43d680a9327e087b06a libibverbs-22.4-4.el7_8.i686.rpm 7fd38827789deea174302f81113e9a6387dd19c3ff6cc9e97abda3e53d506ded libibverbs-22.4-4.el7_8.x86_64.rpm 95fece06596adfd7ad12b4fc5010a53a15cfbb8f035c8b7051797663b21e71ca libibverbs-utils-22.4-4.el7_8.x86_64.rpm d406bde4cc99b6ec51e2f62a5ae891a0bb641fabeebd46fa97942b367ea69c83 librdmacm-22.4-4.el7_8.i686.rpm 8ab3808a39cd1a3b77479a7f0ba0bcb2af4c34cf5bc50a55a14b81d29f785b2d librdmacm-22.4-4.el7_8.x86_64.rpm 5a169530aff0154784a5b5c6f29977d995af8bd257d8576bd550ec4b1dc25579 librdmacm-utils-22.4-4.el7_8.x86_64.rpm 19e381909f3e9d23e2216a028d8a23f7e4067e7cbe6e07004d5170d26537bf43 rdma-core-22.4-4.el7_8.i686.rpm 1d93bbb9fa2ae2cb4a02f22b8c0f44710cecd592f3ee85026e3b8b77257603e6 rdma-core-22.4-4.el7_8.x86_64.rpm 26fc9f77718c9b3c14f849895ef5cd54ef24a1c13b7e23643bdf543e646b88a8 rdma-core-devel-22.4-4.el7_8.i686.rpm 3a2811db0c5ff8c3d37365976127d0df91684438bb8e6e3a6d21ef39f34a370b rdma-core-devel-22.4-4.el7_8.x86_64.rpm 3109bc439b28e69faedc4218a741688aa6b42e5c22ed27c847ac18fb5e499af0 srp_daemon-22.4-4.el7_8.x86_64.rpm Source: e06297368cc5dcfd52e7a5514f5d35d2d217de16ba76900610d67539a117230d rdma-core-22.4-4.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 7 Aug 2020 12:27:54 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:3356 CentOS 7 sos BugFix Update Message-ID: <20200807122754.GA2526(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:3356 Upstream details at : https://access.redhat.com/errata/RHBA-2020:3356 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4009da92eddce4bed2fa62bb0fb255dbf2d4345f1ca2414db2c2e28b9766c14e sos-3.8-9.el7.centos.noarch.rpm Source: 4f333939eb7228c4838905fe8491f0b95acb448a5e59b71863e41ef2ac8f9124 sos-3.8-9.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Fri, 7 Aug 2020 12:28:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3285 Important CentOS 7 postgresql-jdbc Security Update Message-ID: <20200807122804.GA2653(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3285 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:3285 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4085f09e7be4410758ded16aeb5fca59795cf4c2ad37a1afa78cddf45bef6806 postgresql-jdbc-9.2.1002-8.el7_8.noarch.rpm 7ac006a9950b2c1cc710083732c5cc4a33e7c20c3699c50ad6f24318b5986edb postgresql-jdbc-javadoc-9.2.1002-8.el7_8.noarch.rpm Source: dec9a91e3d4f1c930e75b9ca02ce766fc30afc08ad522f6bb121cd0888e2e3fa postgresql-jdbc-9.2.1002-8.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Fri, 7 Aug 2020 12:28:11 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:3351 CentOS 7 nfs-utils BugFix Update Message-ID: <20200807122811.GA2745(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:3351 Upstream details at : https://access.redhat.com/errata/RHBA-2020:3351 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8094c76c7b75b5258a6632f6d5b20b2c596df2b9328f073c8424a3e11b02ce6c nfs-utils-1.3.0-0.66.el7_8.x86_64.rpm Source: 1e243fc653f07565d48a007a8a2dcc8bf7537abf0f5d4dff7969ee3df4ba6096 nfs-utils-1.3.0-0.66.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Fri, 7 Aug 2020 12:28:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3281 Important CentOS 7 libvncserver Security Update Message-ID: <20200807122823.GA2879(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3281 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:3281 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6e3bb564a139de89aa75082746181d125ed4c599326591693741010469bbd88e libvncserver-0.9.9-14.el7_8.1.i686.rpm cc9eef61c95aebbc7a432d58f5f85fbab25f19ee777834f671bc23fa94964d57 libvncserver-0.9.9-14.el7_8.1.x86_64.rpm 27fd50136804eda5f0c7bfe32a61dcd680349725916fcebde89f0c8a2e549767 libvncserver-devel-0.9.9-14.el7_8.1.i686.rpm 2b6dd64d39816de5f6fd5330c2e6b95ae66fa3c853d61272092b0a027fbd1da3 libvncserver-devel-0.9.9-14.el7_8.1.x86_64.rpm Source: 81f064d3624ca56c60a31e1328be3cc2ddf66aecceadabc2c7fa3195e20dfb40 libvncserver-0.9.9-14.el7_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Fri, 7 Aug 2020 12:29:25 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2969 Important CentOS 7 java-11-openjdk Security Update Message-ID: <20200807122925.GA3181(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2969 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2969 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f0baba96420d32cf4eebb994427ba2f86c7118788b4b3418c7b9402e2cd3c429 java-11-openjdk-11.0.8.10-0.el7_8.i686.rpm 30b285edd46334713aa83e0b1b65a1b650ea385c267f67b0dd03546ac5d41329 java-11-openjdk-11.0.8.10-0.el7_8.x86_64.rpm 9cec6ada57d884a042c6dac053f24360fa6d08e10d8cc3d5ae4425221285ae27 java-11-openjdk-demo-11.0.8.10-0.el7_8.i686.rpm 04f656bf38e094ddfd1d3cdc3cdaab3c6143d0a01cf84af3b6adb01f43f3d3cd java-11-openjdk-demo-11.0.8.10-0.el7_8.x86_64.rpm f5da7a184df2e97305571f4ef8d722f55bd7e2e511665a80b815081a382a6402 java-11-openjdk-devel-11.0.8.10-0.el7_8.i686.rpm e08bed834260820266f02776e247df0a271225ba91dbb647ac4a1199a40c8df6 java-11-openjdk-devel-11.0.8.10-0.el7_8.x86_64.rpm ed21b65052096b035615416b6caad336ad7ed21f7c00249fbed2114334613899 java-11-openjdk-headless-11.0.8.10-0.el7_8.i686.rpm 4bb37201217d3967dd808c606e2278fb6bc38d94a6f7649ece2629ee1f7ec627 java-11-openjdk-headless-11.0.8.10-0.el7_8.x86_64.rpm a612490af174fb6404253014d82ac9126deab2e8cadbddf61de4b7b3cb8f7cb9 java-11-openjdk-javadoc-11.0.8.10-0.el7_8.i686.rpm ca4619eda8674e17681e66e31ee6c5a3c7c23a68863343ea2c07729675dd219c java-11-openjdk-javadoc-11.0.8.10-0.el7_8.x86_64.rpm df07c8b3408ef966eb8912d441f8738a34f932886b59ca78f6b217f75ed20950 java-11-openjdk-javadoc-zip-11.0.8.10-0.el7_8.i686.rpm b255dc83851df1591ff837548b60443661f4c144c1ee08d0fb68f82fdaa0b8f2 java-11-openjdk-javadoc-zip-11.0.8.10-0.el7_8.x86_64.rpm 5f2aee56a3aed990696e5c55ed2e32e96962b332fd99cf0b1744e731ac92a144 java-11-openjdk-jmods-11.0.8.10-0.el7_8.i686.rpm d0e09ef3079784e791ee53675f1e513bb98b53a8e7364089f993932eaf337663 java-11-openjdk-jmods-11.0.8.10-0.el7_8.x86_64.rpm 8bdc41759d184666d96af0e64af8af5b7987e20b16b2ee54a797f3fe29bc73ba java-11-openjdk-src-11.0.8.10-0.el7_8.i686.rpm 61b97e281b86031b9203e5395b4738f04c73e4172ba7ea9ac0066a7ff6d8454d java-11-openjdk-src-11.0.8.10-0.el7_8.x86_64.rpm Source: e1c8da851ffc41a0622f258701ce0a3476dc6386660ed6e3a158b4956aa08d4b java-11-openjdk-11.0.8.10-0.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 8 Date: Fri, 7 Aug 2020 12:30:19 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2968 Important CentOS 7 java-1.8.0-openjdk Security Update Message-ID: <20200807123019.GA3589(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2968 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2968 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8f532a7f0a9990179096861d989457eea9f7c24edd5b3d341dc10c80f1df4c6d java-1.8.0-openjdk-1.8.0.262.b10-0.el7_8.i686.rpm 4157b121445b5c96d528d8bdce4d74a1db80e85b1aa5381c3c6f234e48252e12 java-1.8.0-openjdk-1.8.0.262.b10-0.el7_8.x86_64.rpm 67bef95466a88959ff6f628ff841e0520c29c9a342d14db3c79fd2e0d28c24a7 java-1.8.0-openjdk-accessibility-1.8.0.262.b10-0.el7_8.i686.rpm b3c37393386892c3d785cd1e9c992f1a21cb1192bab0843fe54e5b4adae99a86 java-1.8.0-openjdk-accessibility-1.8.0.262.b10-0.el7_8.x86_64.rpm eb98030160767bedcae681955fbfe61ddaf3ce240b8235fd0b49038bb76f081a java-1.8.0-openjdk-demo-1.8.0.262.b10-0.el7_8.i686.rpm cc621a3587b79b7bcb34c2d61ba251003fd1135ceb35954b8ad8cb4d28821eb9 java-1.8.0-openjdk-demo-1.8.0.262.b10-0.el7_8.x86_64.rpm 9e5dc66739f0a75c5667ad152ed9c6c5b05e87c43a1aba2b696426132db70ced java-1.8.0-openjdk-devel-1.8.0.262.b10-0.el7_8.i686.rpm a254d18accf85eabddb12b71d74683267d6b8c50c5b52b432489dc26da022f59 java-1.8.0-openjdk-devel-1.8.0.262.b10-0.el7_8.x86_64.rpm a61026d900ca0f74c38b7b37467fea46fa28f5b85e9a196b0bcd45e581d130e7 java-1.8.0-openjdk-headless-1.8.0.262.b10-0.el7_8.i686.rpm e2ab13df96583856fe6833bc907fa6cf19ceca648eb39e7ad3249970d41b1c2a java-1.8.0-openjdk-headless-1.8.0.262.b10-0.el7_8.x86_64.rpm 75ad65bcf12772af5222e052e70544be9a8af0fde301200a4a13ce9687c43720 java-1.8.0-openjdk-javadoc-1.8.0.262.b10-0.el7_8.noarch.rpm 05457a56238a851fcd82d51c688a9802e3ad782dbc20ccce63d598870e75afb5 java-1.8.0-openjdk-javadoc-zip-1.8.0.262.b10-0.el7_8.noarch.rpm 51e36310bdc0ddce15d267dc6944de19a91a9d19e9dd44f37ad4ddbdd0724d41 java-1.8.0-openjdk-src-1.8.0.262.b10-0.el7_8.i686.rpm 540929693f191dacff0dac4cceb9ec615306ccfbce80d5a1d0429d29ad8ca70e java-1.8.0-openjdk-src-1.8.0.262.b10-0.el7_8.x86_64.rpm Source: f54585510704640991a5e66c7b0e2891db5792771110f207d661d630730898cd java-1.8.0-openjdk-1.8.0.262.b10-0.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 9 Date: Fri, 7 Aug 2020 12:59:34 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:2985 Important CentOS 6 java-1.8.0-openjdk Security Update Message-ID: <20200807125934.GA6351(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:2985 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2985 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f75a638d28154c766756d9aeca9aaa885edbdd2783a700aae8503ede26f48498 java-1.8.0-openjdk-1.8.0.262.b10-0.el6_10.i686.rpm 1876e63dc8c5bcc3c01732633a6d9396db5c7450ccc8e94975e56500ddfa080c java-1.8.0-openjdk-debug-1.8.0.262.b10-0.el6_10.i686.rpm 18c3d30bbbf499bd04d2efb8ec4898f27b9ab7465fb62d632dac9c276e384a44 java-1.8.0-openjdk-demo-1.8.0.262.b10-0.el6_10.i686.rpm 8668ccefe8d0a342b85e05f973e91ce83fa123156909e77080fafd808d742eaf java-1.8.0-openjdk-demo-debug-1.8.0.262.b10-0.el6_10.i686.rpm e3e9e43f455d3a1f0fb0fe0d76d173d6f03e679a41d0792ec423e1938307048c java-1.8.0-openjdk-devel-1.8.0.262.b10-0.el6_10.i686.rpm 12785de8d77d72818f91005350514866bb71773a32e9f9f8441921027d805d7e java-1.8.0-openjdk-devel-debug-1.8.0.262.b10-0.el6_10.i686.rpm 7e8bc1a88dd9e1ae7b2e1796047dbd23d0fecd3f8359123507f3e104c33c5f99 java-1.8.0-openjdk-headless-1.8.0.262.b10-0.el6_10.i686.rpm 33d5602fa98dbacd65ced6a3c6bdc07e19b1d0a41b1aa1245f2589ee8ef8eb9c java-1.8.0-openjdk-headless-debug-1.8.0.262.b10-0.el6_10.i686.rpm fa3012271b3417ee47ffbabbc4796c960a1ab4581b0050330f7be6fce79d9396 java-1.8.0-openjdk-javadoc-1.8.0.262.b10-0.el6_10.noarch.rpm 5a526cf985821b87a11622b883216a0684c42a2bbcef5a8dffdcce9b0051d7db java-1.8.0-openjdk-javadoc-debug-1.8.0.262.b10-0.el6_10.noarch.rpm ee7cdcaecfaa87fa778a608a8cd55dfe8ecc90f085078481af1e656f5d20e4fc java-1.8.0-openjdk-src-1.8.0.262.b10-0.el6_10.i686.rpm 742bc65e528fb22755fdbe43b620de70aa4c2bc3e0800382c38475ecbf93df88 java-1.8.0-openjdk-src-debug-1.8.0.262.b10-0.el6_10.i686.rpm x86_64: 1bef0dcee38ee08a34d74db4846192699e8b61586651aa083915bad611d04fb0 java-1.8.0-openjdk-1.8.0.262.b10-0.el6_10.x86_64.rpm 951270257f960d024c4351519ca8837f5040f175f99d7eae4eb082067a6e50e1 java-1.8.0-openjdk-debug-1.8.0.262.b10-0.el6_10.x86_64.rpm 604fde532fd66a74fe7ea1eb6fa8566023cba64b5ae61320b5ae6a93c3b6ce6f java-1.8.0-openjdk-demo-1.8.0.262.b10-0.el6_10.x86_64.rpm 400bccddfdafb028e6e685d8503e8c1ede80a54d78ba973004ab380f2c5b0d8c java-1.8.0-openjdk-demo-debug-1.8.0.262.b10-0.el6_10.x86_64.rpm 71c47203564d984c673d15146861601a77b0c01f28f43d1e74215ce072eeae94 java-1.8.0-openjdk-devel-1.8.0.262.b10-0.el6_10.x86_64.rpm e9082bae3be8fa82f4f6256640d796ff5617dc4b6ae4cc4c12ec00394a95859b java-1.8.0-openjdk-devel-debug-1.8.0.262.b10-0.el6_10.x86_64.rpm 847168d108cc411613839297d78f9943543391c0e85316cc7e49398b18235af9 java-1.8.0-openjdk-headless-1.8.0.262.b10-0.el6_10.x86_64.rpm cb47353d46c301885dedb4852c0b22e6c136148b52ff462bd4316811dfe2c97f java-1.8.0-openjdk-headless-debug-1.8.0.262.b10-0.el6_10.x86_64.rpm fa3012271b3417ee47ffbabbc4796c960a1ab4581b0050330f7be6fce79d9396 java-1.8.0-openjdk-javadoc-1.8.0.262.b10-0.el6_10.noarch.rpm 5a526cf985821b87a11622b883216a0684c42a2bbcef5a8dffdcce9b0051d7db java-1.8.0-openjdk-javadoc-debug-1.8.0.262.b10-0.el6_10.noarch.rpm 5425d0fefb4ae469e9126bf6583470093669126808106874b4418472a56d1708 java-1.8.0-openjdk-src-1.8.0.262.b10-0.el6_10.x86_64.rpm 886dce58b333eb7b5dda2f290bf95c31707c3012b0dbd05254fe5ad01ef66401 java-1.8.0-openjdk-src-debug-1.8.0.262.b10-0.el6_10.x86_64.rpm Source: efc8feb6d3b3479a7521be9a643f583f4f8cd77ef54699413a4e4b54caeb38c0 java-1.8.0-openjdk-1.8.0.262.b10-0.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 10 Date: Fri, 7 Aug 2020 13:00:18 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3284 Important CentOS 6 postgresql-jdbc Security Update Message-ID: <20200807130018.GA6567(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3284 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:3284 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7da24f52d632e4a7bfe00e2133a719c22e6927e21c74a8c4a584b001aeb35df8 postgresql-jdbc-8.4.704-4.el6_10.noarch.rpm x86_64: 7da24f52d632e4a7bfe00e2133a719c22e6927e21c74a8c4a584b001aeb35df8 postgresql-jdbc-8.4.704-4.el6_10.noarch.rpm Source: 72decf7b6b1f789fbe15f76d71c768e6d5c95ea45c37ceea449a6b578ee61a8c postgresql-jdbc-8.4.704-4.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 11 Date: Fri, 7 Aug 2020 13:01:09 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3345 Important CentOS 6 thunderbird Security Update Message-ID: <20200807130109.GA6747(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3345 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:3345 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5ca8ca5aed2e182a74276462102ae266b546b12bc4823ebcd7cc07b4412f741a thunderbird-68.11.0-1.el6.centos.i686.rpm x86_64: d00deca958deb6d40c61b780599f9d56822cca073952ad0db29041d2249d7c5e thunderbird-68.11.0-1.el6.centos.x86_64.rpm Source: 3c8d27d6bbb365d6be581f8bddf126d8d3f6df8bfc173377a4189e5cb93c372d thunderbird-68.11.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 12 Date: Fri, 7 Aug 2020 13:02:21 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3233 Important CentOS 6 firefox Security Update Message-ID: <20200807130221.GA6894(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3233 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:3233 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7044f145b77b097e9563a8f3db28972097d7f4690d7a80199e49b49d3d61cc5e firefox-68.11.0-1.el6.centos.i686.rpm x86_64: 7044f145b77b097e9563a8f3db28972097d7f4690d7a80199e49b49d3d61cc5e firefox-68.11.0-1.el6.centos.i686.rpm 8ee0612e553f9f3f549f841001f353e36807f2e803fc80e4e053e445d9eb741c firefox-68.11.0-1.el6.centos.x86_64.rpm Source: ef35f3d262b5627d8b0868c42ab00cb41ffd5709a07db75b5a16ab638020a3e7 firefox-68.11.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 13 Date: Fri, 7 Aug 2020 13:03:15 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3344 Important CentOS 7 thunderbird Security Update Message-ID: <20200807130315.GA7027(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3344 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:3344 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 1843f66766dd4e3ec0481895eb214582b167995238898e2666b1dcb523e0a7a1 thunderbird-68.11.0-1.el7.centos.x86_64.rpm Source: ad6d42bca1ff78685b464bb05fab28a9ddedde5fc9c7a4a71de77fef45fedc6d thunderbird-68.11.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 14 Date: Fri, 7 Aug 2020 13:04:05 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3253 Important CentOS 7 firefox Security Update Message-ID: <20200807130405.GA7152(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3253 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:3253 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c05f2405cfacec8c3474e4d03a33e999ca1ce8cd292603d6a09ae4709a2b3d37 firefox-68.11.0-1.el7.centos.i686.rpm d33e218058831eee24361057e3fc29e409d9ae6f2e73f76af0541a2311584a89 firefox-68.11.0-1.el7.centos.x86_64.rpm Source: 66241fa85b0f1176b74f76794478a4005fdf335985bf7f8c117d064b7b6e9636 firefox-68.11.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 15 Date: Fri, 7 Aug 2020 13:25:11 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:3348 CentOS 7 curl BugFix Update Message-ID: <20200807132511.GA7738(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:3348 Upstream details at : https://access.redhat.com/errata/RHBA-2020:3348 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ee225e394bfa89bf736af8ccbdc1de6dd411a05ede84e4493d27f935cee02a32 curl-7.29.0-57.el7_8.1.x86_64.rpm 88ee4332615170eedaac483e9c5f7d0751be7ffcf7afd65cd6f2e8ce384e6e34 libcurl-7.29.0-57.el7_8.1.i686.rpm 8efe21c365f79b4f7aa8f282faecff8f6d5acf301bd09c85d475eb736077c2db libcurl-7.29.0-57.el7_8.1.x86_64.rpm ad59135146f02ca9ba3bb097f53883bd64e4a4b37df29f5f87c07e3728cd895d libcurl-devel-7.29.0-57.el7_8.1.i686.rpm 4e5cb836df4034cb950555892c1260a7903557e80f9c40ac80689627054674a5 libcurl-devel-7.29.0-57.el7_8.1.x86_64.rpm Source: cb8a06720f8bf740f3f8023d4da375ede8dd4d5876f4c1a2969e20e5a4e269a5 curl-7.29.0-57.el7_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 16 Date: Fri, 7 Aug 2020 13:28:34 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:3349 CentOS 7 sssd BugFix Update Message-ID: <20200807132834.GA8318(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:3349 Upstream details at : https://access.redhat.com/errata/RHBA-2020:3349 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 951fc236cc64f56e35cbac9230458a0b7e9f02ce0ca94111f13b21728f3b01d6 libipa_hbac-1.16.4-37.el7_8.4.i686.rpm de6f5b0f12a323a952eac6fb26a71f83c4b31a17e73b674f17e0c25c3f0d5f28 libipa_hbac-1.16.4-37.el7_8.4.x86_64.rpm bdf75258c4c5982943a0164ed90fb4e38c59e624b2d32c77243a08c7572773a8 libipa_hbac-devel-1.16.4-37.el7_8.4.i686.rpm 9e9e5f103edaffb9279059b2cf845ba927049d9afee19a71882882af28fbe12f libipa_hbac-devel-1.16.4-37.el7_8.4.x86_64.rpm 18feb09f3b6e5ac1a0aac276866af303cde065e854ab4351f0e9f6c43850f177 libsss_autofs-1.16.4-37.el7_8.4.x86_64.rpm 4a257178b7d51080d29e42e53a5f92872cdf2243577473f2697565426c704a5f libsss_certmap-1.16.4-37.el7_8.4.i686.rpm 9f7df78e88a9ebcf9ac28fd22145329ef2187f908b3331e46c941ad35f27c590 libsss_certmap-1.16.4-37.el7_8.4.x86_64.rpm 0aba5df1a174057050040f1cc7a8f0ae762fe8f0629dee49fe30b083ad25e9c3 libsss_certmap-devel-1.16.4-37.el7_8.4.i686.rpm 7d4d2077888381b8547bde72a0147cd0a07b14c3665d3ed357d2f0cabf16565b libsss_certmap-devel-1.16.4-37.el7_8.4.x86_64.rpm 40af5b1a1322d4f5a1e460d7159c6b22e20cb5860c374a5fb0bcd8416f7f4cd6 libsss_idmap-1.16.4-37.el7_8.4.i686.rpm c3f3aec998aabd137978361995084df8c304b6cf6dcb6d52a370810143408dd7 libsss_idmap-1.16.4-37.el7_8.4.x86_64.rpm 604c9865933f37465ce10184b730e8f3def1aaaa530a1b673c6716d30ba5894f libsss_idmap-devel-1.16.4-37.el7_8.4.i686.rpm 549bb38e7f9f2b41b58ed83df096931c805553c62cc77bef63a5132ca464d3ac libsss_idmap-devel-1.16.4-37.el7_8.4.x86_64.rpm da0ff01442f292320033fcf40983e8cc391f3147cc4b9d82ec110e6b4a8612ee libsss_nss_idmap-1.16.4-37.el7_8.4.i686.rpm 776d9e1183b29511bb664261fcb50ff18cfcf03f09983ee0cda2262d1bf9214f libsss_nss_idmap-1.16.4-37.el7_8.4.x86_64.rpm 0bb688d4fdb510b6aa3305dd4f04eb123defdb4b1b4e7adf5ea05fd8c8035910 libsss_nss_idmap-devel-1.16.4-37.el7_8.4.i686.rpm 83ef5b96c747c01f20f91131e073a42b034309463c767434107ac7622cb6588d libsss_nss_idmap-devel-1.16.4-37.el7_8.4.x86_64.rpm f9a25ae69ede6a881d1ee057dfc324ba166a2437b2ee76675aae535e03a6d292 libsss_simpleifp-1.16.4-37.el7_8.4.i686.rpm 8deb1cf27707b4157e2d35b534127a519e5c9ec2ed04a66fdc2ee7eac0e3a9b4 libsss_simpleifp-1.16.4-37.el7_8.4.x86_64.rpm ad330f1c4d29533cd112e262db9aac8d6cd05d8f7c95e92d6b403a45ac934423 libsss_simpleifp-devel-1.16.4-37.el7_8.4.i686.rpm 975a0ec56c1e93233de9b5f1b88c36c089d0f97bdab02f1338de5a8e2def69f3 libsss_simpleifp-devel-1.16.4-37.el7_8.4.x86_64.rpm 11648abbd4f5328bb3ec6ccc429907af6e57508806777147a4163dd47bbd657c libsss_sudo-1.16.4-37.el7_8.4.x86_64.rpm 08ae769c871b5a5ba80e3d03b3633ac25bd441ee207c5ece704b30d78ff0a73a python-libipa_hbac-1.16.4-37.el7_8.4.x86_64.rpm a88b7709cda2745e911e7b17a20bd551c92d0a76fec7bd71df37075d69a90764 python-libsss_nss_idmap-1.16.4-37.el7_8.4.x86_64.rpm f7131988ed7fd2ef3bb0029ffc17668dbb3ba55046e443bac889a36fe10dc0c1 python-sss-1.16.4-37.el7_8.4.x86_64.rpm 4033e9d709feccb8259d1502d2e4b628ad8784a4411ed8b5be28bda4da62414b python-sssdconfig-1.16.4-37.el7_8.4.noarch.rpm 2e7004d1968ff0e18ec095c8abc1a73489809b1396c392e4c4761c434f6084e7 python-sss-murmur-1.16.4-37.el7_8.4.x86_64.rpm f532fdec191ef4df783588315603da50f35c3575b082e22df9c5dc7b672c5002 sssd-1.16.4-37.el7_8.4.x86_64.rpm b05cf098b124b0e5c8ead1606bf991143528c832ed99eb96560a13bd0225ad48 sssd-ad-1.16.4-37.el7_8.4.x86_64.rpm 4fb4b7a169cbdbcea5b5cde8e127c75879de15cec42e7b8a1b319c2d2453c213 sssd-client-1.16.4-37.el7_8.4.i686.rpm 7a46b3da0245464a79e1281a79f0596c8dcc4a061e4810c2c636840e930b7472 sssd-client-1.16.4-37.el7_8.4.x86_64.rpm c6e4ed20c732c4eb29c6832618c6c9cb2228db0d78992e1ad01bba4d146cecf4 sssd-common-1.16.4-37.el7_8.4.x86_64.rpm 2763fdaeb5f910cb6707a6f6aaa0a478911f0a3c9076496462911d923862b33d sssd-common-pac-1.16.4-37.el7_8.4.x86_64.rpm a0117e31fc98d241300acd5f5c842689f64c41ae0dafd733ae76211a536b99a9 sssd-dbus-1.16.4-37.el7_8.4.x86_64.rpm 3ed23e867739a86334b5c8e928dfd2c6111426cec4c14570b43fc89b25ed7fa3 sssd-ipa-1.16.4-37.el7_8.4.x86_64.rpm a1a3dbd2e49bffcd5290a411f675d0202a93bbe4567cc51c81a0771fb31715ec sssd-kcm-1.16.4-37.el7_8.4.x86_64.rpm 94a2e518b7228034d268b8a114a1b1f233f017cb28dffcf88e82c2207fd73d4a sssd-krb5-1.16.4-37.el7_8.4.x86_64.rpm 060c08fb78f3758c88f9a4a6ee5eeba408b602f1d3357b83180566a4d8d93916 sssd-krb5-common-1.16.4-37.el7_8.4.x86_64.rpm 4ec48a061d2ab2c5e771589ff4dbe2d7e8334ea2e2d2e9c3834f8994379a6bdb sssd-ldap-1.16.4-37.el7_8.4.x86_64.rpm ce1e7a403bb1a64cf8beb0d2fbf12fc85dab20960e978efe858386b687531668 sssd-libwbclient-1.16.4-37.el7_8.4.x86_64.rpm e1d4ed400e1a67410fc8debcd49ea116a9997543eb5bc7fd044ed76f9f4dfa3a sssd-libwbclient-devel-1.16.4-37.el7_8.4.i686.rpm 2980c43373fa3a063fb892d311e776a297ccc7582a9d188fc6e9129c2d38bd2f sssd-libwbclient-devel-1.16.4-37.el7_8.4.x86_64.rpm 3db373a29f4ebc71670875aa680289bcba5490a0b4798d116df09989f687d9d5 sssd-polkit-rules-1.16.4-37.el7_8.4.x86_64.rpm 7a8b167357b7897b95af6ab8818f3107c4f2e2d045f3dfa585278c6a8696f1c7 sssd-proxy-1.16.4-37.el7_8.4.x86_64.rpm 2ec2acfb61607e8c0f070323ec796f5981153d374bc696492c569d75fe8b02c7 sssd-tools-1.16.4-37.el7_8.4.x86_64.rpm f7c1c4f96c53f3ac75617688f4bd3380f2f14c83c634af544813cdc7218f3551 sssd-winbind-idmap-1.16.4-37.el7_8.4.x86_64.rpm Source: 39b815656cea1f86b38e04528e794641535404deeeb9d164982942da17617042 sssd-1.16.4-37.el7_8.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 17 Date: Fri, 7 Aug 2020 13:31:27 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:3352 CentOS 7 libguestfs BugFix Update Message-ID: <20200807133127.GA9036(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:3352 Upstream details at : https://access.redhat.com/errata/RHBA-2020:3352 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 77b147b4b83ab5a39862886802f52743204acdd211bc182717baa04d9f3d18e8 libguestfs-1.40.2-9.el7_8.1.x86_64.rpm 030459e529cc50051e5b486606e6585957b502d24768e1d5644bc4e10d3e43c2 libguestfs-bash-completion-1.40.2-9.el7_8.1.noarch.rpm 55051979ecdc81def367969a4afb981ec816f13615ae3c99f94746eb5e29cf3d libguestfs-benchmarking-1.40.2-9.el7_8.1.x86_64.rpm 13823b9874c6d87cd746037bb59fc86c19f9131553c740f5a28bb474465270fa libguestfs-devel-1.40.2-9.el7_8.1.x86_64.rpm 45120039734c27b8499740d683d22a8f7ac9caeb378d4ceb59009ab695d222f7 libguestfs-gfs2-1.40.2-9.el7_8.1.x86_64.rpm 59419b8f6c0889f74674dcb3309818a41e40e77bd42c73e019a25d13e7429be7 libguestfs-gobject-1.40.2-9.el7_8.1.x86_64.rpm 204135b4c46d77a895db416f6451a62678f8ff946c7dc72c5fd69cf149ef6f7a libguestfs-gobject-devel-1.40.2-9.el7_8.1.x86_64.rpm 48d9853bf1961cb1f40090f854c994532d7d5784ebecd42882d2ce2b527414ab libguestfs-inspect-icons-1.40.2-9.el7_8.1.noarch.rpm ba27f4a03b548f85a6d41bc6aa93580cc0855210c77b8061e858663ac9dd9116 libguestfs-java-1.40.2-9.el7_8.1.x86_64.rpm 2e6ea0b023c47063b5197ca090e3312e686b52eea237f4f98ad8c35d8c79c13b libguestfs-java-devel-1.40.2-9.el7_8.1.x86_64.rpm 0b3e153df45c7d406efe2db0487ca2278493d2a0a4ed8c544c9cf19ba5ee927c libguestfs-javadoc-1.40.2-9.el7_8.1.noarch.rpm 29608d37055f960c98adba1aba18ef51823f4dd263548fab29e3c5b080297eca libguestfs-man-pages-ja-1.40.2-9.el7_8.1.noarch.rpm 976e9fb45bb02ca003c0a846d114f612b404387727273ee7ac179eb03dbaa98b libguestfs-man-pages-uk-1.40.2-9.el7_8.1.noarch.rpm 7805602c8817b566df468e17525b0d3dcca02e220d786e532f3c9970e54a00b1 libguestfs-rescue-1.40.2-9.el7_8.1.x86_64.rpm ab9f32e0dfe2af2d8859cf6c07cc0e58391fbfdab9e0be2ec86110bc3fd878b5 libguestfs-rsync-1.40.2-9.el7_8.1.x86_64.rpm ed887dc7c8d39b16fb6c6742b892f83a2aecfbbd7d9174607ac900f2e00f57eb libguestfs-tools-1.40.2-9.el7_8.1.noarch.rpm 51d4e1034df4345f7a8b94264648a482bca9dde1a8aad4bccce6cfdc613d848d libguestfs-tools-c-1.40.2-9.el7_8.1.x86_64.rpm 3e9092ea1ce89c1f922fd320d68156a6200e8a11c8f15d1d18987d0bdc3dff45 libguestfs-xfs-1.40.2-9.el7_8.1.x86_64.rpm 56f4f6a716c7b1cf270bb210147af70f38e281277cc812d9724c7c4992890e1e lua-guestfs-1.40.2-9.el7_8.1.x86_64.rpm f29152aa7fe69f3eb768ed4b341443ac2c2b1bb9df914a11954da95e738f51da ocaml-libguestfs-1.40.2-9.el7_8.1.x86_64.rpm c8de13380a0feddd18abdf1b9a29eceaf0cb24eea7091a310d366af74ed67a69 ocaml-libguestfs-devel-1.40.2-9.el7_8.1.x86_64.rpm 2c7061002ca911bf7418481b87d84c606d0ca1dfb74a35d80bef875208354a9b perl-Sys-Guestfs-1.40.2-9.el7_8.1.x86_64.rpm 5e45cc8bbd922d98f9bf9d2f042a215ed712ea17b1a41011945d52dbce844059 python-libguestfs-1.40.2-9.el7_8.1.x86_64.rpm a2470419fc05aca99cb87d9218a0ed7f27b7a5694278af881222e9047ae6440b ruby-libguestfs-1.40.2-9.el7_8.1.x86_64.rpm 7daf3c9007c7216488c486e1a69c894c3e96f8f071e6fa2b4ebd312baa002ab8 virt-dib-1.40.2-9.el7_8.1.x86_64.rpm be944d66f6c6da09ae48e6521ca777ec34020f7d8495b5c6668b5699ac8ed5da virt-p2v-maker-1.40.2-9.el7_8.1.x86_64.rpm 916470f0485620ed84cc9f22d55c823f39c260f2b3447847e882d223b1d15f6f virt-v2v-1.40.2-9.el7_8.1.x86_64.rpm Source: 9d55a698084e85eea8bec825f62488100110889d17abd241c12cb9464d83ffa8 libguestfs-1.40.2-9.el7_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 18 Date: Fri, 7 Aug 2020 13:38:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:3354 CentOS 7 libreswan BugFix Update Message-ID: <20200807133835.GA9247(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:3354 Upstream details at : https://access.redhat.com/errata/RHBA-2020:3354 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c205e6c8f267b531e6cb7cdabe53c2b3cda12f1afd4735ece2a55f5c116d0159 libreswan-3.25-9.1.el7_8.x86_64.rpm Source: 9fa72dc64fb2cbf7abd5961455b8d7de3e7bf228fb8380dc66ff74d573de1492 libreswan-3.25-9.1.el7_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 19 Date: Fri, 7 Aug 2020 13:40:12 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2020:3355 CentOS 7 subscription-manage BugFix Update Message-ID: <20200807134012.GA9474(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2020:3355 Upstream details at : https://access.redhat.com/errata/RHBA-2020:3355 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 1c927db066d49d2572c84d77b53b0152ce2ba9a04520f93e897c15cdc8fd46a5 python-syspurpose-1.24.26-4.el7.centos.x86_64.rpm 31468f95062ca8fa88067ef39ba88f6eecd517d7a203635e18d88225a8acb427 rhsm-gtk-1.24.26-4.el7.centos.x86_64.rpm 9aa646de32ca88972bf93a978410a05d61c3d74879acf70f8887856b278d25c2 subscription-manager-1.24.26-4.el7.centos.x86_64.rpm 6dac13f254edbe203f0d68e9d6b4bb5eb7a7f0c862351d15722295a78d9a257d subscription-manager-cockpit-1.24.26-4.el7.centos.noarch.rpm 251a068e56bb4816188fbce34d909886b0b02c3bad468d0e4e3825739aee9e14 subscription-manager-gui-1.24.26-4.el7.centos.x86_64.rpm 0b8c765849f43d0d81d66dfeb49dafd2f2e14b0aa2e7dec718c78cce7d2efb1d subscription-manager-initial-setup-addon-1.24.26-4.el7.centos.x86_64.rpm 194e384492a53d4bff6c4b772d366eb2594020465973fd4442d483cde5117b04 subscription-manager-plugin-container-1.24.26-4.el7.centos.x86_64.rpm 6454bc386904286cab7d050a3caec7ef1a83d84dd106a943e59fc5b5f232f014 subscription-manager-plugin-ostree-1.24.26-4.el7.centos.x86_64.rpm b02caf885b59066ab1966c0082bf91a5eeffb7606f3f9d26807f53cea39eab32 subscription-manager-rhsm-1.24.26-4.el7.centos.x86_64.rpm c0e63169421d350f84ad5b85faa7513a4404dedc34039fa7035730e980c699f1 subscription-manager-rhsm-certificates-1.24.26-4.el7.centos.x86_64.rpm Source: ff8247b904efa20e0d45b9f8c21545793e20bebf55dfd9cd708b4d8d2695605a subscription-manager-1.24.26-4.el7.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 186, Issue 1 ***********************************************

1 0

Running commands as apache user
by H 08 Aug '20

08 Aug '20

I have a dilemma: I have nextcloud running under user and group apache, as recommended by the installation. I now have to run some nextcloud commands but even as root I cannot su to user apache because "this account is currently not available". Is there a way around this? The commands must be run as user apache...

2 2

Reset booleans to default value ?
by Nicolas Kovacs 07 Aug '20

07 Aug '20

Hi, Here's a list of all the booleans I tweaked on my server running CentOS 7: $ sudo cat /etc/selinux/targeted/active/booleans.local # This file is auto-generated by libsemanage # Do not edit directly. named_write_master_zones=0 httpd_can_sendmail=1 httpd_unified=1 ftpd_full_access=1 httpd_can_network_connect=1 spamd_enable_home_dirs=1 How can I "reset" (in a manner of speaking) these booleans to their default value post-install? Ideally, the booleans.local file should be empty, but since it's auto-generated, there's not much sense in simply erasing it. Curiously enough, I didn't find any information about this. 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 Mob. : 06 51 80 12 12

1 0

rsync upgrade
by Christopher Wensink 07 Aug '20

07 Aug '20

Can anyone tell me the repository to use to upgrade to a version of rsync later than 3.1.2? Chris -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwensink(a)five-star-plastics.com www.five-star-plastics.com

10 12

Thunderbird 68.10.0
by Chris Schanzle 07 Aug '20

07 Aug '20

Sorry if I'm being overly impatient, but is there some snag with releasing Thunderbird 68.10.0 for EL8? [RHSA-2020:3038-01] Important: thunderbird security update https://access.redhat.com/errata/RHSA-2020:3038 Thanks!

3 3

Centos 7 shim fix failed
by david 06 Aug '20

06 Aug '20

Following the advice on this mailing list, I rebuilt (from scratch) Centos 7.8. I added the following line into /etc/yum.conf before the first update: exclude=grub2* shim* mokutil The system worked fine. I was able to do general updates yum -y update and all was well. HOWEVER, following Johnny Hughes' directions: a) remove the 'exclude' line from yum.conf b) perform update: yum -y update c) reinstall kernel. Here the instructions were vague, so I typed in... yum reinstall kernel-3.10.0 deriving the "3.10.0" label by the output of rpm -qa | grep kernel Yum got up to the point: Running transaction Installing : kernel-3.10.0-1127.el7.x86_64 1/1 at which point the process appeared to hang. No further output happened for five minutes. I opened a different terminal and entered "shutdown -r now". The result is an unbootable system. What did I do wrong? I must admit that there are multiple copies of advice on the mailing list, so perhaps I followed the wrong one? ------------------------------ So now, I tried the 'repair' mechanism, but couldn't make that work either. So, it was back to initial from-scratch install. David

8 13

CentOS 8 DNS resolution not working as expected
by isdtor 06 Aug '20

06 Aug '20

[root@localhost ~]# lsb_release -d Description: CentOS Linux release 8.2.2004 (Core) [root@localhost ~]# cat /etc/resolv.conf # Generated by NetworkManager search subdomain.company.com company.com nameserver 1.2.3.4 nameserver 5.6.7.8 [root@localhost ~]# host foo foo.subdomain.company.com has address 1.2.3.4 [root@localhost ~]# host foo.subdomain Host foo.subdomain not found: 3(NXDOMAIN) [root@localhost ~]# host foo.subdomain.company.com foo.subdomain.company.com has address 1.2.3.4 [root@localhost ~]# The expected result is that the lookup for foo.subdomain works, like it does under CentOS < 8. I tested this also on a RHEL8 machine and followed https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht… to disable DNS processing by NM, but this did not change the outcome. How can the pre-CentOS 8 behaviour be restored?

3 5

CentOS Security Advisories OVAL feed??
by centos＠niob.at 05 Aug '20

05 Aug '20

Dear List, I have spent some time playing around with oscap and the RHEL OVAL feed (https://www.redhat.com/security/data/oval/v2/RHEL8/, also check Chapter 16 of the RHEL 8 Design Guide). Because I could not find an existing OVAL file for CentOS, I downloaded one of the RHEL8 files and managed to modify (eg. the rhel-8.1-e4s.oval.xml) it to make it work on a CentOS machine. Basically I just had to change the package signing key check to use the CentOS key and I had to replace the redhat-release RPM package name with "centos-release". Obviously, this would violate all kinds of rights if redistributed, due to the fact that the upstream vendor is named all over the place, but technically it "worked". On an internal system running a freshly updated CentOS 8.1 system I ended up with three errors, titled: * RHSA-2019:4269: container-tools:rhel8 security and bug fix update (Important) * RHSA-2019:3403: container-tools:rhel8 security, bug fix, and enhancement update (Important) * RHSA-2019:2799: nginx:1.14 security update (Important) This raises some questions (some of them connected), namely: Q1) There are no equivalent CESA advisories for those RHSA advisories: why is that? Note that there are also no equivalent CentOS packages to those mentioned in the RHSA advisories. (My guess: because, when the advisories where issued, Centos already had moved on to 8.2) Q2) Does this indicate a problem in the release process / handling of upstream updates on the side of the CentOS project? Were the advisories missed at the time of issuance? Q3) Does this indicate that only the latest CentOS (minor) release can be considered "secure" or "patched"? Q4) Is there a native OVAL file released from the CentOS project covering these issues? It could be extremely similar to the RHEL one, but it should take the answers to the above questions into account (eg. it could require the latests minor-release and there would only be one file for CentOS 8 if the answer to Q3 is "yes"). Q5) If the answer to the last question is "no": shouldn't there be such a resource? Thanks for any answers. peter

5 8

Announcing the version 1.0 hexpeek release!
by hexpeek＠hexpeek.com 05 Aug '20

05 Aug '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Announcing the version 1.0 hexpeek release! I am pleased to announce the first stable release of hexpeek, which seeks to be an efficient, powerful, and portable hex editor for files of all kinds and sizes. This release improves on the beta release with a live undo, a greatly increased backup depth, better support for writing to non-seekable files, and some miscellaneous cleanup. Visit https://www.hexpeek.com for more information. Out of respect for the bandwidth on this mailing list, I do not plan to announce future hexpeek releases here. There is a mailing list on https://www.hexpeek.com where future announcements will be posted. If you are interested in hexpeek becoming a package/port for your distro, please let me know. -----BEGIN PGP SIGNATURE----- iQJIBAEBCgAyFiEEfeRsn/lRU2hTiGbecMFr/kefAX8FAl8qMysUHGhleHBlZWtA aGV4cGVlay5jb20ACgkQcMFr/kefAX9U9w//QlTM/zrd25att9/yYcqbQPkDAqhr sjCtSfMoY6sLlsI1IFR1GDu0v0l+TiW4R2iDDn8dD7esLBrhHXe+QLWd9OjioCF7 jB3Tpg+ozk9GMmwDFglbU6hiwTAM4w7O4NKrLEuR/kQoWZzweEXGjIV2ytWhCpps tsl3c/t2rSG0SqlhcHrQpy0uZ38v7f7+o3BCH23gqzdAW+mvvPC9iYLfYJqUGDRt fc5zmouLai9ZAARpqK3Mhu/RTlv8DnxpmsIt2cSJ6OFVbonKBqvDk1RFbLqSUwhU iJv+wMF97f2HT7g1RCNG+GGClD0TvceFP+8qhwIYUhBaRXLe1u+gEEqXvmlURd0h m77ydS58Z1ND1YGw01rTTBzDxnW21HHTFCqGHfRKOjVcLEQrt8CkTvcf7tM5fX+n fodXdEv8k8rrhbOYDyWqurdekWPZCrvrzEPuF+Ww/W6ownW8RwP2cgNccfOiuC2P dTJdIe5j4VASLtC17iUcwDiQuZYWdK5oBlf/ws9flInFHOlGVUGXuD1pum05Iq1u OZeJEHJj+yvP1drm4A1O8z3r8XfPa2WmWsQBc0TP8lOvU3l/E20p1T3TPs8EQbqA dRJyN1PcAv63DE0USa2P+tB18jZkvDV15YT/6yDkOtKEgIdtSsw6H5oscs96LfuI cKK++c04aRN9e28= =02ro -----END PGP SIGNATURE-----

2 1

Re: [CentOS] Safe to do yum update now?
by Marc Balmer 04 Aug '20

04 Aug '20

> Am 04.08.2020 um 17:59 schrieb Jerome Lille <jerome.lille(a)ownbay.net>: > > Hello > > Luckily I was not afflicted by this boot hole problem. I haven't done > yum update in a week or so. I just want to make sure that now it is > safe to do yum update? It is. > > /Jerome > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos

1 0

Safe to do yum update now?
by Jerome Lille 04 Aug '20

04 Aug '20

Hello Luckily I was not afflicted by this boot hole problem. I haven't done yum update in a week or so. I just want to make sure that now it is safe to do yum update? /Jerome

1 0

Re: [CentOS] Boot failed on latest CentOS 7 update
by david 03 Aug '20

03 Aug '20

At 12:50 PM 8/1/2020, Kay Schenk wrote: >Totally and completely on my HP microfiber. Wouldn't get past anything to >even get me into the grub menu. NOT AMUSED! > >_______________________ >Kay Schenk I was going to confirm the same, but the system that became unbootable was my mail system :-( Apparently, the SHIM/GRUB bug has hit both Centos 7 and 8. Too bad Ubuntu is enough different that makes it hard to switch. David

21 38

Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
by david 03 Aug '20

03 Aug '20

At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >Hi Johnny, >thank you very much for clarification. > >You said that in the centos infrastructure only one server got the problem. >What are the conditions that permit the breakage? There is a particular >configuration (hw/sw) case that match always the problem or it is random? > >Thank you I have two servers running Centos 7 on apple hardware (one mac-mini and one mac server). They both failed to reboot a few days ago. So perhaps whatever anti-boot bug hit Centos 8, also hit Centos 7. I can't tell what version got updated since the system simply fails to boot. I don't even get a grub screen. I'll have to rebuild the systems from scratch. David

12 27

8.2.2004 Quick recovery and fix for unbootable machines
by Alan McRae 03 Aug '20

03 Aug '20

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture (shim-<arch>-15-11.el8.<arch>.rpm) I have tested this by breaking a machine and then recovering it. It works for me. I hope someone finds it useful. Let me know. Regards Alan HOW TO BOOT AN UNBOOTABLE MACHINE ================================= 1) Download a copy of rEFind. This is a UEFI boot manager. Burn it to a USB key. # wget -O refind.zip http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.… # unzip refind.zip # cd refind-flashdrive-0.12.0 # dd if=refind-flashdrive-0.12.0.img bs=4096 of=/dev/sdX (sdX is the device for your USB key, this will be erased, use the whole device use sdX not sdX1) 1800+0 records in 1800+0 records out 7372800 bytes (7.4 MB, 7.0 MiB) copied, 0.980893 s, 7.5 MB/s 2) Turn off secureboot in your UEFI hardware. 3) Boot the USB key. You should get a colourful screen with icons and a filename below. Use the left/right arrow keys to select the correct grubx64.efi. Hit space to boot. Your usual grub menu should appear and the system should boot normally. HOW TO FIX THE PROBLEM ===================== 1) We need to downgrade the shim package. Now your system is running get an older copy of the correct shim package for your architecture from the CentOS installation media (e.g. CentOS-8.2.2004-x86_64-dvd1.iso) and install it. # mount CentOS-8.2.2004-x86_64-dvd1.iso /mnt # cd /mnt/BaseOS/Packages # cp shim-x64-15-11.el8.x86_64.rpm /root # cd /root # umount /mnt OR Get the package from a CentOS mirror: # cd /root # wget http://ucmirror.canterbury.ac.nz/linux/CentOS/8.2.2004/BaseOS/x86_64/os/Pac… 2) We can now reinstall the older shim package using yum. This will downgrade the package to the working version. # yum install shim-x64-15-11.el8.x86_64.rpm Last metadata expiration check: 2:11:11 ago on Sun 02 Aug 2020 11:31:06 NZST. Dependencies resolved. ==================================================================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================================================================== Downgrading: shim-x64 x86_64 15-11.el8 @commandline 647 k Transaction Summary ==================================================================================================================================================================================== Downgrade 1 Package Total size: 647 k Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Downgrading : shim-x64-15-11.el8.x86_64 1/2 Cleanup : shim-x64-15-13.el8.x86_64 2/2 Verifying : shim-x64-15-11.el8.x86_64 1/2 Verifying : shim-x64-15-13.el8.x86_64 2/2 Installed products updated. Downgraded: shim-x64-15-11.el8.x86_64 Complete! 3) Your system should now boot normally. 4) add "exclude=shim*" to /etc/yum.conf to prevent the broken one being reinstalled. You should now be able to run 'yum update'. Remove the exclude= when a proper fix becomes available.

5 5

GUI boot failure after latest shim (etc) updates
by Fred Smith 03 Aug '20

03 Aug '20

This isn't the problem everyone else has been talking about, but... I made sure that yum update offered the packages Johnny said it should then updated. when I rebooted everything looked normal except it was taking a long time to bring up the login screen. Flipped over to ALT-F2 and saw a message about waiting for Plymouth boot screen to quit. I waited a while and it went up to (and past) 15 minutes. It said "no limit" so it apparently would have gone on forever. I couldn't get to a text-mode screen with ALT-f[2-6] so I went down to my Linux laptop to see if I could ssh into this box. Lo and behold, ssh worked fine. So I ran top and saw a plymouth (or plymouthd, I forget which) at the top of the list. killed it, came back upstairs and it was no longer spewing that message. now ALT-f2 gave me a text login, that I'm using now. I ran startx and after a long-seeming wait I get a desktop, but it is NOT my normal Mate desktop. Might be Gnome (since I installed a Centos Gnome system and retrofitted Mate from EPEL). Johnny had said we needed to make sure the kernel was installed along with the shim, et al. I looked at the list of files YUM wanted to install and saw some kernel files, so I assumed all was well. But maybe I missed something. What info can I provide to help figure this out? Or, what Kernel files should I force to be (re)installed? Also, I don't very often manually force a kernel install, but I know that some of the files are updates and some are installs, I'd appreciate a reminder of which is which so I can force it. Thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The eyes of the Lord are everywhere, keeping watch on the wicked and the good. ----------------------------- Proverbs 15:3 (niv) -----------------------------

1 0

Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
by david 02 Aug '20

02 Aug '20

At 07:57 AM 8/2/2020, you wrote: >On Sun, 2 Aug 2020 at 10:20, david <david(a)daku.org> wrote: > > > > > > ><snip> > > > > > > > > > > > >> Yes .. it should be on mirror.centos.org now .. you could change the > > > >> repo where your updates come from.Ã OR > .. wait for that mirror to get > > > >> updated. > > > > > > > > > > > > I just did > > > > yum clean all > > > > yum update > > > > > > > > and 15-8 showed up.Ã Maybe the 'clean all' > > > did it, or maybe just showed up. > > > > > > > > I applied the update (yum update), rebooted and... > > > > no boot.Ã Just a blank screen. > > > > > > > > Hardware is a Mac-Mini :-( > > > > > > > > This is not an essential machine, so I could re-install (from > > > > netinstall) if you think it's worth the effort. > > > > > > > > Or what? > > > > > > > > David > > > > > >You just need to reinstall the kernel and it should work. > > > > > > > Sorry for being so ignorant, but I don't > > understand "just reinstall the kernel". I don't > > know how to translate that into a specific yum or rpm command. > >I agree it is a lot of shorthand because of expectations. In the end >we (the list) don't know what you have on your system or what state it >is in. In order to get that information to help we would need you to >try the following: > >1. boot using a working USB/cdrom/netboot path and installer >2. choose the rescue mode >3. have the rescue mount the disks as local and chroot into the >system. << if possible have the system also bring up networking >> > >Then >yum list kernel shim grub2 mokutil > >It would also help to know which kind of Mac Mini it is (year, model, >firmware versions). Apple changes the internal hardware of these >things and how they boot so if there it may be that a particular model >is more affected than others. How does one obtain that information? There's nothing written on the box. David

2 1

Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
by david 02 Aug '20

02 Aug '20

><snip> > >> Yes .. it should be on mirror.centos.org now .. you could change the > >> repo where your updates come from.Â OR .. wait for that mirror to get > >> updated. > > > > > > I just did > > yum clean all > > yum update > > > > and 15-8 showed up.Â Maybe the 'clean all' > did it, or maybe just showed up. > > > > I applied the update (yum update), rebooted and... > > no boot.Â Just a blank screen. > > > > Hardware is a Mac-Mini :-( > > > > This is not an essential machine, so I could re-install (from > > netinstall) if you think it's worth the effort. > > > > Or what? > > > > David > >You just need to reinstall the kernel and it should work. Sorry for being so ignorant, but I don't understand "just reinstall the kernel". I don't know how to translate that into a specific yum or rpm command. However, since this is a crash-and-burn system, I'm going back to a virgin install with netinstall of 7 2003. I'll let you know what the results are. --------------- On a Mac-Mini, which got hit by the bug in shim, I re-installed Centos 7 2003 from netinstall, selecting minimal as the software selection. The reboot worked fine. So, I next tried "yum -y update", noticed shim 7-8 got selected. However, at the completion of the update, I did a reboot and got a blank screen. No grub choices. Not good. David

1 0

Boot failed on latest CentOS 7 update
by Kay Schenk 02 Aug '20

02 Aug '20

Totally and completely on my HP microfiber. Wouldn't get past anything to even get me into the grub menu. NOT AMUSED! _______________________ Kay Schenk

2 2

pgbouncer.pid Permissions on CentOS 7
by Bee.Lists 01 Aug '20

01 Aug '20

I’ve installed pgbouncer on CentOS7 and it’s reliant upon a .pid file: 2020-07-31 04:58:34.082 EDT [3682] DEBUG parse_ini_file: 'logfile' = '/var/log/pgbouncer/pgbouncer.log' 2020-07-31 04:58:34.082 EDT [3682] DEBUG parse_ini_file: 'logfile' = '/var/log/pgbouncer/pgbouncer.log' ok:1 2020-07-31 04:58:34.082 EDT [3682] DEBUG parse_ini_file: 'pidfile' = '/var/run/pgbouncer/pgbouncer.pid' 2020-07-31 04:58:34.082 EDT [3682] DEBUG parse_ini_file: 'pidfile' = '/var/run/pgbouncer/pgbouncer.pid' ok:1 However the service isn’t starting because the ownership of the parent directory, pgbouncer:pgbouncer results in some permissions issues: 2020-07-31 04:58:34.089 EDT [3682] FATAL could not open pidfile '/var/run/pgbouncer/pgbouncer.pid': Permission denied /var/run/ has special flushing behaviour which I want to retain, but I need to get around this permission issue. Changing ownership on this directory just results in an automatic ownership set by the service, so that’s not an option. - Is there another location that can achieve this? - Is there any other way to solve this? I can’t find anything online, other than the same permissions issue for .pid files in this location. Cheers, Bee

2 1

8.2.2004 Latest yum update renders machine unbootable
by Alan McRae 01 Aug '20

01 Aug '20

I am running an Intel x64 machine using UEFI to boot an SSD. Installing the latest yum update which includes grub2 and kernel 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank screen where grub should be, no error messages, just hangs. After some hours I managed to modify another bootable partition (containing older software) and boot it from there. After that, I found out it is a known problem. The main point of this message is to make people aware of the problem and suggest admins don't run 'yum update' until they understand the problem and have a fix at hand. See 'UEFI boot blank screen post update' for a solution and directions to the redhat article. Regards Alan

10 15

Re: [CentOS] OpenJDK vulnerability and best way to find status of package that remediates vulnerability for CentOS
by Boushy, Phillip 31 Jul '20

31 Jul '20

>> 2. Is there a page like Ubuntu's CVE Tracker site where it shows the >> CVE, the package name, and the status > > Red Hat (CentOS's upsream) posts advisories for these sorts of things: > > https://access.redhat.com/errata/RHSA-2020:2969 > > This is the security advisory for this package. Yeah, I found this page cause harbor even links these, I apparently left out the important piece in this question "and the status per OS" - e.g. CentOS 7 "pending", CentOS 8 "released" I'm guessing there's not a central place? >> 3. If 2 is no, How can I look up the status of a package that has >> been released by upstream on CentOS? (e.g. it's been released in >> Upstream, it's available in CentOS, it's pending backport for CentOS 7) > As I mentioned earlier, the Red Hat errata site is a good place to > look. You can search for CVEs there too. This doesn't show the more critical piece though: "What is the status of the package being released per CentOS?" Leon mentioned: > https://git.centos.org/rpms/java-11-openjdk/releases Which (assuming I'm reading this right) seems like 11.0.8 was released for CentOS 7 15 days ago...? c7 = CentOS 7 But 11.0.8 isn't in the YUM repo, so that doesn't seem accurate. I'm trying to find out "Ok, it's been released for CentOS 8, what's the status of CentOS 7 - is it not vulnerable? Is it deferred? Is it pending?" Essentially I want to find out how you know that "No, but it's in the process of being built and distributed." - cause I can't tell that based on any info I've found so far.

1 0

OpenJDK vulnerability and best way to find status of package that remediates vulnerability for CentOS
by Boushy, Phillip 31 Jul '20

31 Jul '20

I have a docker image based off centos:7 with java-11-openjdk-devel. It appears that the current java-11-openjdk-devel available in the CentOS 7 Yum repo is 1:11.0.7.10-4.el7_8 11.0.7 is reported to have some high vulnerabilities RHSA-2020:2969 that are fixed in 11.0.8, but 11.0.8 is not available for CentOS 7. 1. Is there a 11.0.8 update for java-11-openjdk-devel available for CentOS 7? 2. Is there a page like Ubuntu's CVE Tracker site where it shows the CVE, the package name, and the status (e.g. https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-14578.html) 3. If 2 is no, How can I look up the status of a package that has been released by upstream on CentOS? (e.g. it's been released in Upstream, it's available in CentOS, it's pending backport for CentOS 7)

3 2

systemd syslog.target
by ctcard 31 Jul '20

31 Jul '20

I've noticed that there are several systemd unit files in CentOS 7 and 8 with the optionAfter=syslog.targetin the [Unit] section, but since systemd version 198 syslog.target has not existed.I deduce from this that "After=syslog.target" is ignored by systemd and can therefore be removed. Is this correct? I am writing some systemd unit files for our own services which previously used init.d scripts, so I want to ensure I'm not causing problems by omitting "After=syslog.target"ChrisSent from Samsung Mobile on O2

2 1

UEFI boot blank screen post update
by Anshu Prateek 31 Jul '20

31 Jul '20

Hi folks, I am able to install workstation successfully on a dedicated SSD w/ GPT partition w/ UEFI boot using the latest `CentOS-8.2.2004-x86_64-dvd1.iso` from a bootable pen drive. The motherboard is ASRock x570 Gaming 4 ( https://www.asrock.com/mb/AMD/X570%20phantom%20Gaming%204/index.asp) w/ Ryzen 3600, 16G RAM, 1TB SSD in question. However, after login, when I do a DNF update (which is updating the kernel presently) and then do a reboot, I don't see the grub2 screen anymore. I end up on a blank screen. Tried fixing grub2 via recovery method, no luck. Tried this couple of times, i.e, fresh install then dnf update, always ended up with the same result. In my latest reinstall, I did not format the boot and EFI partition, and after it came up post the reinstall, I could see the upgraded kernel entry from the last install in the grub menu. Thoughts on what could be causing this and how could I fix it? -- [image: --] Anshu Prateek [image: http://]about.me/anshuprateek <http://about.me/anshuprateek>

3 3

Boot Failed After 4.18.0-193.14.2.el8_2.x86_64
by Mark LaPierre 31 Jul '20

31 Jul '20

Hey All, My CentOS 8 system will not boot into the new kernel that was part of the update this evening. How do I boot the previous kernel? I can't select it on the boot menu. The only choice I can select, other than the new kernel that dies with a kernel panic, is the rescue kernel. If I try to edit the boot command every time I touch the cursor key the cursor jumps 15 characters. What now brown cow? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

1 0

Centos 8: removing font rpms leaves directory and .uuid file behind
by Frank Cox 31 Jul '20

31 Jul '20

remove an unneeded font that was installed during the initial setup: dnf remove thai-scalable ls -a /usr/share/fonts/thai-scalable Not only did the directory survive the removal, but we still have a hidden file named .uuid in the directory (which is probably why it didn't get removed). The directory and .uuid file is an orphan though, since rpm --whatprovides tells me that no rpm owns it. Again, not surprising since we removed the rpm. This happens when removing any of the default fonts like smc, any of the sil-* fonts and so forth. They all leave their directory under /usr/share/fonts and a .uuid file behind. -- Can we uninstall 2020 and install it again? This one has a virus. MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

CentOS-announce Digest, Vol 185, Issue 4
by centos-announce-request＠centos.org 30 Jul '20

30 Jul '20

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. CentOS Linux, CentOS Stream and the Boot Hole vulnerability (Brian Stinson) 2. [Correction/Additions] CentOS Linux, CentOS Stream and the Boot Hole vulnerability (Brian Stinson) 3. CESA-2020:3220 Important CentOS 7 kernel Security Update (Johnny Hughes) 4. CESA-2020:3217 Moderate CentOS 7 shim Security Update (Johnny Hughes) 5. CESA-2018:3140 Moderate CentOS 7 fwupdate Security Update (Johnny Hughes) 6. CESA-2020:3217 Moderate CentOS 7 shim-signed Security Update (Johnny Hughes) 7. CESA-2020:3217 Moderate CentOS 7 grub2 Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jul 2020 12:38:47 -0500 From: Brian Stinson <bstinson(a)centosproject.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CentOS Linux, CentOS Stream and the Boot Hole vulnerability Message-ID: <0f0d3ad8-7160-73b7-82d2-6d8ff51ef5f1(a)centosproject.org> Content-Type: text/plain; charset=utf-8 We are aware of the Boot Hole vulnerability in grub2 (CVE-2020-1073) and are working on releasing new packages for CentOS Linux 7, CentOS Linux 8 and CentOS Stream in response. These should make it out to a mirror near you shortly. /!\ Secureboot Systems - Please do a full update /!\ CentOS Linux 8 and CentOS Stream systems with secureboot enabled MUST update the kernel, grub2, and shim packages together. As part of this CVE, we have re-issued the kernel and shim signing certificate authorities, and previously released EL8 kernels cannot boot in secureboot mode with the newer shim/grub2. The following packages boot together in secureboot mode on CentOS Stream: * kernel-4.18.0-227.el8 / kernel-rt-4.18.0-227.rt7.39.el8 * grub2-2.02-87.el8_2 * shim-x64-15-13.el8 The following packages boot together in secureboot mode on CentOS Linux 8: * kernel-4.18.0-193.14.2.el8_2 * grub2-2.02-87.el8_2 * shim-x64-15-13.el8 For systems with CentOS Linux 7 or with secureboot disabled, we strongly recommend doing a full `dnf/yum update` to pick up all of the latest patches at the same time. On behalf of the CentOS Team, -- Brian Stinson ------------------------------ Message: 2 Date: Wed, 29 Jul 2020 13:46:26 -0500 From: Brian Stinson <bstinson(a)centosproject.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] [Correction/Additions] CentOS Linux, CentOS Stream and the Boot Hole vulnerability Message-ID: <d82db84a-7564-48bb-ef18-e6dd0a2f5036(a)centosproject.org> Content-Type: text/plain; charset=utf-8 On 7/29/20 12:38 PM, Brian Stinson wrote: > We are aware of the Boot Hole vulnerability in grub2 (CVE-2020-1073) and > are working on releasing new packages for CentOS Linux 7, CentOS Linux 8 > and CentOS Stream in response. These should make it out to a mirror near > you shortly. > > > /!\ Secureboot Systems - Please do a full update /!\ > > > CentOS Linux 8 and CentOS Stream systems with secureboot enabled MUST > update the kernel, grub2, and shim packages together. As part of this > CVE, we have re-issued the kernel and shim signing certificate > authorities, and previously released EL8 kernels cannot boot in > secureboot mode with the newer shim/grub2. > > > The following packages boot together in secureboot mode on CentOS Stream: > > * > > kernel-4.18.0-227.el8 / kernel-rt-4.18.0-227.rt7.39.el8 > > * > > grub2-2.02-87.el8_2 > > * > > shim-x64-15-13.el8 > > > The following packages boot together in secureboot mode on CentOS Linux 8: > > * > > kernel-4.18.0-193.14.2.el8_2 > > * > > grub2-2.02-87.el8_2 > > * > > shim-x64-15-13.el8 > > > For systems with CentOS Linux 7 or with secureboot disabled, we strongly > recommend doing a full `dnf/yum update` to pick up all of the latest > patches at the same time. > > On behalf of the CentOS Team, > > -- > > Brian Stinson > > > _______________________________________________ > CentOS-announce mailing list > CentOS-announce(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-announce This is a minor correction to the CVE number referenced in this earlier post. CVE-2020-10713 is the correct assignment. This is a link to the research article: https://eclypsium.com/2020/07/29/theres-a-hole-in-the-boot/ And a link to the post on OSS Security with details about related CVEs: https://www.openwall.com/lists/oss-security/2020/07/29/3 ? ------------------------------ Message: 3 Date: Thu, 30 Jul 2020 00:08:16 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3220 Important CentOS 7 kernel Security Update Message-ID: <20200730000816.GA18261(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3220 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:3220 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 902acadffe6f22819077496921383eaf7b2e83dc506a6ef6024c662bf7aa219b bpftool-3.10.0-1127.18.2.el7.x86_64.rpm 28bd92ee760fa1d9d6665ee33382089eab61f13e44ea46cc77bc7bd456cc78d1 kernel-3.10.0-1127.18.2.el7.x86_64.rpm 92f9b61e88437523d873b8dc22e8a29a44e0a487b0dc5a343ed81fe35428d7c4 kernel-abi-whitelists-3.10.0-1127.18.2.el7.noarch.rpm 5f0282fc7886ba082a43a0259bd3a6038dd3aca4574bbbceef90a1aba88d9a84 kernel-debug-3.10.0-1127.18.2.el7.x86_64.rpm b39c5e6e7b1bb5fb503352e67d0cbf0f20e4040f50ea8a24450cda3d0ce316ef kernel-debug-devel-3.10.0-1127.18.2.el7.x86_64.rpm ee25595e47130f137034ab8c665d8509448f1dbba65d4bf4e7fc5292e9d2b7a5 kernel-devel-3.10.0-1127.18.2.el7.x86_64.rpm 93dbc66703ceae3244ee11c60d8af22cd10ebd7b182dea59353916941389f0df kernel-doc-3.10.0-1127.18.2.el7.noarch.rpm 686c91ea38d4d22461bb9db234d6204208818a3b9c36e36e33ffe85adf43918b kernel-headers-3.10.0-1127.18.2.el7.x86_64.rpm b5780110e4033f75514552d8118119ce545cb00b0f30aeb883d738cb2eb6eaa8 kernel-tools-3.10.0-1127.18.2.el7.x86_64.rpm cbcedbc44f834457956181f8a5f5a20a39bdddb10c7d3dd6a324beb388c71321 kernel-tools-libs-3.10.0-1127.18.2.el7.x86_64.rpm aaee5ada299aea7c953b48a29d74fb7f2c2e5e23bab0c5cfb2c409c32e16fadb kernel-tools-libs-devel-3.10.0-1127.18.2.el7.x86_64.rpm 139a42a53f1b974880e3513eb48d80a63e6071aa2a50370c7e68e9ac2ba52213 perf-3.10.0-1127.18.2.el7.x86_64.rpm 619c92886d32633e098d4e5ef558c46e6452eccdd365a8be75e5d89bafae27a7 python-perf-3.10.0-1127.18.2.el7.x86_64.rpm Source: 6ef0b9b15b602fbf9573a22158fad1537397dc6cfb6ab507ddc31a65335e4837 kernel-3.10.0-1127.18.2.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Thu, 30 Jul 2020 00:08:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3217 Moderate CentOS 7 shim Security Update Message-ID: <20200730000850.GA18384(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3217 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:3217 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 920e0075aa2fd067ef46bdaeac583b32d8d9871c01db67f1e2ec4b107926df04 shim-unsigned-ia32-15-7.el7_9.x86_64.rpm cd6842c60c2a012c8d8250c46cfd24c3381b392d5f5556a1755829311e74c732 shim-unsigned-x64-15-7.el7_9.x86_64.rpm Source: 249512caa1fc6e5956cded0c0a6fdb7e999c97b86dc6c249773dff614d4f746f shim-15-7.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Thu, 30 Jul 2020 00:09:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:3140 Moderate CentOS 7 fwupdate Security Update Message-ID: <20200730000907.GA18499(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:3140 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2018:3140 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c05389bec1bdbeb04d070fccf0f5bdf8881ad807d6f837f35cbbf68b1848cbb0 fwupdate-12-6.el7.centos.x86_64.rpm 6bf6d673a0b0b1174165533f726dc07d6b804b59a5500958689c5df99572e6ab fwupdate-devel-12-6.el7.centos.x86_64.rpm 52e24c7f1318f068f2611bba1e5f083feb60de6ef7554da28e48ad9120dd49c5 fwupdate-efi-12-6.el7.centos.x86_64.rpm bd06f43c52936c555729b0b1262c077b94fac2b989c4b3a6d218cc1c5ee50ff5 fwupdate-libs-12-6.el7.centos.x86_64.rpm Source: 1e4802e55272b2fc79d6b09f81ed5e325f600b15c3a91774055ac56989d0bf13 fwupdate-12-6.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Thu, 30 Jul 2020 00:09:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3217 Moderate CentOS 7 shim-signed Security Update Message-ID: <20200730000923.GA18599(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3217 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:3217 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 46d78ecee751d736f35445677f13e9513bcc73e01c21e8b46e19f6d5f9fdb44f mokutil-15-7.el7_9.x86_64.rpm 44a808272f4977f5c81fcb76b18199b90b5bf4b058f2f418014b8c2f24cb5a83 shim-ia32-15-7.el7_9.x86_64.rpm bc8bf6b6c2068d3d9477e9a5596ff038ea1dc233cc3609e56571d4982e7d0879 shim-x64-15-7.el7_9.x86_64.rpm Source: df836efee4f974f207aa81aa396cda6f72daa95380b4d1f9f6659200c828bf5d shim-signed-15-7.el7_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Thu, 30 Jul 2020 00:10:07 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2020:3217 Moderate CentOS 7 grub2 Security Update Message-ID: <20200730001007.GA18819(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2020:3217 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:3217 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 10f5fc45885e9744b499a8d1830336902b9f4f4dd51ce0575fd5bb18e9047631 grub2-2.02-0.86.el7.centos.x86_64.rpm 9e82c47470c39b8c9c33717412a158f6bc1812fb771990b5dd8496ee1c94b22b grub2-common-2.02-0.86.el7.centos.noarch.rpm c5df733e242a01dac2a0caacf4436ed89ad75524499d26b675cacdae40d52fbd grub2-efi-ia32-2.02-0.86.el7.centos.x86_64.rpm c80037611cffa96c137a0fb8d69fc24c0bb09bdc375e050eb5e31462afa150d2 grub2-efi-ia32-cdboot-2.02-0.86.el7.centos.x86_64.rpm 5136ed781f53e9330c45a1b087415e526db7c34786a3820b5ed6f94a984d602a grub2-efi-ia32-modules-2.02-0.86.el7.centos.noarch.rpm 1ec6e0366621da95205d57d23923c753ba502e8edfcf93cf6a01fe77f5f5af11 grub2-efi-x64-2.02-0.86.el7.centos.x86_64.rpm 1383ce6a6084b7f57053146679c211ea1b26f8301c44a7cbfdba8ea0d78de9f4 grub2-efi-x64-cdboot-2.02-0.86.el7.centos.x86_64.rpm 7b0f54f0c04a7d856a2211e2620f528097ee3c2d2a8d04adfc7d8631b97922df grub2-efi-x64-modules-2.02-0.86.el7.centos.noarch.rpm 8f89bbf59c8970c2521bb90058f66a5fa744b00c80e411faed66a164b4c02a7e grub2-i386-modules-2.02-0.86.el7.centos.noarch.rpm 888f2ae0c70346cd235901ec3f4a8b1aa5a34c6d665b0868fa1ec25291497932 grub2-pc-2.02-0.86.el7.centos.x86_64.rpm 53aac7825660300e05a2bdb6b4d79221788bc50c554f9f1dbd9bf0706fe3db14 grub2-pc-modules-2.02-0.86.el7.centos.noarch.rpm cb5848b77ed2a5f81e8b27a7138917442d54656a3438a92cfa15d4f724549ed4 grub2-tools-2.02-0.86.el7.centos.x86_64.rpm 4441a4895a43bec4adc5bbc9acc8a888c1b0f5db6022f6b18a9099139ee26caa grub2-tools-extra-2.02-0.86.el7.centos.x86_64.rpm c2caccf01f5c959fa74e82800f6e5dc2aaaa59904c453388ad0debae8bbbe51b grub2-tools-minimal-2.02-0.86.el7.centos.x86_64.rpm Source: e5f72d4c65882ee14644d92931f6177a194863702367f1f62228b38547d5dab4 grub2-2.02-0.86.el7.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 185, Issue 4 ***********************************************

1 0

mysql-connector-odbc i686 package
by sthustfo 30 Jul '20

30 Jul '20

Hi all, I am looking for a i686 package (32 bit) for mysql-connector-odbc. However, I could locate only the x86-64 version on the repositories. Not much of a DB person but trying to connect to a 64bit MySQL server on remote host. Any suggestions where I can locate the i686 package? Is there a mariadb package that I can use? Thanks.

3 2

CentOS user survey results
by Rich Bowen 29 Jul '20

29 Jul '20

Over the past 3 or 4 months, we have been running a survey about how you use CentOS. Many thanks to those who participated in this, to help us better understand how we can give you what you need. I've written up the results of the survey here - https://blog.centos.org/2020/07/centos-community-user-survey/ While some of the results were expected - most of you use CentOS in small to medium shops, running services either for work or personal use - there were some eye-opening things in this. To me personally, the volunteerism question shows that a lot of you are looking for places to get involved, and that we haven't done a great job telling you where and how. We'll be working to fix that. For those of you who missed the survey, we intend to do this again, perhaps as often as twice a year, and also provide opportunities to give more feedback beyond the simple 5-minute questionnaire. Thank you all for participating, and for being part of our community.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss