- Discuss - lists.centos.org

How to have more than on SELinux context on a directory
by Bernard Fay 08 Jul '16

08 Jul '16

Hello, I need to have the tftpdir_rw_t and samba_share_t SELinux context on the same directory. How can we do this? Is it feasible to have more than one SELinux context? Thanks, Bernard

6 11

Help sought for email problem
by Timothy Murphy 07 Jul '16

07 Jul '16

My home server is running CentOS-7.1 I'm running postfix and dovecot on it. I collect email from a few sources with fetchmail and move it to ~/Maildir/cur/ with procmail. Or at least, I did do this. For some reason procmail has stopped doing its job, and the email that I collect is finishing in /var/spool/mail/tim/ I can't work out what has caused this, or what the cure is. I haven't changed postfix or dovecot config files, or .procmailrc. I did stop and re-start postfix and dovecot on the server, which I haven't done for some time, so it is possible some earlier upgrade has come into play. Any advice or elucidation gratefully received. -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

2 1

Re: [CentOS] CentOS 6, iscsi,
by Denniston, Todd A CIV NAVSURFWARCENDIV Crane 07 Jul '16

07 Jul '16

Thu Jul 7 14:47:23 UTC 2016, m.roth at 5-cent.us wrote: > Hi, folks, > > I installed the iscsi packages, and I *thought* that the first thing to > do was configure /etc/tgt/target.conf. Am I wrong? Did I have to > configure iSNS on the RAID appliance? One thing to make sure you have straight is Target vs. Initiator [2], for me it originally felt like the names were backwards. I would expect the physical RAID machine to be the Target. Was that your expectation too, as it is a little unclear from the para above? > > All that I find on the web, incl. upstream docs, is to install it, then > start the service. It might have helped if you had pointed at which upstream docs... some are better than others on the same subject. When I did a test of it, I found starting with the Target creation doc [1] and following with the Initiator doc[3] (each on different RH/CentOS boxes) helped me to figure it out. BTW while in [1] they use /dev/vdb it works as well with real /dev/sd* or Logical Volumes, I don't recall _trying_ with PVs. [1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht… [2] https://en.wikipedia.org/wiki/ISCSI#Initiator [3] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht… Even when this disclaimer is not here: I am not a contracting officer. I do not have authority to make or modify the terms of any contract.

2 2

CentOS 6, iscsi,
by m.roth＠5-cent.us 07 Jul '16

07 Jul '16

Hi, folks, I installed the iscsi packages, and I *thought* that the first thing to do was configure /etc/tgt/target.conf. Am I wrong? Did I have to configure iSNS on the RAID appliance? All that I find on the web, incl. upstream docs, is to install it, then start the service. What am I misunderstanding? mark, aka "Confused"

1 1

Re: [CentOS] DHCP max-lease-time maximum
by Eero Volotinen 07 Jul '16

07 Jul '16

Static MAC ip mapping on dhcp server? Eero 7.7.2016 12.38 ip. "Götz Reinicke - IT Koordinator" < goetz.reinicke(a)filmakademie.de> kirjoitti: Am 06.07.16 um 18:19 schrieb John R Pierce: > On 7/6/2016 1:27 AM, Götz Reinicke - IT Koordinator wrote: >> :) ... the long lease is for some Accesspoints which we dont like to >> configure static, just plug in and run. > > why not configure reservations for those access points? > > the downside of a really long lease time is if you have to change > something like DNS, gateway, whatever, the clients with a really long > lease will not 'see' the change until 50% of hte lease time expires as > thats the default refresh. > > Hi, what do you mean with "reservations"? the APs in question just need an IP for connecting to the managemnt server which is in the same subnet. Thanks for your feedback . Götz _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

3 2

CentOS-announce Digest, Vol 137, Issue 2
by centos-announce-request＠centos.org 07 Jul '16

07 Jul '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. Announcing Release for Gluster 3.8 on CentOS Linux 7 x86_64 (Niels de Vos) 2. Announcing Release for Gluster 3.8 on CentOS Linux 6 x86_64 (Niels de Vos) 3. CEEA-2016:1388 CentOS 5 tzdata Enhancement Update (Johnny Hughes) 4. CEEA-2016:1388 CentOS 7 tzdata Enhancement Update (Johnny Hughes) 5. CEEA-2016:1388 CentOS 6 tzdata Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 6 Jul 2016 16:03:34 +0200 From: Niels de Vos <ndevos(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing Release for Gluster 3.8 on CentOS Linux 7 x86_64 Message-ID: <20160706140334.GF15951(a)ndevos-x240.usersys.redhat.com> Content-Type: text/plain; charset="us-ascii" We are happy to announce the General Availability of Gluster 3.8 for CentOS Linux 7. Earlier versions (3.6 and 3.7) are still available and will keep receiving updates until the upstream Gluster Community marks them End-Of-Life. GlusterFS 3.8 brings many improvements and new functionalities. These are documented in the 3.8.0 release notes: https://github.com/gluster/glusterfs/blob/release-3.8/doc/release-notes/3.8… To install GlusterFS 3.8, only two commands are needed: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster content comes from the centos-release-gluster38 package delivered via CentOS Extras repos. This contains all the metadata and dependancy information, needed to install GlusterFS 3.8. Deployments that have centos-release-gluster36 or -gluster37 installed will not automatically upgrade to version 3.8. These installations will continue to stick to their current stable version with minor updates. The existing quickstart guide will still work with the new version of Gluster. In fact, we do not expect to see any issues with use-cases that work on 3.7 already. Installation and configuration is the same in the new version: https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart More details about the packages that the Gluster project provides in the Storage SIG is available in the documentation: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster The centos-release-gluster* repositories offer additional packages that enhance the usability of Gluster itself. Users can request additional tools and applications to be provided, just send us an email with your suggestions. The current list of packages that is (planned to become) available can be found here: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster/Ecosystem-pkgs These Gluster repositories and packages are provided through the Storage SIG. General information about the SIG can be read in the wiki: https://wiki.centos.org/SpecialInterestGroup/Storage We welcome all feedback, comments and contributions. You can get in touch with the CentOS Storage SIG on the centos-devel mailing list ( https://lists.centos.org ) and with the Gluster developer and user communities at https://www.gluster.org/mailman/listinfo , we are also available on irc at #gluster on irc.freenode.net, and on twitter at @gluster . Cheers, Niels de Vos Storage SIG member & Gluster maintainer

1 0

DHCP max-lease-time maximum
by Götz Reinicke - IT Koordinator 07 Jul '16

07 Jul '16

Hi, I m looking for the max value for max-lease-time. would 512640 seconds (1 year) work? Thanks . Götz

3 7

arne303 scratch in the sleep-blackboxxxx- no money
by Arne Siebert 07 Jul '16

07 Jul '16

1 0

.NET on Centos.
by Peter Q. 06 Jul '16

06 Jul '16

Hi there, I was reading about it. https://www.redhat.com/en/about/blog/net-core-now-available-and-supported-r… What will happen with Centos and .NET? In the side of security and stability.

6 7

SELinux C7 audit
by Alessandro Baggi 06 Jul '16

06 Jul '16

Hi list, I'm studying SELinux on my workstation and for this I've enforced. In a first time selinux was permissive and when switched to enforcing I had relabel some things. Due to my "nescience" about selinux and what I must configure, I'm waiting avc denied for specified services. Until today, I've configured successfully httpd, smbd. Today I've noticed that my bacula system does not work due to selinux denied because when bacula try to run pre/post job script I get access denied due to differences about context. Bacula is on bacula_t and in pre script I call commands in other context like: systemd_systemctl_exec_t ... (and other) Reading from RHEL DOC (SELinux Guide) I can accomplish to remove denied access using audit2allow and creating TE rules. I've runned: grep systemctl /var/log/audit/audit.log | audit2allow -M pol and I got 2 files pol.pp (compiled) and pol.te. pol.te reports: require { type systemd_systemctl_exec_t; type bacula_t; class file execute; } #============= bacula_t ============== allow bacula_t systemd_systemctl_exec_t:file execute; Loading this policy things "will work". Now this problem is solved by audit2allow and not by me. I don't know what is necessary to make pre/post job script to get work done. What are the meaning of rules on pol.te and why bacula can't do transiction between context? Hope in help. Thanks in advance.

2 2

OT: hardware, MegaRAID SAS 2008 (falcon)
by m.roth＠5-cent.us 05 Jul '16

05 Jul '16

I've been googling, and haven't yet found the answer: does anyone here know if a MegaRAID SAS 2008 (falcon) (rev 03) can handle drives bigger than 2TB? mark

3 5

how to set/add environment variables and make file search priority on centos
by qw 05 Jul '16

05 Jul '16

Hi, I'm using centos 6.8. In order to build gstreamer 1.8.2, I install some new packages, such as python 2.7 and yasm. And cerbero is the build system for gstreamer, and downloads some new packages from network and build them, such libtool, glib. All new packages are downloaded, built and installed in my custom directory. I want cerbero use the new packages in my custom directory. It mean that, linux will search my custom directory first, and will search others if target program or lib is not found. How to make search priority for programs, static libs, shared libs, and pkgconfig files? Thanks! Regards Andrew

2 1

A
by Duvall, Michael 05 Jul '16

05 Jul '16

A Regards, Michael Duvall Systems Analyst Concurrent Computer Corporation 2881 Gateway Drive Pompano Beach, FL 33069 c: 954-531-4538 o: 954-973-5395

2 1

how to build/install pulseaudio 6.0 on centos 6.8
by qw 05 Jul '16

05 Jul '16

Hi, Centos 6.8 comes with pulseaudio 0.9, but I want to use pulseaudio 6.0 or higher version, which is used on centso 7. How to build/install new pulseaudio on centso 6.8? Are there some dependency libs for pulseaudio? is there some rpm of pulseaudio 6.0 for centos 6.8? Thanks Regards andrew

1 0

how to use python 2.7 by default instead python 2.6 on centos 6.8
by qw 04 Jul '16

04 Jul '16

Hi, centos 6.8 comes with python 2.6. But I want to use python 2.7 to build gstreamer sdk. I have built python 2.7 and installed it into my custom directory. How to set centos to use python 2.7 by default instead of python 2.6? Thanks! Regards Andrew

5 6

netbook screen suddenly goes black
by Fred Smith 02 Jul '16

02 Jul '16

Hi all! I'm running an up to date Centos-7 on my Acer Aspire One netbook. have been for, well, ever since C7 was released. Just had an event today that also happened 2 or 3 times with earlier systems installed, but I never pursued it. What happens is that suddenly while working away on the desktop the display suddenly goes black... not black as in turned off, I can see that the backlight is still on, but no image is displayed. Nothing I can do fixes it except a reboot. I've tried CTRL-ALT-BKSP, CTRL-ALT-DEL, alt+printscreen+r+e+i+s+u+b. none of them do anything noticeable. I've been looking at system logs and don't find anything that gives me a clue what is going wrong when that happens. neither dmesg, /var/log/Xorg*, nor /var/log/messages contins much. I've tried digging thru "man journalctl" and ultimately reading thru the output of journalctl with no arguments. Can anyone of you provide further hints on what I should be looking for or at? thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. ------------------------------- Romans 5:8 (niv) ------------------------------

8 18

Securing RPC
by Leon Vergottini 01 Jul '16

01 Jul '16

Dear Community I hope you are all doing well. Recently I have been receiving several complaints from our service provider. Please see the complaint below: A public-facing device on your network, running on IP address XXX.XXX.XXX.XXX, operates a RPC port mapping service responding on UDP port 111 and participated in a large-scale attack against a customer of ours, generating responses to spoofed requests that claimed to be from the attack target. Please consider reconfiguring this server in one or more of these ways: 1. Adding a firewall rule to block all access to this host's UDP port 111 at your network edge (it would continue to be available on TCP port 111 in this case). 2. Adding firewall rules to allow connections to this service (on UDP port 111) from authorized endpoints but block connections from all other hosts. 3. Disabling the port mapping service entirely (if it is not needed). Unfortunately, I cannot disable NFS which lies at the root of this problem. In addition, I am struggling to find a proper tutorial of moving NFS from udp over to tcp. May I kindly ask you to point me in a direction or provide me with ideas on how to nail this thing in the .... Kind Regards Leon

4 3

how to update glib-2.28.8 to glib-2.40.0 or newer version
by qw 01 Jul '16

01 Jul '16

Hi, I'm trying to build gstreamer sdk on centos 6.7. When configure is run for 'gstreamer-1.8.2.tar.xz' on centos 6.7, error messages are reported as below: checking for GLIB... no configure: Requested 'glib-2.0 >= 2.40.0' but version of GLib is 2.28.8 configure: error: This package requires GLib >= 2.40.0 to compile. The command of 'yum install glib*' can only update glib to glib-2.28.8. How to update glib to the version of >=2.40.0 on centos 6.7? Thanks! Regards Andrew

3 2

[CENTOS ]IPTABLES - How Secure & Best Practice
by Leon Vergottini 01 Jul '16

01 Jul '16

Dear Members I hope you are all doing well. I am busy teaching myself iptables and was wondering if I may get some advise. The scenario is the following: 1. Default policy is to block all traffic 2. Allow web traffic and SSH 3. Allow other applications I have come up with the following: #!/bin/bash # RESET CURRENT RULE BASE iptables -F service iptables save # DEFAULT FIREWALL POLICY iptables -P INPUT DROP iptables -P FORWARD DROP iptables -P OUTPUT DROP # ------------------------------------------------------ # INPUT CHAIN RULES # ------------------------------------------------------ # MOST COMMON ATTACKS iptables -A INPUT -p tcp --tcp-flags ALL NONE -j DROP iptables -A INPUT -p tcp ! --syn -m state --state NEW -j DROP iptables -A INPUT -p tcp --tcp-flags ALL ALL -j DROP # LOOPBACK, ESTABLISHED & RELATED CONNECTIONS iptables -A INPUT -i lo -j ACCEPT iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # SSH iptables -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT # WEB SERVICES iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT # EMAIL iptables -A INPUT -p tcp -m tcp --dport 143 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 993 -j ACCEPT # OTHER APPLICATIONS iptables -A INPUT -p tcp -m tcp --dport XXXXX -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport XXXXX -j ACCEPT # ------------------------------------------------------ # OUTPUT CHAIN RULES # ------------------------------------------------------ # UDP iptables -A OUTPUT -p udp -j DROP # LOOPBACK, ESTABLISHED & RELATED CONNECTIONS iptables -A OUTPUT -i lo -j ACCEPT iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # SSH iptables -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT # WEB SERVICES iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT # EMAIL iptables -A INPUT -p tcp -m tcp --dport 143 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 993 -j ACCEPT # OTHER APPLICATIONS iptables -A INPUT -p tcp -m tcp --dport 11009 -j ACCEPT iptables -A INPUT -p tcp -m tcp --dport 12009 -j ACCEPT # ------------------------------------------------------ # SAVE & APPLY # ------------------------------------------------------ service iptables save service iptables restart To note: 1. The drop commands at the beginning of each chain is for increase performance. It is my understanding that file gets read from top to bottom and applied accordingly. Therefore, applying them in the beginning will increase the performance by not reading through all the rules only to apply the default policy. 2. I know the above point will not really affect the performance, so it is more of getting into a habit of structuring the rules according to best practice, or at least establishing a pattern for myself. How secure is this setup? Is there any mistakes or things that I need to look out for? Thank you in advance for your feedback. Kind Regards Leon

9 16

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

01 Jul '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. CEEA-2016:1375 CentOS 7 qla2xxx Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 30 Jun 2016 17:45:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2016:1375 CentOS 7 qla2xxx Enhancement Update Message-ID: <20160630174538.GA46122(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2016:1375 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1375.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 08a6bc752e27c15e9416e7e517f3d8196230222a0b48500feabb503a51526233 kmod-qla2xxx-8.07.00.33.07.3_k-1.el7_2.x86_64.rpm Source: 8c3640fe32a123a6f1630d3f3be4007be5c3a3bcbac94a6ea37c5ff21b921456 qla2xxx-8.07.00.33.07.3_k-1.el7_2.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 137, Issue 1 ***********************************************

1 0

Does centos 6.8 support gstreamer 1.8?
by qw 30 Jun '16

30 Jun '16

Hi, I found gstreamer offcial have just announced 1.8.2 version. ("gstreamer.freedesktop.org") But centos 6 only support gstreamer 0.10. When will centos 6 support gstreamer 1.8? Thanks! Regards Andrew

3 2

CentOS-7 Screen black after boot
by Venkata Balaji N 30 Jun '16

30 Jun '16

Hello Community, This is my first ever email to CentOS community. Firstly, CentOS is a great open-source operating system. I have been using it for years and recommending the same for production use to our customers. I have installed CentOS-7 operating system couple of days ago and everything was working fine. Yesterday, the screen got struck and the whole system was unresponsive, after a long wait, i have restarted the system. Since, then, i can only see the black screen and GUI is not coming up. I can remotely login to the system from Putty and can operate without any issues, the only issue is that GUI is not coming up. I have installed CentOS-7 server-GUI. Any help would be appreciated here. Regards, Venkata B N

1 0

VNC server issue- Gnome - oh no! Something has gone wrong
by Hersh 29 Jun '16

29 Jun '16

Hi, I have been using VNC on CentOS 7 server from last couple of months and it was running all fine till last night. Unfortunately, there was an abrupt power failure and system got restarted. Now, when I try to login with VNCviwer, it thrown an error message- "*Gnome - oh no! Something has gone wrong "* with a logout option. When I click on logout, I see black/dark gray screen with 3 check boxes. I googled to figure out a solution and tried several solutions but could not fix the problem. Any suggestion would be very helpful. Regards Hersh

3 4

CentOS-announce Digest, Vol 136, Issue 6
by centos-announce-request＠centos.org 29 Jun '16

29 Jun '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. CEBA-2016:1349 CentOS 7 lvm2 BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jun 2016 00:12:11 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1349 CentOS 7 lvm2 BugFix Update Message-ID: <20160629001211.GA46363(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1349 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1349.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9f8f2152738415ddef6509c16881468f8abedf7488490bfe724561ee7eb582c7 cmirror-2.02.130-5.el7_2.5.x86_64.rpm e23f39c92b83682c140324b0891d426bf538fbdc68cf7f267c2a87356816d89c device-mapper-1.02.107-5.el7_2.5.x86_64.rpm 0c3dc7d9d7957e749ad019f06e0cc1c87f3db76cb500457050ce2c3e46080b8b device-mapper-devel-1.02.107-5.el7_2.5.i686.rpm 4da48171c8f599255dd47809d5ed2cdbd23afe152c44540e4e6c41bb88cf7f6b device-mapper-devel-1.02.107-5.el7_2.5.x86_64.rpm b1f004cceca52345c14d2dec35b44d989d39003d3a0e37ae14ee08210296e157 device-mapper-event-1.02.107-5.el7_2.5.x86_64.rpm 6a8203ef009bd1dae1c2575bfaa89582a5d9b402e9a450ce3a787c22ead8f4a6 device-mapper-event-devel-1.02.107-5.el7_2.5.i686.rpm a2a822a1de226771fd00b9d6bce566def68a67b5c4ef1351f7d4e756a3d23e03 device-mapper-event-devel-1.02.107-5.el7_2.5.x86_64.rpm 44d8c251698d60f8bf82d71d774652c7743515edd9077a780bb33709303188e6 device-mapper-event-libs-1.02.107-5.el7_2.5.i686.rpm 59b65674dcab344b3d219b6961722bfd40780455bc0bce6bd02edd6dd768453c device-mapper-event-libs-1.02.107-5.el7_2.5.x86_64.rpm 8475f1a20a99c5f1d041187a531b5c5406c67bf84afb926096d11810f1a53d8e device-mapper-libs-1.02.107-5.el7_2.5.i686.rpm 4d964e6a7643010f2862791e2588e08f6011e4c656540d61d3ebe937ac9ce13a device-mapper-libs-1.02.107-5.el7_2.5.x86_64.rpm b7a90ef80f4e8ddb35257802a57c07660e1ddc7e2c4a9957edf382ff67ec1567 lvm2-2.02.130-5.el7_2.5.x86_64.rpm 65a4c81480d0efba21f0da7969a2f820d69e26934af24bf4fdb8c449a2d502dc lvm2-cluster-2.02.130-5.el7_2.5.x86_64.rpm 04d6d35438ff31602702872775f9fdc758c94d1e9656319dcfa09580ef21609d lvm2-devel-2.02.130-5.el7_2.5.i686.rpm e53af702e6143a89598e64754410bbdbb079fb3e5b657091d88f44fec28fa391 lvm2-devel-2.02.130-5.el7_2.5.x86_64.rpm abafec8cbed90c9e68a796b61235bab160be70a8d0a8290041d78c155d41804e lvm2-libs-2.02.130-5.el7_2.5.i686.rpm 6c0f6537d19eecc549c1c7adf01cdee3aa6d805b30496946fbcc73cb4b3fe582 lvm2-libs-2.02.130-5.el7_2.5.x86_64.rpm 39727f939e993c9baac491080ef3901b3d18536c3c4a7e12668bf381f15f99e9 lvm2-lockd-2.02.130-5.el7_2.5.x86_64.rpm 2f3b320f5108eef429344b89416a2fcf6e15a47e014faeff5b47c6a3ebe234a3 lvm2-python-libs-2.02.130-5.el7_2.5.x86_64.rpm 53316ba2995b27f5b7a4137817a66cd811c42c4ce286e682869d565f5bae76be lvm2-sysvinit-2.02.130-5.el7_2.5.x86_64.rpm Source: 399d8210953038b445e7ac3fc91fc13b517b11dc1a849f820f17296a27477a56 lvm2-2.02.130-5.el7_2.5.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 136, Issue 6 ***********************************************

1 0

Errors on yum upgrade
by henimp＠openmail.cc 28 Jun '16

28 Jun '16

During yum upgrade a couple days ago, I saw this: Cleanup : kernel-3.10.0-229.20.1.el7.x86_64 35/64 warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.softdep: remove failed: No such file or directory warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.devname: remove failed: No such file or directory Should I be concerned about this? What could have caused it? ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!

2 2

Re: [CentOS] UDP Constant IP Identification Field Fingerprinting Vulnerability
by James B. Byrne 28 Jun '16

28 Jun '16

On Mon, June 27, 2016 12:29, Gordon Messmer wrote: > On 06/26/2016 01:50 PM, James B. Byrne wrote: >> However, all I am seeking is knowledge on how to handle this using >> iptables. I am sure that this defect/anomaly has already been >> solved wherever it is an issue. Does anyone have an example on >> how to do this? > > > I think the bit you're missing is that you don't have to address every > detail that your auditors send you. You can label an item a false > positive. You can respond that you are aware, and that you don't > consider an item to be a security defect. Fingerprinting is an > excellent example thereof. As was already noted, the IP ID field is > just one of many aspects of IP networking that can be used to identify > Linux systems. If you don't address them all, addressing one is not a > useful exercise. I understand WRT false positive flagging. And that is exactly what I have done. However, the PCI DSS report piqued my interest in this matter and I thought to satisfy my curiosity. The other stuff flagged in the report seemed a little far-fetched to me. At least the explanation of why they were flagged did. As none of them affect our PCI status I have no interest in the rest. This one however I was previously unaware and so I wanted to discover more about it. Thank you for the information and especially for the references. Sincerely, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

Guest's Additions Virtual CD
by raving Joker 28 Jun '16

28 Jun '16

Hello to everyone I'm a new italian member so I'm sorry if my english isn't perfect. I was thinking... Why not (in CentOS 7) insert a tab in the installation phase that can permit an automatic installation of guest's additions tools (I'm using virtualbox, but it can be applied to other platforms with a menu), a little system that reveals the guest addition's cd and if isn't inserted, displays to the user a message with informations about how insert it and do the installation automatically? Thanks for all of people that want to reply, I know that this virtualization platforms are in part in discordance with the ethical free software's mindset...but why not in centos, with proper informative messages? Good afternoon Raving

1 0

Use USB2.0 Camera with KVM based VM
by Mark LaPierre 28 Jun '16

28 Jun '16

Hey All, I've been googleing this issue for hours but I can't find a workable solution. I found a reply to a bug posting that said the USB hub on the VM defaults to USB 1.1. I see this is true when I lsusb on the CentOS 7 guest. The reply to the bug post went on to say that the problem is that the USB 2.0 camera will not work with the USB 1.1 default hub and that I should change the hub from USB 1.1 to USB 2.0. I see no way to do that. Can anyone shed some light on this? Is there a way to change the USB hub from USB 1.1 to USB 2.0 inside the VM Manager? Is there a better way to get my USB 2.0 web camera to appear in my CentOS 7 guest? -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

2 1

Re: [CentOS] UDP Constant IP Identification Field Fingerprinting Vulnerability
by James B. Byrne 27 Jun '16

27 Jun '16

On Fri, June 24, 2016 12:24, John R Pierce wrote: > On 6/24/2016 9:20 AM, James B. Byrne wrote: >> We received a notice from our pci-dss auditors respecting this: >> >> CVE-2002-0510 The UDP implementation in Linux 2.4.x kernels keeps >> the >> IP Identification field at 0 for all non-fragmented packets, which >> could allow remote attackers to determine that a target system is >> running Linux. > > > 2.4 kernels are kinda old. kinda really really old. are you still > running CentOS 4 on PCI audited systems ?!?? > > The CVE is from 2002 and the kernel mentioned refers to the original report. Linux core team said it was a non-problem and the issue remains in the kernel found in CentOS-6.8. Possibly the one in 7. Perhaps it is still present in the development branch. However, all I am seeking is knowledge on how to handle this using iptables. I am sure that this defect/anomaly has already been solved wherever it is an issue. Does anyone have an example on how to do this? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

haproxy + Apache + virtual hosts -> wrong host is displayed
by Alexander Farber 24 Jun '16

24 Jun '16

Hello, I hope my question is not off-topic here. On CentOS 7.2.1511 I have installed: haproxy-1.5.14-3.el7.x86_64 httpd-2.4.6-40.el7.centos.1.x86_64 The /etc/haproxy/haproxy.cfg binds HAProxy to ports 80 and 443 and accepts HTTPS to slova.de: defaults mode http option http-server-close option forwardfor except 127.0.0.0/8 option redispatch .... frontend public bind 144.76.184.151:80 bind 144.76.184.151:443 ssl crt /etc/pki/tls/certs/slova.de.pem reqidel ^X-Forwarded-Proto: reqidel ^X-Forwarded-For: reqadd X-Forwarded-Proto:\ https if { ssl_fc } option forwardfor default_backend apache backend apache server domain 127.0.0.1:8080 The /etc/httpd/conf/httpd.conf binds Apache to port 8080 and serves several Wordpress sites: Listen 127.0.0.1:8080 ServerName 144.76.184.151 <VirtualHost 127.0.0.1:8080> DocumentRoot /var/www/html/afarber.de ServerName afarber.de ErrorLog logs/afarber.de/error_log CustomLog logs/afarber.de/access_log common </VirtualHost> <VirtualHost 127.0.0.1:8080> DocumentRoot /var/www/html/ruhrgebietsingle.de ServerName ruhrgebietsingle.de ErrorLog logs/ruhrgebietsingle.de/error_log CustomLog logs/ruhrgebietsingle.de/access_log common </VirtualHost> <VirtualHost 127.0.0.1:8080> DocumentRoot /var/www/html/bukvy.de ServerName bukvy.de ErrorLog logs/bukvy.de/error_log CustomLog logs/bukvy.de/access_log common </VirtualHost> <VirtualHost 127.0.0.1:8080> DocumentRoot /var/www/html/slova.de ServerName slova.de ErrorLog logs/slova.de/error_log CustomLog logs/slova.de/access_log common </VirtualHost> When I open http://slova.de or https://www.slova.de they work fine. But when I try to open same URLs with "www." prepended, the browser displays http://ruhrgebietsingle.de (the 2nd site out of 4) Why does it happen? I just can not figure it out. What tool would help here to debug? Thank you Alex

1 1

UDP Constant IP Identification Field Fingerprinting Vulnerability
by James B. Byrne 24 Jun '16

24 Jun '16

We received a notice from our pci-dss auditors respecting this: CVE-2002-0510 The UDP implementation in Linux 2.4.x kernels keeps the IP Identification field at 0 for all non-fragmented packets, which could allow remote attackers to determine that a target system is running Linux. The NVD entry for which contains this note: CHANGE> [Cox changed vote from REVIEWING to NOOP] Cox> So I asked some kernel guys about this - it's not considered an issue. There are several other ways to identify Linux on the wire and people who care about this kind of thing rewrite their packets in various ways via firewall technology to trick the identifier programs. So, what packet mangling may be done in iptables to solve this without breaking udp transmission? I take it that we are talking about something in the prerouting chain but what kind of mangelling is safe? Is there an example somewhere? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

CPU Compatibility Question
by listmail 23 Jun '16

23 Jun '16

Hi All, Hopefully someone with broad overview of CentOS compatibility issues can comment on this: I am evaluating a Supermicro X10SLM motherboard with an Intel E3-1231 v3 CPU. Testing with boots from Live DVDs, the CentOS 6.x family is panicking at boot time. I have tried 6.8, 6.5, and 6.3, and each one panics at slightly different points, but they all seem to fail after udev starts up (or tries to). On the other hand, I was able to boot CentOS 7.0 1511 from the Live CD. According to the compatibility chart over here: https://access.redhat.com/support/policy/intel ...anything later than 6.3 (6.4 and up) should work with the E3-12xx v3 family of processors. But those are not the results I am seeing. Does anyone have experience or commentary on this compatibility issue? Thanks, --Bill

2 2

sssd.conf file missing
by Kaplan, Andrew H. 23 Jun '16

23 Jun '16

Hello -- We are running CentOS 7.2 on a virtual machine, and we are trying to set up LDAP authentication. The ldap packages that are currently installed on the system are the following: python-sss 1.13.0-40.el7_2.4 python-sssdconfig 1.13.0-40.el7_2.4 sssd 1.13.0-40.el7_2.4 sssd-ad 1.13.0-40.el7_2.4 sssd-client 1.13.0-40.el7_2.4 sssd-common 1.13.0-40.el7_2.4 sssd-common-pac 1.13.0-40.el7_2.4 sssd-dbus 1.13.0-40.el7_2.4 sssd-ipa 1.13.0-40.el7_2.4 sssd-krb5 1.13.0-40.el7_2.4 sssd-krb5-common 1.13.0-40.el7_2.4 sssd-ldap 1.13.0-40.el7_2.4 sssd-libwbclient 1.13.0-40.el7_2.4 sssd-libwbclient-devel 1.13.0-40.el7_2.4 sssd-proxy 1.13.0-40.el7_2.4 sssd-tools 1.13.0-40.el7_2.4 I ran the following commands to set up LDAP/AD authentication: # ln -s /bin/bash /bin/PHSshell # ln -s /home /PHShome # authconfig --enablesssdauth --enablemkhomedir --enablesssd -update # chkconfig sssd on # service sssd restart Initially, I ran into problems because I had not created an sssd.conf file. Eventually I did create one, and its contents are the following: [<domain>.org] enumate = true cache_credentials = TRUE id_provider = ldap auth_provider = ldap chpass_provider = ldap ldap_uri = ldap://ldap.<domain>.org ldap_search_base = dc=<domain>,dc=org tls_reqcert = demand ldap_tls_cacert /etc/pki/tls/certs/ca-bundle.crt If there are any additions or corrections that I need to make, please let me know. I reran the service sssd restart command, and the error message that I am seeing via journalctl -xe is the following: Unit sssd.service has begun starting up. Jun 22 16:05:34 roadtest2.partners.org sssd[6384]: SSSD couldn't load the configuration database [5]: Input/output error. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: sssd.service: control process exited, code=exited status=4 Jun 22 16:05:34 roadtest2.partners.org systemd[1]: Failed to start System Security Services Daemon. -- Subject: Unit sssd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman.../systemd-devel<http://lists.freedesktop.org/mailman/listinfo/systemd-devel> -- -- Unit sssd.service has failed. -- -- The result is failed. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: Unit sssd.service entered failed state. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: sssd.service failed. Jun 22 16:05:34 roadtest2.partners.org polkitd[787]: Unregistered Authentication Agent for unix-process:6369:52587318 (system bus name :1.2287, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Any ideas? The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

2 1

Re: [CentOS] sssd.conf file missing
by Kaplan, Andrew H. 23 Jun '16

23 Jun '16

Hello - I have made the following changes to the nsswitch.conf file as suggested by another mailing-list member: Domain = <company>.org ... Method = nsswitch and I have restarted idmapd service. I checked the nsswitch.conf file, and references to sss are mentioned in the following lines: passwd: shadow: group: ... services: netgroup: ... automount: I also ran the following command syntax as root to check the sssd configuration: sssd -c /etc/sssd/sssd.conf -d2 -i The output was as follows: sssd -c /etc/sssd/sssd.conf -d2 -i (Thu Jun 23 10:44:39:600097 2016) [sssd] [add_implicit_services] (0x0040): id_provider is not set for domain [<company>.org], trying next domain. (Thu Jun 23 10:44:39:600411 2016) [sssd] [confdb_get_domain_internal] (0x0010): Unknown domain [<company>.org] (Thu Jun 23 10:44:39:600443 2016) [sssd] [confdb_get_domains] (0x0010): Error (2 [No such file or directory]) retrieving domain [<company>.org], skipping! (Thu Jun 23 10:44:39:600452 2016) [sssd] [confdb_get_domains] (0x0010): No properly configured domains, fatal error! (Thu Jun 23 10:44:39:600458 2016) [sssd] [get_monitor_config] (0x0010): No domains configured. (Thu Jun 23 10:44:39:600483 2016) [sssd] [main] (0x0020): SSSD couldn't load the configuration database. The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

2 1

Re: [CentOS] sssd.conf file missing
by Kaplan, Andrew H. 23 Jun '16

23 Jun '16

Hello - I have made the changes to the nsswitch.conf file as suggested, and I have restarted idmapd service. I also ran the following command syntax as root to check the sssd configuration: sssd -c /etc/sssd/sssd.conf -d2 -i The output was as follows: sssd -c /etc/sssd/sssd.conf -d2 -i (Thu Jun 23 10:44:39:600097 2016) [sssd] [add_implicit_services] (0x0040): id_provider is not set for domain [<company>.org], trying next domain. (Thu Jun 23 10:44:39:600411 2016) [sssd] [confdb_get_domain_internal] (0x0010): Unknown domain [<company>.org] (Thu Jun 23 10:44:39:600443 2016) [sssd] [confdb_get_domains] (0x0010): Error (2 [No such file or directory]) retrieving domain [<company>.org], skipping! (Thu Jun 23 10:44:39:600452 2016) [sssd] [confdb_get_domains] (0x0010): No properly configured domains, fatal error! (Thu Jun 23 10:44:39:600458 2016) [sssd] [get_monitor_config] (0x0010): No domains configured. (Thu Jun 23 10:44:39:600483 2016) [sssd] [main] (0x0020): SSSD couldn't load the configuration database. The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

1 0

Re: [CentOS] sssd.conf file missing
by Kaplan, Andrew H. 23 Jun '16

23 Jun '16

Hello – Thank-you for your e-mail. I corrected the syntax in the file, and I have confirmed the permissions are correct: -rw-------. 1 root root 266 Jun 23 08:45 sssd.conf Unfortunately, the error condition and messages listed in my initial e-mail are still present. From: l(a)avc.su [mailto:l@avc.su] Sent: Thursday, June 23, 2016 8:34 AM To: CentOS mailing list; Kaplan, Andrew H. Subject: Re: [CentOS] sssd.conf file missing Hello Andrew. The sssd.conf should be owned by root:root, mode 0600. Also please note this line in your config: [<domain>.org] enumate = true it's enumerate, not enumate. 23.06.2016, 15:24, "Kaplan, Andrew H." <ahkaplan(a)partners.org<mailto:ahkaplan@partners.org>>: Hello -- We are running CentOS 7.2 on a virtual machine, and we are trying to set up LDAP authentication. The ldap packages that are currently installed on the system are the following: python-sss 1.13.0-40.el7_2.4 python-sssdconfig 1.13.0-40.el7_2.4 sssd 1.13.0-40.el7_2.4 sssd-ad 1.13.0-40.el7_2.4 sssd-client 1.13.0-40.el7_2.4 sssd-common 1.13.0-40.el7_2.4 sssd-common-pac 1.13.0-40.el7_2.4 sssd-dbus 1.13.0-40.el7_2.4 sssd-ipa 1.13.0-40.el7_2.4 sssd-krb5 1.13.0-40.el7_2.4 sssd-krb5-common 1.13.0-40.el7_2.4 sssd-ldap 1.13.0-40.el7_2.4 sssd-libwbclient 1.13.0-40.el7_2.4 sssd-libwbclient-devel 1.13.0-40.el7_2.4 sssd-proxy 1.13.0-40.el7_2.4 sssd-tools 1.13.0-40.el7_2.4 I ran the following commands to set up LDAP/AD authentication: # ln -s /bin/bash /bin/PHSshell # ln -s /home /PHShome # authconfig --enablesssdauth --enablemkhomedir --enablesssd -update # chkconfig sssd on # service sssd restart Initially, I ran into problems because I had not created an sssd.conf file. Eventually I did create one, and its contents are the following: [<domain>.org] enumate = true cache_credentials = TRUE id_provider = ldap auth_provider = ldap chpass_provider = ldap ldap_uri = ldap://ldap.<domain>.org ldap_search_base = dc=<domain>,dc=org tls_reqcert = demand ldap_tls_cacert /etc/pki/tls/certs/ca-bundle.crt If there are any additions or corrections that I need to make, please let me know. I reran the service sssd restart command, and the error message that I am seeing via journalctl -xe is the following: Unit sssd.service has begun starting up. Jun 22 16:05:34 roadtest2.partners.org sssd[6384]: SSSD couldn't load the configuration database [5]: Input/output error. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: sssd.service: control process exited, code=exited status=4 Jun 22 16:05:34 roadtest2.partners.org systemd[1]: Failed to start System Security Services Daemon. -- Subject: Unit sssd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman.../systemd-devel<http://lists.freedesktop.org/mailman/listinfo/systemd-devel> -- -- Unit sssd.service has failed. -- -- The result is failed. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: Unit sssd.service entered failed state. Jun 22 16:05:34 roadtest2.partners.org systemd[1]: sssd.service failed. Jun 22 16:05:34 roadtest2.partners.org polkitd[787]: Unregistered Authentication Agent for unix-process:6369:52587318 (system bus name :1.2287, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Any ideas? The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. _______________________________________________ CentOS mailing list CentOS(a)centos.org<mailto:CentOS@centos.org> https://lists.centos.org/mailman/listinfo/centos

3 6

Ovirt migration
by Andrew Dent 23 Jun '16

23 Jun '16

Hi We have a Single box running Ovirt 3.5.6.2-1 + CentOS7. The Engine, VDSM Host and the Storage is all on the Single box, which contains 2 * RAID1 arrays. We are looking to purchase a second box, and I'm wondering if someone can please help me to understand of how best to migrate to a HA environment using both boxes. We do have some additional NFS storage on the network that we can temporarily move VMs to. Is it possible to migrate our current Ovirt setup to be HA using Gluster, or would we need to start again by exporting all VMs, wipe box one and reinstall CentOS & Ovirt, then install CentOS and Ovirt on box two. I'd like to move the Engine to be hosted in a VM as well. Can we do HA without Gluster? Pros/Cons.... Regards Andrew Dent

2 1

KVM HA
by Tom Robinson 23 Jun '16

23 Jun '16

Hi, I have two KVM hosts (CentOS 7) and would like them to operate as High Availability servers, automatically migrating guests when one of the hosts goes down. My question is: Is this even possible? All the documentation for HA that I've found appears to not do this. Am I missing something? My configuration so fare includes: * SAN Storage Volumes for raw device mappings for guest vms (single volume per guest). * multipathing of iSCSI and Infiniband paths to raw devices * live migration of guests works * a cluster configuration (pcs, corosync, pacemaker) Currently when I migrate a guest, I can all too easily start it up on both hosts! There must be some way to fence these off but I'm just not sure how to do this. Any help is appreciated. Kind regards, Tom -- Tom Robinson IT Manager/System Administrator MoTeC Pty Ltd 121 Merrindale Drive Croydon South 3136 Victoria Australia T: +61 3 9761 5050 F: +61 3 9761 5051 E: tom.robinson(a)motec.com.au

9 23

Install C7 VM on C6 Host
by Mark LaPierre 22 Jun '16

22 Jun '16

Hey all, Before I waste myself a bunch of time trying the impossible I figured I would ask if I can install an instance of C7 in a KVM based VM on a C6 host. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

4 4

Centos 7 boot hanging unless systemd.log_target=console is used
by James Hartig 22 Jun '16

22 Jun '16

I have multiple VMs that are hanging on boot. Sometimes they'll boot fine after 5 mins and other times it'll take over an hour. The problem seems to be related to journald but I'd like to figure out how I can get more information. The VMs are running CentOS 7.1.1503. systemd and journald are both version 208. We are reluctant to upgrade to the newest CentOS because we found that journal-gatewayd is broken on boxes that have been upgraded. If I add the kernel parameter systemd.log_target=console then they boot up fine without hanging at all. I can't seem to get into the debug shell (Ctrl+Alt+F9) while the system is hanging after enabling debug-shell. Adding systemd.log_level=debug without systemd.log_target=console seems to make the problem worse and causes a hang of over an hour. I tried deleting /var/log/journal but that didn't help and I ran fsck on the root drive with no errors. I also tried masking systemd-udev-settle but that didn't help either. While the system is hanging the last console output is "Welcome to CentOS Linux 7 (Core)!". Here's the output from dmesg without "quiet" kernel parameter and without "systemd.log_level=debug": http://gobin.io/zScc systemd-analyze blame doesn't seem to help either (top 3): 10.451s nginx.service 7.149s network.service 2.178s etcd.service What else can I do to debug this? Thanks!

1 0

CentOS-announce Digest, Vol 136, Issue 4
by centos-announce-request＠centos.org 22 Jun '16

22 Jun '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. CEBA-2016:1266 CentOS 6 tzdata BugFix Update (Johnny Hughes) 2. CEBA-2016:1266 CentOS 7 tzdata BugFix Update (Johnny Hughes) 3. CESA-2016:1267 Important CentOS 6 setroubleshoot-plugins Security Update (Johnny Hughes) 4. CESA-2016:1267 Important CentOS 6 setroubleshoot Security Update (Johnny Hughes) 5. CEBA-2016:1266 CentOS 5 tzdata BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 Jun 2016 18:43:34 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1266 CentOS 6 tzdata BugFix Update Message-ID: <20160621184334.GA56003(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1266 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1266.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 27275c88c15db6a83722068e6f998d74ccc00bafbb2a80cb4590b47b6ed9e5a2 tzdata-2016e-1.el6.noarch.rpm df6503b270368fa7f3b9147637e423ca6db45485f03072e9d5e273409d782007 tzdata-java-2016e-1.el6.noarch.rpm x86_64: 27275c88c15db6a83722068e6f998d74ccc00bafbb2a80cb4590b47b6ed9e5a2 tzdata-2016e-1.el6.noarch.rpm df6503b270368fa7f3b9147637e423ca6db45485f03072e9d5e273409d782007 tzdata-java-2016e-1.el6.noarch.rpm Source: 65814adef78cc1939847dc32f5ffbce8db34fc58acd8f1a002e002f5917ea638 tzdata-2016e-1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 21 Jun 2016 19:05:22 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1266 CentOS 7 tzdata BugFix Update Message-ID: <20160621190522.GA59766(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1266 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1266.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 35e627912852d34e84ea76e5cbcadf233c7945185320fc0a8b2fa7e5e4ee2099 tzdata-2016e-1.el7.noarch.rpm 688596a9be955e0f481845db5b41da2232ef701d56967971e2fe382be32fdad4 tzdata-java-2016e-1.el7.noarch.rpm Source: 32bbb097ae98767d8b45e3b38f03ae1c205eecaef6d1bcd58912fd6f5443a5fb tzdata-2016e-1.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 21 Jun 2016 19:07:23 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1267 Important CentOS 6 setroubleshoot-plugins Security Update Message-ID: <20160621190723.GA60050(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1267 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1267.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3b8bbdeaf83bf2ae720395dd7ea13c3946f439e85bc60731f54414d85beb8a90 setroubleshoot-plugins-3.0.40-3.1.el6_8.noarch.rpm x86_64: 3b8bbdeaf83bf2ae720395dd7ea13c3946f439e85bc60731f54414d85beb8a90 setroubleshoot-plugins-3.0.40-3.1.el6_8.noarch.rpm Source: 524e4dac899bb14f96404df56f34475e037b4c9c770db40b4e039a05b5b1804f setroubleshoot-plugins-3.0.40-3.1.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 21 Jun 2016 19:07:49 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1267 Important CentOS 6 setroubleshoot Security Update Message-ID: <20160621190749.GA60273(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1267 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1267.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6162d2040eee1d468be25455dff5505b881b0e843848a0d770b47f8f7b6de9fe setroubleshoot-3.0.47-12.el6_8.i686.rpm 711deca2ead9d099e1ca7f7a951902a3c7380ba0afa701870a280d23a7cbce89 setroubleshoot-doc-3.0.47-12.el6_8.i686.rpm 856cbc9cbfd54ebc46934f28aff9b56779aabc387ca4ecd5ebb0457572cf056e setroubleshoot-server-3.0.47-12.el6_8.i686.rpm x86_64: f108837ced085b3b45952528799c88f53bd1203d7e2f46e65c21a2ef9baa44ed setroubleshoot-3.0.47-12.el6_8.x86_64.rpm 0a76b22ee3f5d8bdcec67c3def7496f7c276c77db4bf23ac6cd5a208ed066260 setroubleshoot-doc-3.0.47-12.el6_8.x86_64.rpm 8a91304bb9f4f120a78858f5e18555b43027997923b0a3a73bdaa2b3c5ecabb4 setroubleshoot-server-3.0.47-12.el6_8.x86_64.rpm Source: 64dea800d736c50ce5d72c06dad0cfb36857a46254d84f01131bd2a09da549d5 setroubleshoot-3.0.47-12.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Tue, 21 Jun 2016 19:09:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1266 CentOS 5 tzdata BugFix Update Message-ID: <20160621190943.GA27729(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1266 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1266.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 980470351aa45a505738913c6b98e22543d182acb91410d9d23adcd5ce22efa4 tzdata-2016e-1.el5.i386.rpm f1ab933aec64ab8335388d2dc170670e6842c1828da3d9e6761d6ea4653bb729 tzdata-java-2016e-1.el5.i386.rpm x86_64: 14eea96779590f3a0a341ac8e144377cc2f5327c6e3df6d2757daf0e6a753123 tzdata-2016e-1.el5.x86_64.rpm 27051668651683bf9255059ca73b75ad2a42dee0b97c38065f073feee90fdd25 tzdata-java-2016e-1.el5.x86_64.rpm Source: 2be0737a89567aab8fa13639cfd0f98a04e6f2b337d5604e470ca5d44740f557 tzdata-2016e-1.el5.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 136, Issue 4 ***********************************************

1 0

Any further developments on CentOS7 for i386?
by Kay Schenk 22 Jun '16

22 Jun '16

Well I haven't tested out the CentOS 7 for i386 yet as sent in the message of 06/02-- https://lists.centos.org/pipermail/centos-devel/2015-June/013426.html Nor have I seen any additional information. So how is this going? I'm almost ready to jump in as I would really prefer to be on Gnome 3. -- -------------------------------------------- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu

3 7

Package NetworkManager-libreswan-0.9.8.0-5.el7.x86_64.rpm is not signed
by Jules Bashizi 21 Jun '16

21 Jun '16

How to inst that Network manager please ================ Worthy agent of Light ================ Jules Irenge MSc Student University of Liverpool

4 3

Redirecting port 8080 to port 80 - how to add in /etc/sysconfig/iptables file?
by Alexander Farber 21 Jun '16

21 Jun '16

Good evening, on a CentOS 7 LAMP (not gateway) dedicated server I am using iptables-services with the following /etc/sysconfig/iptables: *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [294:35064] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type any -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp -m multiport --dports 25,80,443,8080 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 --tcp-flags FIN,SYN,RST,ACK SYN -m limit --limit 2/min --limit-burst 1 -j ACCEPT COMMIT Also I am running Jetty as user "nobody" at the port 8080 using the /etc/systemd/system/websocket-handler.service file: [Unit] Description=WebSocket Handler Service After=network-online.target [Service] Type=simple User=nobody Group=nobody ExecStart=/usr/bin/java -classpath '/usr/share/java/jetty/*' de.afarber.MyHandler 144.76.184.151:8080 ExecStop=/bin/kill ${MAINPID} SuccessExitStatus=143 [Install] WantedBy=multi-user.target However I actually need my Jetty program to run at port 80 - so that users behind corporate firewalls can connect too. The Jetty doc at https://www.eclipse.org/jetty/documentation/current/setting-port80-access.h… suggests to run the command # iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080 but I can not figure out the corresponding line for the /etc/sysconfig/iptables I have tried running the above command and then "iptables -S" to see the added rule, but that didn't really work. Thank you Alex

6 11

Pulling in broadwell support for cent6u5
by jsl6uy js16uy 21 Jun '16

21 Jun '16

Hello, all. Hope all is well Is it possible to install kernel and support files from 6u7 into a base 6u5 image to achieve full broadwell support in 6u5? We are "locked", clearly not fully since willing to up jump kernels, on 6u5. Thanks for any and all help

4 7

Re: [CentOS] https and self signed
by James B. Byrne 21 Jun '16

21 Jun '16

On Mon, June 20, 2016 13:16, Gordon Messmer wrote: > On 06/20/2016 07:47 AM, James B. Byrne wrote: >> On Sat, June 18, 2016 18:39, Gordon Messmer wrote: >> >>> I'm not interested in turning this in to a discussion on >>> epistemology. >>> This is based on the experience (the evidence) of some of the >>> world's foremost experts in the field (Akamai, Cisco, EFF, >>> Mozilla, etc). I would rather look to Bruce Schneier and Noam Chomsky for guidance before I would take security advice from organisations that have already shown to be compromised in the matters of their clients' security -- the EFF being the sole exception in the list provided. Or so I presently believe. >> Really? Then why did you forward your reply a private message to a >> public mailing list if not to do exactly what you claim you wish to >> avoid? > > Accidents happen. I didn't intentionally mail you off-list, > and when I noticed that I had, seconds later, I re-sent the > message to the list, expecting that you'd notice and understand > that I intended to keep the conversation on the list. > Except that I get the list as a digest. Which means that your assumptions were wrong. Funny that think you not? > ..which isn't relevant to the question of what you consider "evidence" > of security practice implications. > > Look, go to https://www.google.com/ right now and tell me what you > see. A snoop that self-signs its own certificates? > Do you suddenly distrust the internet's single largest domain? Do you > think they implement poor security practices? > My distrust of Google developed over many years. There was nothing sudden about it. But it is deep now. >>> For someone who wants "evidence" you make a lot of unsupported >>> assertions. You do see the irony, don't you? I assert my opinions if that is what you are referring to. I do not claim them to be fact. I believe them to be true but I admit readily that I may be wrong. Indeed I most certainly must be wrong in some of them. My difficulty begin determining which ones. However, I have formed my opinions on the basis of a long term exposure to security matters both pre and post Internet. And I have seen before the same thoughtless enthusiasms for things shiny and different in the security community. Things adopted and put into practice without even the most cursory of trials and evaluations for effectiveness and efficacy -- not to mention lawfulness on some occasions --. Sometimes I have had to deal with the consequences of those choices at the pointy end of the stick. Thus if I am to adopt a different point of view then I require something in the way of supporting measurable evidence to show that I am wrong and that others are right. >> The difference is that I state this is my opinion and I do not claim >> it as a fact. Your statement claimed a factual basis. I was >> naturally curious to see what evidence supported your claim. > > Citation required. > > Allow me an example. To quote you: > "The usual way a private key gets compromised is by theft or by > tampering with its generation. Putting yourself on a hamster wheel of > constant certificate generation and distribution simply increases the > opportunities for key theft and tampering." > > Now, when you asked "what possible benefit accrues from changing > secured device keys on a frequent basis?" I pointed you to > letsencrypt's documentation, which describes the benefits of > 90-day certificates. Having actual software in the possession of users rendered unusable by a policy decision implemented in the name of security is not beneficial. Referring to others self-justification of measures they have already implemented is not evidence. It is argument. Which has its place providing that one accepts the fundamental postulates of the positions being argued. These, in this case, require evidence. Assertions that these measures solve certain perceived flaws without addressing the costs of those measures is a one-side argument and not very convincing in my opinion. Refusing to deal with that is simply ignoring the elephant in the room. > > So, please describe how I am "claiming a factual basis" while you are > not. > >> Automated security is BS. It has always been BS and it always will >> be BS. That is my OPINION. It may not be a fact for I lack >> empirical evidence to support it. However, it has long been my >> observation that when people place excessive trust in automation >> they are are eventually and inevitably betrayed by it. Often at >> enormous cost. > > This is what I consider "enormous cost": > https://en.wikipedia.org/wiki/Heartbleed#Certificate_renewal_and_revocation > > After a major security bug which exposed private keys, hundreds of > thousands of servers did not take the required action to secure their > services, and the vast majority of those that took *some* action did > it incorrectly and did not resolve the problem. > > Had those sites been using letsencrypt and renewing automatically, > the exposed keys would have been replaced within 90 days > (typically 60 max, so 30 days on average). Instead, it is likely > that the problem will remain a risk for "months, if not years, to > come." > > And that's empirical evidence, which you have yet to offer. Again, you miss the point. I am not offering evidence of something that I am claiming as fact. I am seeking evidence in support of what someone else is claiming as fact. Evading the question may be a good rhetorical technique but it is hardly science. And your 'evidence' as presented above presupposes a number of unspoken assumptions. Some of which I fear would not stand scrutiny. The consequences of Heartbleed are well known to me. I had to tear down and re-establish our entire PKI because of it. However, anecdotal references to specific cases where a particular practice might, and let us remember that HB was out in the wild being exploited for at least two years before being publicly revealed, just might have provided some protection in some cases does not prove anything. In the case cited I do not believe changing certificates on an hourly basis would have made much difference against an technically proficient attacker exploiting the weakness. It is well to recall how HB came to be. A misguided attempt at an improvement in protocol exchange which amounted to not much more than gilding-the-lily and which since has been discarded without noticeable loss. What prevents similarly motivated 'improvements' to an automated certificate authority from having equally damaging effects on the robustness of the the certificates that they provide? We trusted OpenSSL because it was open. How do you trust an organisation's internal practices once they have been automated? Does anyone here actually believe that once in production this automation is or will be adequately documented? Or that said documentation will be rigourously maintained up-to-date? Or that independent and competent audits will be regularly conducted without notice? I take particular care with my PKI. I rebuild all the moduli for ssh on all of our servers for SSH. Because I trust no-one with my security. And that includes RedHat and any other external organisation, volunteer or commercial, open-source or proprietary. Automating your certificate replacement and entrusting it to an outside provider is begging to have some state actor or other financially powerful group subvert it. Look at what the NSA pulled off with RSA. That was for just money. What about patriotism? What would a true believer do if asked by his state and they were in a position to act? Think of the security nightmare that would result from having the certificate production of an automated 90 day certificate authority tampered with and left undetected for even a modest amount of time, say 180 days. At its core security is about risk analysis. And at the core of risk analysis is cost/benefit analysis. If the cost of a security measure exceeds the value of what is being secured then it makes no sense. I am seeking that cost-benefit analysis for short term certificates. And I have not seen anything in the way of objective evidence that supports the assertion that short-term certificates, or passwords for that matter, provide any measurable security benefit other than the feel-good sense that "at least its something". For one thing, this position presupposes that the rest of your security is so bad that frequent key compromise is inevitable. For another is assumes that the cost to users having to constantly deal with change is negligible. I run a business. Let me assure you that the cost of change is never negligible. > >> This impediment however is strictly an artefact of signing code with >> short term certificates. I simply had to reset the date on my MB >> back to some future date when the certificate was valid and >> everything worked fine. > > Apple's intermediate certs have a 10 year lifetime. If you consider > that "short term" then I fear that nothing is suitable in your > opinion. Apple evidently did not use those certificates to sign their software in this case. So you point is irrelevant even if it may be true. > >> But hey, what is my time worth in comparison to the security those >> certificates provided? SECURITY that was trivially evaded in the >> end. > > Fixing your clock is not "evading" security. Setting a clock backwards in time by two years is 'fixing it'? A curious point of view in my opinion. > >> Exactly what mindless person or committee of bike-shedders decided >> that software should be distributed so that copies of it expire? > > Expiration is a fundamental aspect of x509 certificates. Do you > understand x509 at all? Expiry is a fundamental part of many things including life itself. That does not imply that shorter is better. Why sign software with an expiry date when you know that your recovery programme will fail to operate after it expires? Imagine that you are on a hospital operating table and the defibrillators fail to function because the certificate that signed the firmware has expired. And that the immediate the fix is to simply reset the computer clock in the defibrillator controller backwards in time. Which of course no-one in the OR knows. So, too bad. But, you were secure when you expired. There is absolutely no sensible reason why the recovery software could not have simply warned me that the signature had expired and then asked me if I wished to proceed regardless. Having made the design decision that it would not do so then it was incumbent on the organisation responsible to allow people to override it. Instead they offer up some weasel-worded warning about "TAMPERING" and "CORRUPTION". Just what a person in the middle of system recovery is waiting to hear. Most of what passes for informed opinion about security is folk remedy dressed up with techno-babble and pushed onto an audience mostly too embarrassed to admit that they do not understand what is being talked about. In my opinion of course. However, decisions having real consequences are made on the basis of such ignorant acceptance of received wisdom. Therefore I think it important to challenge those that assert such things to produce convincing evidence that what they say is so. I understand that you believe that short term certificates and passwords and such provide a measure of security. That very well may be the case. I am not trying to convince you otherwise. All I ask for is a reasonable explanation of how much these practices cost those that employ them, how much benefit they provide to those users and what further risks they introduce. Security is a funny sort of thing being mostly based on our fear of the unknown; our too-active imaginations; and our attraction to the spectacular at the cost of dealing adequately with the mundane. At one time an automobile had to be preceded by a pedestrian waving a red flag. This too was done for the general security of all. We do not do it any more so there must have been a reason we stopped. I suggest that it was because the evidence did not support a positive cost/benefit analysis. But it sure sounded reasonable at the time to people that had little or no experience with automobiles. YMMV. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

CentOS 6 + nux-dextop: GIMP vs. GIMP 2.8 ?
by Nicolas Kovacs 21 Jun '16

21 Jun '16

Hi, I just setup a CentOS 6 desktop with the nux-dextop repository activated. When installing GIMP (yum install gimp), I get a gimp package as well as a gimp28 package. I understand this is the Nux-Dextop GIMP 2.8 package. Unfortunately this doesn't work so well with my system. It's not localized (menus appear in english, though the system is in French), the main GTK theme (Murrina Gilouche) is not managed and the application has that ugly east german look like in the good old GTK1 days, and there are two redundant menu entries, one of which is not responsive. I'd like to be able to install the plain "official" GIMP 2.6 application on my system, but when I try to 'yum remove gimp28', it takes the whole GIMP stuff down the drain with it. Note: I'm already using the Yum Priorities plugin. Official repos (base, updates and extra) are configured with a priority of 1, the other stuff (epel, adobe, nux-dextop) has a priority of 10. Any suggestions? Cheers from the sunny South of France, Niki Kovacs -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

3 5

bad iscsi performance after upgrade to CentOS 7.2
by Ulrich Leodolter 21 Jun '16

21 Jun '16

hi all, after i upgraded a physical server (SUN FIRE X4170) from CentOS 6.8 to 7.2 i am not able to get the same iSCSI read performance. the server is connected to HP P2000 Storage via 2 x 1GbE Ethernet. CentOS 6.8 gives me full read performance on raw iSCSI devices /dev/sdxx at 115MB/s. CentOS 7.2 allows only 90-100MB/s, read performance varies and is not stable like for 6.8 the multipath performance on 7.2 is even worse. CentOS 6.8 allows to read a full speed and stable 220MB/s. CentOS 7.2 maximum was 140MB/s after i disabled readahead for multipath devices in tuned. btw. i tried many recommended optimizations in 7.2, but i am not getting the raw iSCSI read performance than on 6.8, and on 6.8 i had no special tuning für iSCSI. mtu 9000 is set and verified for both OS, other settings like network buffers are almost identical. has anyone an idea why iSCSI read performance degraded in CentOS 7.2 ? best regards ulrich

2 1

https and self signed
by Jerry Geis 21 Jun '16

21 Jun '16

I followed the instructions here https://wiki.centos.org/HowTos/Https Checking port 80 I get the file... curl http://localhost/file.html <HTML> <FORM> Working </FORM> </HTML> Checking port 443 I get and error curl https://localhost/file.html curl: (60) Peer's certificate issuer has been marked as not trusted by the user. More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. How do I get past this? I was looking to just self sign for https. Yes I can added the --insecure for curl - but - my other app doesn't seem to work either - perhaps getting the same return message instead of the actual file. Thanks, jerry

13 39

Re: [CentOS] https and self signed
by James B. Byrne 21 Jun '16

21 Jun '16

On Sat, June 18, 2016 18:39, Gordon Messmer wrote: > On 06/18/2016 02:49 PM, James B. Byrne wrote: >> On Fri, June 17, 2016 21:40, Gordon Messmer wrote: >>> https://letsencrypt.org/2015/11/09/why-90-days.html >> With respect citing another person's or people's opinion in support >> of >> your own is not evidence in the sense I understand the word to mean. > > I'm not interested in turning this in to a discussion on epistemology. > This is based on the experience (the evidence) of some of the world's > foremost experts in the field (Akamai, Cisco, EFF, Mozilla, etc). Really? Then why did you forward your reply a private message to a public mailing list if not to do exactly what you claim you wish to avoid? > >> The assertion expressed in the link given above that 90-day >> certificate lives will serve to increase certificate renewal >> automation is at best a pious hope. > > You are ignoring the fact that the tool used to acquire letsencrypt > certificates automates the entire process. They're not merely hoping > that users will automate the process, they're automating it on behalf > of users. They've done everything but schedule it for their users. > >> One that is unlikely to be >> realised in my opinion for the simple reason that automated and >> therefore mostly unobserved security systems are a primary target >> for tampering. > > For someone who wants "evidence" you make a lot of unsupported > assertions. You do see the irony, don't you? The difference is that I state this is my opinion and I do not claim it as a fact. Your statement claimed a factual basis. I was naturally curious to see what evidence supported your claim. > >> Likewise the authors' opinion that pki certificates are in >> general just casually left laying around to be compromised displays >> a >> certain level of what reasonably could be considered elitist >> contempt >> for the average human's intelligence. > > Or, you know, a review of actual security problems in the real world. > >> Even as arguments I find these two positions are less than >> compelling. >> And in no respect could either opinion be considered evidence. > > That's fine. I don't really need to convince you, personally, of > anything. But for the security of the internet community in general, > I'll continue to advocate for secure practices, including pervasive > security (which means reducing barriers to the use of encryption at > all points along the process of setup). > > I know, and we put infants on no-fly lists for essentially the same religious beliefs. The benefit of so-called general security for the rest of us who do not have to bear its individual specific cost. The is no evidence that this sort of stuff works. It is just done so that if anything bad happens the authorities can claim that they did something preventative which they can point to. Regardless of how ineffectual it was. Automated security is BS. It has always been BS and it always will be BS. That is my OPINION. It may not be a fact for I lack empirical evidence to support it. However, it has long been my observation that when people place excessive trust in automation they are are eventually and inevitably betrayed by it. Often at enormous cost. Let me give you an example of stupidity in action with respect to signed certificates. I have a MacBookPro c. early 2009. There have been five or six major releases of OSX since then. Being a cautious type I download the upgrade installer apps and archive them before installing and upgrading. Over this past weekend my MB stopped booting. It would get to the Apple symbol and go black. Much trial, error, and research later I discover that this is sometimes occurs when a MB has been repeatedly upgraded and that a clean install is the recommended cure. Oh, by-the-way, if you ever have to do this then do not use the Apple Migration Assistant app when you are done. You will be sorry. So, I get out my archived Installer app, go to install it and BANG! My MB proclaims that "Somebody has tampered with the application or it is corrupted!". OH NO! This impediment however is strictly an artefact of signing code with short term certificates. I simply had to reset the date on my MB back to some future date when the certificate was valid and everything worked fine. Of course this took me a great deal of frustrating effort to discover what had happened to all of my archived copies and how to fix it. In the middle of a system recovery I might add. But hey, what is my time worth in comparison to the security those certificates provided? SECURITY that was trivially evaded in the end. Exactly what mindless person or committee of bike-shedders decided that software should be distributed so that copies of it expire? What security issue was addressed by this decision? What benefit to the public was achieved? When real people suffer real inconvenience and real loss of productive effort because of mindless adhesion to bromide based cures that are blandly offered for ills that mostly exist in the imagination of the ignorant then yes; I require evidence of their efficacy. And lining up a bunch of band-wagon pundits chanting the same vacuous refrains is not evidence. And this one is going to the list. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

4 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss