Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Python hashlib and ripemd160
by Alice Wonder 03 Feb '16

03 Feb '16

Hi - I think the patent monster has struck again. rmd = hashlib.new('ripemd160',binascii.unhexlify(someString)).hexdigest() That fails - ValueError: unsupported hash type From some googling, it appears that the supported hash types are from OpenSSL and that means the OpenSSL in CentOS doesn't support ripemd160. I've worked around other stuff missing from CentOS OpenSSL by building LibreSSL and linking against that but python is central to the operation of CentOS and I do not want to mess with replacing the CentOS packaging of python. Is there an alternate way to get a ripemd160 hash in python on CentOS ?

2 3

In A UEFI World, "rm -rf /" Can Brick Your System
by m.roth＠5-cent.us 02 Feb '16

02 Feb '16

Excerpt: Running rm -rf / on any UEFI Linux distribution can potentially perma-brick your system. As a public service announcement, recursively removing all of your files from / is no longer recommended. On UEFI distributions by default where EFI variables are accessible via /sys, this can now mean trashing your UEFI implementation. There is this systemd bug report requesting that UEFI variables be mounted as read-only by default. Lennart Poettering had initially responded and simply said, "Well, there are tools that actually want to write it. We also expose /dev/sda accessible for root, even though it can be used to hose your system. The ability to hose a system is certainly reason enought to make sure it's well protected and only writable to root. But beyond that: root can do anything really." He then closed the ticket. --- end excerpt --- <http://www.phoronix.com/scan.php?page=news_item&px=UEFI-rm-root-directory> "And they closed the ticket"? That tuxedo on the cockroach is so elegent! Ok, *now* tell me why we shouldn't hate systemd? mark

10 22

Re: [CentOS] NICs order
by m.roth＠5-cent.us 02 Feb '16

02 Feb '16

Gordon Messmer wrote: > On 02/01/2016 07:00 AM, Leroy Tennison wrote: >> The issue here may be systemd > ... >> Web documentation at freedesktop.org says net.ifnames needs to be set to zero, I found just the opposite but if it doesn't work for you try both before giving up. > > Just to clarify: net.ifnames=0 disables the systemd/udev interface renaming feature. biosdevname=0 disables the biosdevname interface renaming feature, which is completely separate. If you want the traditional, non-deterministic Linux interface naming, you must specify both. You call it "deterministic". I will note that it is, in fact, straight from Sun - 20 years ago, that was the naming on the Sparc Server that I first picked up sysadmin work. Which was fine... FOR SUN HARDWARE. For admins and users, it's *really* NOT a great idea, given that the system could have a m/b from any OEM, and even trying to set up a std. kickstart is a pain with that, much less anything more arcane. Why ethx, with the option of adding the firmware MAC address, is such a bad idea, I have no clue. > > Also, if you add rules to /etc/udev/rules.d, you should rebuild your initrd. ?!?!?!?! THAT I had never considered, nor done, and I'm sure that in CentOS 6, I've changed things there, and just rebooted. Oh, great, I'm getting flashes of WinDoze. Thanks for that info, though. I need to remember that. mark

3 2

Folding At Home
by Mark LaPierre 02 Feb '16

02 Feb '16

Hey Y'all, I have the Stanford University Folding At Home project running on three of my machines. I had them all set up so that I could control them all from my main machine, 192.168.15.101, but some time ago something changed so that I can no longer connect to the FAH clients on the other two machines. I figured it wasn't really important so I would look into it later. Well time has passed and my Christmas break is almost passed too to I guess this is the time to figure it out. I can still SSH onto both machines. I can ping both machines. When I open the FAH Control on my machine connection to clients running on 192.168.15.105 and 192.168.15.107 fails. I'm assuming that there would be an entry in a log on those two machines detailing the failed connection attempt. What log file should I be looking at? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 5

NICs order
by Daniel Ruiz Molina 01 Feb '16

01 Feb '16

Hi, After installing CentOS 7 in a server with 2 NICs, system detects eth0 and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as eth1. I have forced HWADDR attribute in /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but after rebooting, order is the same... How can I solve it? Thanks.

2 1

CentOS 7 and network printers: FYI
by m.roth＠5-cent.us 01 Feb '16

01 Feb '16

I got an email from a user that I'd just handed a new CentOS 7 workstation to, wondering where all the printers were. It took some investigation to find /etc/cups/cups-browsed.conf, and see, in it, at the very bottom of the file: # NOTE: This file is not part of CUPS. You need to start & enable cups-browsed service. Which appears to be brand new with 7, and I have not seen any mention of it. Enabled and started, and the network printers are visible on the cups localhost web page->printers. mark

2 3

Re: [CentOS] NICs order
by Ricardo J. Barberis 01 Feb '16

01 Feb '16

El Lunes 01/02/2016, Daniel Ruiz Molina escribió: > Hi, > > After installing CentOS 7 in a server with 2 NICs, system detects eth0 > and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as > eth1. I have forced HWADDR attribute in > /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but after rebooting, > order is the same... > > How can I solve it? > > Thanks. You could put the MAC addresses in /etc/udev/rules.d/60-net.rules, e.g.: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" But that never worked reliably for me, no matter what I tried. In the end I had to use different names instead of eth0 and eth1, like: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="nic0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="nic1" And also rename /etc/sysconfig/network-scripts/ifcfg-ethX to ifcfg-nicX and modify them accordingly. HTH, -- Ricardo J. Barberis Usuario Linux Nº 250625: http://counter.li.org/ Usuario LFS Nº 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com

4 5

LUSTRE Install Guide
by Ben Archuleta 01 Feb '16

01 Feb '16

Hi All, I am in the process of trying to install Lustre on CentOS 7 and I was wondering if anyone could point me to any good documentation. I found https://wiki.hpdd.intel.com/pages/viewpage.action?pageId=8126821 but this really doesn’t help. I am trying to install version 2.7.1. Regards, Ben

1 0

CentOS-announce Digest, Vol 132, Issue 1
by centos-announce-request＠centos.org 01 Feb '16

01 Feb '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2016:0082 Important CentOS 6 qemu-kvm Security Update (Johnny Hughes) 2. CESA-2016:0083 Important CentOS 7 qemu-kvm Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 1 Feb 2016 10:06:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0082 Important CentOS 6 qemu-kvm Security Update Message-ID: <20160201100638.GA48502(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0082 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0082.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a1f7d969256f40bceda80f8b528483daa4c46ffd1aa161d688b5213e82534728 qemu-guest-agent-0.12.1.2-2.479.el6_7.4.i686.rpm x86_64: 1e0bbdb48082401bf939242e8365ed87d978d810461fd5f5f8a07fb27cc68908 qemu-guest-agent-0.12.1.2-2.479.el6_7.4.x86_64.rpm 5659db7806844d947e48a239a10e171bfe614f6ec55e41dc4456bbf681ed93a3 qemu-img-0.12.1.2-2.479.el6_7.4.x86_64.rpm 02c1fb0cf175af0ef966c9bdba504598dcc296acd84943e84c6950b660119858 qemu-kvm-0.12.1.2-2.479.el6_7.4.x86_64.rpm 3a706f6a6c9dd68d53403d9bf28e0460d166ccb14b5e236cb3a570fed8981945 qemu-kvm-tools-0.12.1.2-2.479.el6_7.4.x86_64.rpm Source: 15dd53d31a04e2fbff8ed17825a00a8db774e4b765d21cb8e425dfa7f420e1ed qemu-kvm-0.12.1.2-2.479.el6_7.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 1 Feb 2016 10:07:16 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0083 Important CentOS 7 qemu-kvm Security Update Message-ID: <20160201100716.GA48601(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0083 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0083.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4b32c17ff1beedcb1f6061718d320fabefdfbc097c158d4b1dae708fd42fdcea libcacard-1.5.3-105.el7_2.3.i686.rpm e67108224ae1a48a7e3fe50c844eb72cbb1f2577e14a8b4125223a7733fae0d1 libcacard-1.5.3-105.el7_2.3.x86_64.rpm d87a6e35540834492782b7b8912a4585aa1aed9bc8e8be2411869ac629992b2e libcacard-devel-1.5.3-105.el7_2.3.i686.rpm de52616bc23aa304b8e5754dbd01ea01885be400a7c1971f175a71a4c319c8e2 libcacard-devel-1.5.3-105.el7_2.3.x86_64.rpm 9d5121b15522703d568ef24aa6445d70aa25cce27bff49c94ebebe0d484b461e libcacard-tools-1.5.3-105.el7_2.3.x86_64.rpm f6b81452aa1929447d9bc9b1801276e11c20f356a5fffff4817994da23073ce6 qemu-img-1.5.3-105.el7_2.3.x86_64.rpm 21eaddeefef89775defa32724cb48d501184212b8d05d128a3c83911c1fc2099 qemu-kvm-1.5.3-105.el7_2.3.x86_64.rpm 89bb7aa5f7b8d0ed361b7b9090f7a3a508213829237da9e39b3a1d7a674b4fcc qemu-kvm-common-1.5.3-105.el7_2.3.x86_64.rpm eb6f93064a64451b608d32f292e94fad18c53a16790507fe2d97bf1d0b78e006 qemu-kvm-tools-1.5.3-105.el7_2.3.x86_64.rpm Source: f963af3a6d471d8b82c5afef2fc76ef4f1dd3985e10ceafe2b04e04ef1571bf4 qemu-kvm-1.5.3-105.el7_2.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 132, Issue 1 ***********************************************

1 0

C7 and hplip
by Alessandro Baggi 31 Jan '16

31 Jan '16

Hi list, I've a printer model HP ENVY 5530 (AIO) configured in wifi. I've configured this printer on my C7(1511) workstation using hplip and cups. Printer is installed e configured. After installation I try to send a test print page and it is printed. After reboot, I try to print other doc, and I got it printed only on grey-scale and if I try to send another test print page from hplip or cups I obtain a gray-scale print and half page with wrong size (like if the "image" is printed on A3). If I remove printer and re-add it, the test page output mode is color but after a reboot it come back to gray-scale mode but in configuration is selected color. hplip version is 3.13.7. Can someone point me in the right direction? thanks in advance.

1 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss