Discuss

discuss@lists.centos.org

3 participants
34748 discussions

CentOS-announce Digest, Vol 129, Issue 9
by centos-announce-request＠centos.org 19 Nov '15

19 Nov '15

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-2015:2081 Moderate CentOS 6 postgresql Security Update (Johnny Hughes) 2. CESA-2015:2086 Important CentOS 6 java-1.6.0-openjdk Security Update (Johnny Hughes) 3. CESA-2015:2086 Important CentOS 5 java-1.6.0-openjdk Security Update (Johnny Hughes) 4. CESA-2015:2086 Important CentOS 7 java-1.6.0-openjdk Security Update (Johnny Hughes) 5. CESA-2015:2078 Moderate CentOS 7 postgresql Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 18 Nov 2015 19:45:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:2081 Moderate CentOS 6 postgresql Security Update Message-ID: <20151118194504.GA29856(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:2081 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2081.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0e97fe4a73fd3e52d253aa01a78d4a2c75e57415e62a2468dc8639352016e817 postgresql-8.4.20-4.el6_7.i686.rpm 54877c2fedcbdd30cc66941d449dc70077fc886fcac53e3d589e764452171354 postgresql-contrib-8.4.20-4.el6_7.i686.rpm 23992e58740882150065ac43e544b4f8aa53a942b9393e354faa7bf20411b4b4 postgresql-devel-8.4.20-4.el6_7.i686.rpm a4fc45d81815c93da5d5a3948eaba1f598937a0e6b80a7ced9de1958daa66158 postgresql-docs-8.4.20-4.el6_7.i686.rpm 217f335cc844426b53558859ae65f7e45b96e02ea2e3b267288f9404bbba9fd4 postgresql-libs-8.4.20-4.el6_7.i686.rpm 6e7534efb6c9eb1db98ec1e1e581a351cee2733f7d641decb390f6f60d448099 postgresql-plperl-8.4.20-4.el6_7.i686.rpm cc50decba345bf784b9821edb1c8f1921a708a4d9440f444ece54383c2bf005b postgresql-plpython-8.4.20-4.el6_7.i686.rpm b1d88b3f571a551d5438f3f397ecf79a1bbf45df822019160db4f22776e6a91e postgresql-pltcl-8.4.20-4.el6_7.i686.rpm 65e5d758024188f6ba096bc1c96754f45d6ce98944beddb9ecfa087dad9bf55f postgresql-server-8.4.20-4.el6_7.i686.rpm 9b4ddd7a4cf4ff7c24e91be92fa8062092e19672f3fb939817abd7d770eb9baa postgresql-test-8.4.20-4.el6_7.i686.rpm x86_64: 0e97fe4a73fd3e52d253aa01a78d4a2c75e57415e62a2468dc8639352016e817 postgresql-8.4.20-4.el6_7.i686.rpm 2cf6ecc14534ef1bb553da2743b1a2b7679ad6e076dd2301d241833c8288e02c postgresql-8.4.20-4.el6_7.x86_64.rpm 0cebe83b0f5f91d5055eec015539904d9d6c5c6e4a41848f0f39ddfebf54a082 postgresql-contrib-8.4.20-4.el6_7.x86_64.rpm 23992e58740882150065ac43e544b4f8aa53a942b9393e354faa7bf20411b4b4 postgresql-devel-8.4.20-4.el6_7.i686.rpm f02d225b9769f8a69c9a38bdc360e92b96d37b37db2c372ca020d597dea19dae postgresql-devel-8.4.20-4.el6_7.x86_64.rpm b001349770fb86984191de0d8a90d30d41dab95ca1467d8e31ef067cefd050b8 postgresql-docs-8.4.20-4.el6_7.x86_64.rpm 217f335cc844426b53558859ae65f7e45b96e02ea2e3b267288f9404bbba9fd4 postgresql-libs-8.4.20-4.el6_7.i686.rpm 252e3df351f8007191831d1c40b13e868811672d11c40a81fac17e3d213be926 postgresql-libs-8.4.20-4.el6_7.x86_64.rpm 54c0316956e115eb0c41c445a211675cff32f2628575765b368de7a735119350 postgresql-plperl-8.4.20-4.el6_7.x86_64.rpm 60e79f2a2d21dd3d8d8e1714ca063ecd5a2a302db824f9a735006c700bc351e7 postgresql-plpython-8.4.20-4.el6_7.x86_64.rpm ba395b85bb86749ddb58b1e43509412c684d0b18c7fe41052874073dafc926de postgresql-pltcl-8.4.20-4.el6_7.x86_64.rpm d189c260a6280f771eeed522750d4f7928fad095293fdd287f29b4dd2e8f6871 postgresql-server-8.4.20-4.el6_7.x86_64.rpm 77309a9e212b2f424990eae82510308ea036d9a40040162068be8b4f0a66a597 postgresql-test-8.4.20-4.el6_7.x86_64.rpm Source: b0eb57695234f5cc6f2ab2df3eef661726f065926a303cfa0278cc003ab24ed2 postgresql-8.4.20-4.el6_7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 18 Nov 2015 19:46:16 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:2086 Important CentOS 6 java-1.6.0-openjdk Security Update Message-ID: <20151118194616.GA30144(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:2086 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2086.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e8af0bccd304323e1aa843eb766e70c14e41f10d37f36a10a119a2e5a0a29d99 java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el6_7.i686.rpm 1d5d0435df46b38dd76625bf74d399130fc880d253cce65cc56af02ae95369f6 java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el6_7.i686.rpm a1fb61dd21d3c39e76dd4b586616a0eb9f0e7385f4ffc0646b64caab8e39e023 java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el6_7.i686.rpm e6ef8834495a00342c6795c6350e481121ec1679a11faf111974a8e1cfb513e9 java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el6_7.i686.rpm 8746d8d277b92216022f72bde731eb208376ef80189ff9b537b39818af6191a4 java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el6_7.i686.rpm x86_64: 5aa22726ce93be62ff0833e0ff0a2258dd44b36968f9787c106ce7abac9de92b java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm 5fa7345e069a5d00c0257e1559ec8fe97a2f828306d5538a22c773f800c07181 java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm ed681b21bbcb93543dffc3f82ed8bd93226ad1cdd640d4300c3656630664bce6 java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm c83158d7a0c733b44279ccb95a66a87c137441e1a47c55be94d057e667289a23 java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm a248aefa9bc1c02541ff465f6eb6f98a32072b6fef348adcdf924fd051d06151 java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm Source: 5d935ad8df489bd9c6dcf51e5fa0cdb2eda17face6eccce30cccf8fbfd0312f3 java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el6_7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 18 Nov 2015 19:58:09 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:2086 Important CentOS 5 java-1.6.0-openjdk Security Update Message-ID: <20151118195809.GA32688(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:2086 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2086.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: aa99f34b3c368695046b073a2065735f41b443f5014998662141472784808fc8 java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el5_11.i386.rpm 22a5e9945db46cbc09e28e944037f97e08ada786a29633fc0749c473bf27a75e java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el5_11.i386.rpm 1c74dc66b90779a55849b0f2857c99ed7c44d0e4071bfd0afec944d85df32e2b java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el5_11.i386.rpm 6fdbd6c9f8cf75a2e59755291275d4dd649ae80a723389495e5174eab93cdf20 java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el5_11.i386.rpm 9cb01c62fa3a3c13e33a88fe3e121d9e0509a3fe1aadf1b13a45067046eecf4e java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el5_11.i386.rpm x86_64: 647faf2b65173da2df9cb57b1fc4c55605474eb675b8695551d6ea51f695213c java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm 1e99cb89adbd0b8331adbef47eab6911df5fb042481c004dc9e55978c828acf0 java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm df9c09dc2debaf5315d92f63a2516ba59f1b1a21cf9b8c1817beaa3b76f2f700 java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm e85105b2fe6f41629828fcae5f78bc62bd3b4d4b3e41a27f06c333799c3e74cf java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm 3a46d303cfaff3b86d43d157a039181542895f45d109c77bd0f81540f69a75e0 java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm Source: 02ad1a69ec9a3b1832ec47ff1c4f13fcb54d45f55bf5d9907b6a582888b71bb8 java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el5_11.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 18 Nov 2015 20:38:46 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:2086 Important CentOS 7 java-1.6.0-openjdk Security Update Message-ID: <20151118203846.GA41120(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:2086 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2086.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: dbde32b3ea0f1870bd997de2978ae16c39b5702982e26641b1361e525d836a2a java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm 8c10f117b441e78024068c7d8aebdbe23ed46a772e739c2ec6c8fc5a9bd19300 java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm b9cc50e5cc098bd8cdec6d2c57ed9957b84b17140b20c4dff86116a321fb5743 java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm d7555996e4355cfd7f42227a7dcbc82760cb92dd0387c0e8943a62d58a96a85c java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm 242c990b1fb3bbbec7ae853077c9785752d1a11364241070004ed245a84fd564 java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm Source: 5ca8bb4d945891ee068baac317351d7a571cf7dbf8e28f94fb1b2e2679580aeb java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el7_1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Wed, 18 Nov 2015 20:39:01 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:2078 Moderate CentOS 7 postgresql Security Update Message-ID: <20151118203901.GA41237(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:2078 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2078.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: dac984ae0f6ec9bbb3fbf89ab18387c911ecd381d0d42502212090583a255fb0 postgresql-9.2.14-1.el7_1.i686.rpm 48c8a0de83c28f79cc1a85f1b6572560860563610721ee7700d7ada688d25b4e postgresql-9.2.14-1.el7_1.x86_64.rpm da0f25e0fa38d0fc93d6b3817797b67ed1f5130e49c91477b19f27bde73770f7 postgresql-contrib-9.2.14-1.el7_1.x86_64.rpm 4ff2972830681f8b3878fb465c3b0eb93e315645eb5f8d32d19f04b983f563a6 postgresql-devel-9.2.14-1.el7_1.i686.rpm eae197326a7ae78b9f633c718d0e7eb48f5ac3520fe5ff787ab07dfb9a23ab79 postgresql-devel-9.2.14-1.el7_1.x86_64.rpm efd8026ec5026a22471688e0c19b2a53657c8d9a3333770829dbc12234c46e1c postgresql-docs-9.2.14-1.el7_1.x86_64.rpm 3897ca7ab0e9ed9df4c81c3e15da0ba069b74bd59c2e9743755e3654d8b3b712 postgresql-libs-9.2.14-1.el7_1.i686.rpm 4a409cfde77bc7b14f18a152e896ad3290aef94355a8c9ee993e9075b05160e9 postgresql-libs-9.2.14-1.el7_1.x86_64.rpm 89f5050225e4bc4ca162822ed0bdd16a0cf34f0b70fd0b2b3422a5850d37556d postgresql-plperl-9.2.14-1.el7_1.x86_64.rpm 35868c84234ab8afe3fdc05b181463f2161e2785fe0f55d21ec5368eb556c7a6 postgresql-plpython-9.2.14-1.el7_1.x86_64.rpm 2598a7f5e6b3d9fa1354fd373c039d7eec38e980b60af005a0051096d5e845a6 postgresql-pltcl-9.2.14-1.el7_1.x86_64.rpm bd457b9b0838e97e8dc54e8d730ac75da3ab297623bebaae23ec249c9da32fb2 postgresql-server-9.2.14-1.el7_1.x86_64.rpm 59674923b6e61253f8442a75ad7b1b671af6d8f3d02fac54ee9d93402c357f0a postgresql-test-9.2.14-1.el7_1.x86_64.rpm 7e81ff716e88e95e0157c53a02d2050c4858cce6d8fd22ace50287f18c481789 postgresql-upgrade-9.2.14-1.el7_1.x86_64.rpm Source: 7e684cc6556afa15a60582354c7a110461946416b70332fe09bbb499bd6f0aec postgresql-9.2.14-1.el7_1.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 129, Issue 9 ***********************************************

1 0

Running Fedora under CentOS via systemd-nspawn?
by Matt Garman 18 Nov '15

18 Nov '15

tl;dr - Is anybody "running" a Fedora system via systemd-nspawn under CentOS? Long version: Before CentOS 7, I used chroot to create "lightweight containers" where I could cleanly add extra repos and/or software without the risk of "polluting" my main system (and potentially ending up in dependency hell). The primary driver for this was MythTV, which has dozens of deps that span multiple repos. Without "containing" the MythTV installation within a chroot environment, I would inevitably lead to conflicts when doing a yum update. When I upgraded to CentOS 7, I found out that systemd-nspawn is "chroot on steroids". After figuring it all out, I replicated my MythTV "container", and things were great. Now I have a need for a particular piece of software: HandBrake. I found this site[1] that packages it for both Fedora and CentOS. But the CentOS version is a little older, as the latest HandBrake requires gtk3. The latest version is available for Fedora however. So I thought, what if I could "run" Fedora under systemd-nspawn. Well, I definitely *can* do it. I copied the base Fedora filesystem layout off the Live CD, then booted into it via systemd-nspawn. I was able to add repos (including the one for HandBrake), and actually install then run the HandBrake GUI. So while this does work, I'm wondering if it's safe? I'm thinking that at least some of the Fedora tools assume that they are running under a proper Fedora kernel, whereas in my scheme, they are running under a CentOS kernel. I'm sure there have been changes to the kernel API between the CentOS kernel and the Fedora kernel. Am I risking system stability by doing this? Anyone have any thoughts or experience doing something like this, i.e. running "foreign" Linux distros under CentOS via systemd-nspawn? What if I tried to do this with Debian or Arch or Gentoo? [1] http://negativo17.org/handbrake/

2 2

Re: [CentOS] Intel SSD
by m.roth＠5-cent.us 18 Nov '15

18 Nov '15

Michael Hennebry wrote: > On Wed, 18 Nov 2015, Birta Levente wrote: > >> I have a supermicro server, motherboard is with C612 chipset and beside that with LSI3108 raid controller integrated.Two Intel SSD DC S3710 200GB. OS: Centos 7.1 up to date. >> >> My problem is that the Intel SSD Data Center Tool (ISDCT) does not recognize the SSD drives when they connected to the standard S-ATA ports on the motherboard, but through the LSI raid controller is working. >> >> Does somebody know what could be the problem? <snip> > Perhaps the tool looks for the string RHEL. > My recollection is that when IBM PC's were fairly new, > IBM used that trick with some of its software. > To work around that, some open source developers used the string "not > IBM".I think this was pre-internet, so google might not work. > > If it's worth the effort, you might make another "CentOS" distribution, but call it "not RHEL". > I'll add to that: it was only maybe three years ago that to get one of Dell's support tools (Dset, maybe) to run on one of our CentOS boxes was to edit /etc/redhat-release so that it had the RH info, instead of saying CentosOS release ... You might try that. > -- > Michael hennebry(a)web.cs.ndsu.NoDak.edu > "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." That's never going to work - where the hell do you find a virgin? mark

2 1

centos 7 and keychain
by Pete Stieber 18 Nov '15

18 Nov '15

Is there a centos recommended repository for centos 7 where I can obtain the keychain package? TIA, Pete

3 3

firewalld rule syntax
by Nick Bright 17 Nov '15

17 Nov '15

I'm still learning firewalld obviously, and I am having trouble groking the documentation to understand how to do this. I know I could do an iptables direct, but that doesn't seem like the "right" way to do it. What I'm trying to do is allow a specific service, only for a specific ip. Effectively, SNMP should be allowed form a specific IP address (the systems monitor). What would be the most correct way of doing this? Create a zone for the snmp, then add the associated interface to that zone? firewall-cmd --zone=monitoring --add-source=1.2.3.4/32 firewall-cmd --zone=monitoring --add-service=snmp firewall-cmd --zone=monitoring --add-interface=ens192 firewall-cmd --runtime-to-permanent Would this be an appropriate approach? Is it the 'most correct' way? -- ----------------------------------------------- - Nick Bright - - Vice President of Technology - - Valnet -=- We Connect You -=- - - Tel 888-332-1616 x 315 / Fax 620-331-0789 - - Web http://www.valnet.net/ - ----------------------------------------------- - Are your files safe? - - Valnet Vault - Secure Cloud Backup - - More information & 30 day free trial at - - http://www.valnet.net/services/valnet-vault - ----------------------------------------------- This email message and any attachments are intended solely for the use of the addressees hereof. This message and any attachments may contain information that is confidential, privileged and exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. If you have received this message in error, please promptly notify the sender by reply E-mail and immediately delete this message from your system.

3 4

Re: [CentOS] firewalld being stupid
by James B. Byrne 17 Nov '15

17 Nov '15

On Mon, November 16, 2015 16:39, Nick Bright wrote: > On 11/6/2015 3:58 PM, James Hogarth wrote: >> I have a couple of relevant articles you may be interested in ... >> >> On assigning the zone via NM: >> https://www.hogarthuk.com/?q=node/8 >> >> Look down to the "Specifying a particular firewall zone" bit ... >> remember that if you edit the files rather than using nmcli you must >> reload NM (or do nmcli reload) for that to take effect. >> >> If you specify a zone in NM then this will override the firewalld >> configuration if the zone is specified there. >> >> Here's some firewalld stuff: >> https://www.hogarthuk.com/?q=node/9 >> >> Don't forget that if you use --permanent on a command you need to do >> a >> reload for it to read the config from disk and apply it. > Thanks for the articles, they're informative. > > Here's what's really irritating me though. > > firewall-cmd --zone=internal --change-interface=ens224 --permanent > > ^^ This command results in NO ACTION TAKEN. The zone IS NOT CHANGED. > > firewall-cmd --zone=internal --change-interface=ens224 > > This command results in the zone of ens224 being changed to internal, > as > desired. Of course, this is not permanent. > > As such, firewall-cmd --reload (or a reboot, ect) will revert to the > public zone. To save the change, one must execute firewall-cmd > --runtime-to-permanent. > > This is very frustrating, and not obvious. If --permanent doesn't work > for a command, then it should give an error - not silently fail > without doing anything! > This behaviour is congruent with SELinux. One utility adjusts the permanent configuration, the one that will be applied at startup. Another changes the current running environment without altering the startup config. From a sysadmin point of view this is desirable since changes to a running system are often performed for empirical testing. Leaving ephemeral state changes permanently fixed in the startup config could, and almost certainly would eventually, lead to serious problem during a reboot. Likewise, immediately introducing a state change to a running system when reconfiguring system startup options is just begging for an operations incident report. It may not be intuitive to some but it is certainly the logical way of handling this. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via 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

7 8

firewalld being stupid
by Nick Bright 17 Nov '15

17 Nov '15

Greetings, One of my biggest frustrations with CentOS 7 has been firewalld. Essentially all of the documentation just flat doesn't work. One common thing that needs to be done is to change the zone of an interface, however I've tried: firewall-cmd --permanent --zone=internal --change-interface=ens192 firewall-cmd --permanent --zone=internal --add-interface=ens192 I've also tried setting in /etc/sysconfig/network-scripts/ifcfg-ens192: ZONE=internal ZONE="internal" No matter what, when firewalld starts, ens192 will be in the public zone. What am I doing wrong? Why does the documented command structure not work? -- ----------------------------------------------- - Nick Bright - - Vice President of Technology - - Valnet -=- We Connect You -=- - - Tel 888-332-1616 x 315 / Fax 620-331-0789 - - Web http://www.valnet.net/ - ----------------------------------------------- - Are your files safe? - - Valnet Vault - Secure Cloud Backup - - More information & 30 day free trial at - - http://www.valnet.net/services/valnet-vault - ----------------------------------------------- This email message and any attachments are intended solely for the use of the addressees hereof. This message and any attachments may contain information that is confidential, privileged and exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. If you have received this message in error, please promptly notify the sender by reply E-mail and immediately delete this message from your system.

8 9

CentOS-SCL python version
by Noam Bernstein 17 Nov '15

17 Nov '15

Hi - I’d like to use the CentOS-SCL python27 packages, but those appear to be rather out of date, still on 2.7.5. Is there any chance that there will be an update in the 2.7 track, to 2.7.10? thanks, Noam ----------------------------------------------------------- Noam Bernstein Center for Materials Physics and Technology Naval Research Laboratory Code 6390 noam.bernstein(a)nrl.navy.mil phone: 202 404 8628

2 2

Problems with CentOS Advisory from August 2014
by Ian Stirling 17 Nov '15

17 Nov '15

Regarding this announcement [CentOS-announce] CESA-2014:1008 Important CentOS 6 samba Security Update *Johnny Hughes* johnny at centos.org <mailto:centos-announce%40centos.org?Subject=Re:%20%5BCentOS-announce%5D%20CESA-2014%3A1008%20Important%20CentOS%206%20samba%20Security%0A%09Update&In-Reply-To=%3C20140805200929.GA57368%40n04.lon1.karan.org%3E> /Tue Aug 5 20:09:29 UTC 2014/ Talks about this upstream Redhat problem - https://rhn.redhat.com/errata/RHSA-2014-1008.html When you read that errata it talks about RHEL 7 and in fact the filesets mentioned in the CentOS announcement are for CentOS 7 which leaves us in a state of a CentOS 6 system trying to install CentOS 7 filesets (some examples) x86_64: 157af858bf13ec971678a8bf3fc6cb649d577e671edadf3c860723a87c736eab libsmbclient-4.1.1-37.*el7*_0.i686.rpm 90ea2064837184635e7d718b854ced1482b78514c35b26a75125242b342316c8 libsmbclient-4.1.1-37.*el7*_0.x86_64.rpm 8a02b8e75489ae6972d2dce9cdc641c303903e772913421ad5a0d18ba9b84ecc libsmbclient-devel-4.1.1-37.el7_0.i686.rpm 7fd666c9b7e9fcae08cfe87a1061de6f6bc70c1fe6f9e3b276e08281faaa74db libsmbclient-devel-4.1.1-37.el7_0.x86_64.rpm 6d227ef56d9c743db3ef6ca280232c92a7eac8b7ce831dd97d15eb34b4e456fc libwbclient-4.1.1-37.el7_0.i686.rpm 3b1c4905362c5bded2e3a6b700447adfa16c557a1bed8be96595598ff55f82a1 libwbclient-4.1.1-37.el7_0.x86_64.rpm -- Regards Ian

1 0

CentOS-announce Digest, Vol 129, Issue 8
by centos-announce-request＠centos.org 17 Nov '15

17 Nov '15

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss