Discuss

discuss@lists.centos.org

3 participants
34733 discussions

Compatible SATA controller needed
by Pete Geenhuizen 27 Mar '22

27 Mar '22

I'm trying to install Centos 8 on an older PC but it fails because the SATA controller isn't supported. Anyone have a source for a PCI/ePCI controller card that is compatible with Centos 8? Thanks Pete -- Unencumbered by the thought process. -- Click and Clack the Tappet brothers

4 5

kernel message format - how ?
by lejeczek 24 Mar '22

24 Mar '22

Hi guys. When kernel - I think - broadcasts messages, spits to console, I wonder how one controls that message format. I specifically think of what 'dmesg' offers for time parts of the message, eg. '--reltime' - so the same only persistent/default behavior. many thanks, L.

1 0

Cron and GNU parallel
by Joseph L. Casale 21 Mar '22

21 Mar '22

I am using parallel-20190922-1 from epel and when I run a job in cron such as /usr/bin/parallel /usr/bin/bash ::: a.sh b.sh c.sh I don't receive any mail regardless of all three scripts generating output. All other jobs in cron generate mail if they write to stdout or stderr. When the above is run at a terminal, I get the output from all three jobs grouped in the order they complete. I can't find any documentation for parallel that states the behavior when not running with a terminal. Anyone have any ideas? Thanks, jlc

1 0

Re: [CentOS] Updating a package to one from a different repository
by Fred 21 Mar '22

21 Mar '22

Delete the package then reinstall from EPEL??? On Mon, Mar 21, 2022, 10:33 Kenneth Porter <shiva(a)sewingwitch.com> wrote: > At some point I updated fail2ban from a copr repo to get the latest > release. That repo no longer exists but a newer version is available in > EPEL. Is there a direct way to get yum to update using the different repo? > Or do I need to save my config and DB, erase the old version, and install > the new one from EPEL? > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos >

1 0

TCP Sequence Number Approximation Based Denial of Service on CentOS Linux release 7.9.2009 (Core)
by Kaushal Shriyan 18 Mar '22

18 Mar '22

Hi, I have 3.10.0-1160.59.1.el7.x86_64 on CentOS Linux release 7.9.2009 (Core) running Nagios Monitoring system. We have run an external vulnerability scan today on this server. The vulnerability reports say the below details. I am not sure if I completely understand the below issue. CVSS base score:- 5.0 CVE-2004-0230 Severity : Medium TCP Sequence Number Approximation Based Denial of Service TCP provides stateful communications between hosts on a network. TCP sessions are established by a three-way handshake and use random 32-bit sequence and acknowledgement numbers to ensure the validity of traffic. A vulnerability was reported that may permit TCP sequence numbers to be more easily approximated by remote attackers. This issue affects products released by multiple vendors. The cause of the vulnerability is that affected implementations will accept TCP sequence numbers within a certain range, known as the acknowledgement range, of the expected sequence number for a packet in the session. This is determined by the TCP window size, which is negotiated during the three-way handshake for the session. Larger TCP window sizes may be set to allow for more throughput, but the larger the TCP window size, the more probable it is to guess a TCP sequence number that falls within an acceptable range. It was initially thought that guessing an acceptable sequence number was relatively difficult for most implementations given random distribution, making this type of attack impractical. However, some implementations may make it easier to successfully approximate an acceptable TCP sequence number, making these attacks possible with a number of protocols and implementations. This is further compounded by the fact that some implementations may support the use of the TCP Window Scale Option, as described in RFC 1323, to extend the TCP window size to a maximum value of 1 billion. This vulnerability will permit a remote attacker to inject a SYN or RST packet into the session, causing it to be reset and effectively allowing for denial of service attacks. An attacker would exploit this issue by sending a packet to a receiving implementation with an approximated sequence number and a forged source IP address and TCP port. There are a few factors that may present viable target implementations, such as those which depend on long-lived TCP connections, those that have known or easily guessed IP address endpoints and those implementations with easily guessed TCP source ports. It has been noted that Border Gateway Protocol (BGP) is reported to be particularly vulnerable to this type of attack, due to the use of long-lived TCP sessions and the possibility that some implementations may use the TCP Window Scale Option. As a result, this issue is likely to affect a number of routing platforms. Another factor to consider is the relative difficulty of injecting packets into TCP sessions, as a number of receiving implementations will reassemble packets in order, dropping any duplicates. This may make some implementations more resistant to attacks than others. It should be noted that while a number of vendors have confirmed this issue in various products, investigations are ongoing and it is likely that many other vendors and products will turn out to be vulnerable as the issue is investigated further. Solution Please first check the results section below for the port number on which this vulnerability was detected. If that port number is known to be used for port-forwarding, then it is the backend host that is really vulnerable. Various implementations and products including Check Point, Cisco, Cray Inc, Hitachi, Internet Initiative Japan, Inc (IIJ), Juniper Networks, NEC, Polycom, and Yamaha are currently undergoing review. Contact the vendors to obtain more information about affected products and fixes. " http://packetstormsecurity.org/0404-advisories/246929.html" NISCC Advisory 236929 - Vulnerability Issues in TCP details the vendor patch status as of the time of the advisory, and identifies resolutions and workarounds. Refer to "http://www.kb.cert.org/vuls/id/415294" US-CERT Vulnerability Note VU#415294 and "http://osvdb.org/4030" OSVDB Article 4030 to obtain a list of vendors affected by this issue and a note on resolutions (if any) provided by the vendor. For Microsoft: Refer to " https://docs.microsoft.com/en-us/security-updates/securitybulletins/2005/ms…" MS05-019 and " https://docs.microsoft.com/en-us/security-updates/securitybulletins/2006/ms…" MS06-064 for further details. For SGI IRIX: Refer to " ftp://patches.sgi.com/support/free/security/advisories/20040905-01-P.asc" SGI Security Advisory 20040905-01-P For SCO UnixWare 7.1.3 and 7.1.1: Refer to " ftp://ftp.sco.com/pub/updates/UnixWare/SCOSA-2005.14/SCOSA-2005.14.txt" SCO Security Advisory SCOSA-2005.14 For Solaris (Sun Microsystems): The vendor has acknowledged the vulnerability; however a patch is not available. Refer to "http://www.kb.cert.org/vuls/id/JARL-5YGQAJ" Sun Microsystems, Inc. Information for VU#415294 to obtain additional details. Also, refer to "http://www.us-cert.gov/cas/techalerts/TA04-111A.html" TA04-111A for detailed mitigating strategies against these attacks. For NetBSD: Refer to " ftp://ftp.netbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2004-006.txt.a…" NetBSD-SA2004-006 For Cisco: Refer to " http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml" cisco-sa-20040420-tcp-ios.shtml . For Red Hat Linux: There is no fix available. Workaround: The following BGP-specific workaround information has been provided. For BGP implementations that support it, the TCP MD5 Signature Option should be enabled. Passwords that the MD5 checksum is applied to should be set to strong values and changed on a regular basis. Secure BGP configuration instructions have been provided for Cisco and Juniper at these locations: " http://www.cymru.com/Documents/secure-bgp-template.html" Secure Cisco IOS BGP Template " http://www.cymru.com/gillsr/documents/junos-bgp-template.pdf" JUNOS Secure BGP Template Additional Information Tested on port 80 with an injected SYN/RST offset by 16 bytes. Please guide/suggest. Thanks in advance. Best Regards, Kaushal

2 2

domain configuration does not support video model 'qxl
by Sudheer S 13 Mar '22

13 Mar '22

Hello, Using libvirt and qemu, I am trying to install CentOS Stream 8 guest on CentOS Stream 9. I get this error: Unable to complete install: 'unsupported configuration: domain configuration does not support video model 'qxl'' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createvm.py", line 2001, in _do_async_install installer.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 701, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 649, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib/python3/dist-packages/libvirt.py", line 4389, in createXML raise libvirtError('virDomainCreateXML() failed') libvirt.libvirtError: unsupported configuration: domain configuration does not support video model 'qxl' Am I missing any package? Or having a misconfiguration? - Sudheer

1 0

CentOS 9 and gtk-spice
by Joshua Kramer 11 Mar '22

11 Mar '22

Hello- Before I open a bug report on this, I wanted to ask if there is a specific reason that spice-gtk is not in the OS repositories of EL9? It looks like I have to install the ovirt repositories before I get access to spice-gtk and its dependencies. Thanks! -JK

2 1

Autoreply: "CentOS Digest, Vol 206, Issue 9"
by mak＠jump.com.hk 11 Mar '22

11 Mar '22

Thank you for your email. Vincent Mak is no longer working at Jump. Please do not hesitate to contact samantha(a)jump.com.hk or gary(a)jump.com.hk with any enquiry you have.

2 1

session-*.scope: Succeeded. messages in log
by Emmett Culley 10 Mar '22

10 Mar '22

I am seeing a "Mar 10 07:20:01 avm4 systemd[1]: session-66528.scope: Succeeded." message in the log that happens once each minute, of course with different session number values". What is causing this and how can I stop them. Linux avm4.mydomain.com 4.18.0-358.el8.x86_64 #1 SMP Mon Jan 10 13:11:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux CentOS Stream 8 I could cause logwatch to ignore them, but I would like to understand why three of my server are producing these unnecessary log entries. Emmett

1 0

Process owned by a user running after logout
by Hooton, Gerard 10 Mar '22

10 Mar '22

After logout, process owned by the logged out user keep running. If a user connects using ssh and then, without starting any programs, signs out the following processes remain running 4 S Tom 1808940 1 0 80 0 - 22440 do_epo 11:08 ? 00:00:00 /usr/lib/systemd/systemd --user 5 S Tom 1808943 1808940 0 80 0 - 75441 - 11:08 ? 00:00:00 (sd-pam) 0 S Tom 1809033 1 0 80 0 - 108596 x64_sy 11:08 ? 00:00:00 gio monitor -f /run/systemd/sessions/13496 0 S Tom 1809062 1808940 0 80 0 - 16095 do_epo 11:08 ? 00:00:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only This only applies to users who use ssh, when using the system console [Gnome 3 desktop] all processes own by a user stop when that user signs out. I have a number of users who use the computer for remote access and the number of these running process grows over a few weeks. I am using CentOS Stream 8. Kernel : 4.18.0-365.el8.x86_64 #1 SMP Thu Feb 10 16:11:23 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss