Discuss

discuss@lists.centos.org

34753 discussions

Re: [CentOS] Fedora change that will probably affect RHEL
by Scott Robbins 31 Jul '15

31 Jul '15

This might show up twice, I think I sent it from a bad address previously. If so, please accept my apologies. In Fedora 22, one developer (and only one) decided that if the password chosen during installation wasn't of sufficient strength, the install wouldn't continue. A bug was filed, and there was also a great deal of aggravation about it on the Fedora testing list. So, it was dropped. However, like a US (and probably other countries) politician who has one bad law suddenly exposed, it seems they are doing it for F23, judging from a test installation. I've filed a bug if anyone wants to chime in and ask them not to do it. https://bugzilla.redhat.com/show_bug.cgi?id=1246771 -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

18 77

Re: [CentOS] Fedora change that will probably affect RHEL
by James B. Byrne 31 Jul '15

31 Jul '15

On Thu, July 30, 2015 12:54, Chris Murphy wrote: > On Thu, Jul 30, 2015 at 9:54 AM, Valeri Galtsev > <galtsev(a)kicp.uchicago.edu> wrote: > >>> Now I use Google. They offer MFA opt in. And now I'm more secure >>> than I was with the myopic ISP. >> >> "More secure" only to the level one can trust google ;-) > > Yes I know, but I put them in approximately the same ballpark as > having to trust my proprietary CPU, and proprietary logic board's > proprietary firmware. So your motherboards and nics can 'call-home' on a regular basis and you would not mind if they did? There is, in my opinion, a fundamental difference between accepting the possibility of vendor installed trojans on hosts that may never be connected to an external network and adopting an infrastructure that depends upon such behaviour. Ones risk tolerance varies according to the perceived value of the asset to be protected. The problem that Google, Amazon, NSA, FSB, GCHQ, CCSE and the rest pose to the average person is that the average person has no idea of how to value pervasive recording of their private activities. Thus there is no basis upon which they may form a reasonable risk assessment. Therefore no reasonable estimation of the acceptable cost for prevention can be made. Consequently this promotes the prevalence of what amounts to folk-remedy security measures; virus scanners (most of dubious or no worth) mainly; master password protection schemes (that in many cases require you to reveal all of your passwords to third-parties); and of course consumer grade two-factor authentication schemes that just happen to require revelation of your private cell phone number to commercial enterprises. The common elements to all these are: low cost, dubious efficacy, hidden defects, and consumer ignorance. I have a router at home that 'talks' to both my ISP and its manufacturer on a regular basis, regardless of whether or not there is active traffic on the exceptional circuit. Which behaviour is why all of my home traffic, internal and external, goes via an ssh pipe established through a system placed in front of the router. But how many consumers, and keep in mind that my ISP is one of the largest telecoms in the world, would even dream that such things happen? Much less take steps to thwart that surveillance? Or even know what steps are possible? This sort of stuff should be out and out illegal. But, as the router is the 'property' of the telecom it is up to them what they wish to have it do and the consumer's choice it put up with that or do without. We are living in the golden age of snake-oil technology. Which, as the governments of the world have become addicted to surveillance of their subjects, -- one cannot really call citizens those so treated by their rulers -- is unlikely to change for a generation or more. It took more than 100 years of consumer activism to change advertising and product safety laws and these are yet far from perfect. I am not convinced that effective data security laws will prove any easier to establish. Or be accomplished any sooner. Which is why I consider discussion of password strength nothing more than a pointless diversion of attention from the real issues of data security and network integrity. A discussion that is truly representative of our 'security theatre' industry; being both expensive and irrelevant. In system design we call this stuff 'bike-shedding'. -- *** 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

2 1

CentOS-announce Digest, Vol 125, Issue 13
by centos-announce-request＠centos.org 31 Jul '15

31 Jul '15

1 0

centos6 and virtualbox audio problem
by FHDATA 30 Jul '15

30 Jul '15

hello, host: centos6 64bit (dell desktop) guest: windows 7 64bit virtualbox: 4.3.30 problem: host has audio but guest does not. i.e. when virtualbox comes up, it says: No audio devices could be opened. ErrorID: HostAudioNotResponding #lspci -nn | grep -i audio 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8 086:1c20] (rev 04) 01:00.1 Audio device [0403]: NVIDIA Corporation GF119 HDMI Audio Controller [10de:0e08] (rev a1) Pulse audio and Alsa installed on the host. trying these settings have not worked so far letting me have audio on the guest: Host Audio Driver: OSS,PULSE,ALSA Audio Controller: Intel HD I am not seeing any audio-related errors in virtualbox log. lot of time spent on this so far; any idea as what to do next will be greatly appreciated. thank you, F-

1 0

rsyslog.conf
by m.roth＠5-cent.us 30 Jul '15

30 Jul '15

I was looking at the manpage for rsyslog.conf, primarily because I need to filter my manager's new fedora 22 logs coming to our loghost, because of the bug that I forwarded (if it gets through). At any rate, I am surprised: under selectors, I see that " The keywords error, warn and panic are deprecated and should not be used anymore." Huh? If I only want warn or more severe, how am I supposed to filter - write a much more elaborate RE? mark

12 23

how to get bug fixed by TUV
by Stijn De Weirdt 30 Jul '15

30 Jul '15

hi all, i have a general question (a bit surprised ti's not on the centos faq): we found a bug in a package in a centos install, and we are wondering what the best approach is to get TUV to fix it (and release an update), so it gets fixed in centos rebuild and thus on our nodes. or at the very least to get it on their todo list ;) bugs.centos.org seems an obvious candidate to get them reported via centos to TUV, but as centos doesn't modify the sources, i'm wondering if it is the correct way. so is there a way to funnel these through bugs.centos.org to TUV, or should we get our own (minimal?) support contract with RedHat. if it's the latter, any tips what contract to choose? (money isn't really the issue if we don't have to register all our centos nodes (and i wouldn't mind having access to the KBs if that came with the contract ;)) stijn the bug is https://bugzilla.redhat.com/show_bug.cgi?id=1248003 (i consider it a bug and not a feature since it used to work with EL6, and people upgrading might run into this; but i guess it's all semantics ;)

3 4

Last few days in CentOS
by Karanbir Singh 30 Jul '15

30 Jul '15

hi everyone, I know this update has been a bit delayed, things have been pretty hectic. But lots of good updates for everyone: Distro -------- * Updates for CentOS Linux 5/7 : All updates from upstream are released into the CentOS mirror network. * Upstream 6.7 was released a few days back, we have all the rpms from that release built and released to the early-adopters into the CentOS-CR repos ( ref: http://wiki.centos.org/AdditionalResources/Repositories/CR ); lots of people have applied these updates and there are no major reports of issues so far. If you are one of the people running with CR, please let us know if you hit any issues. * Updates released to EL6 since 6.7 was released are also rolled into CR/ so if you are running this repo, you would be updated all the way. * We have a first cut of the ISOS for CentOS-6.7 ready and in QA, there are a couple of package changes, and we need to tweak the content that ends up on DVD1 Vs/ DVD2 to make sure we can still retain max installs from just DVD1. I aim to have these done and available to the QA folks in the next day or two, with the intention to release early next week to mirror.centos.org. * Another key piece that we've been working on is the AltArch SIG; The aim of this Special Interest Group is to help build and help maintain CentOS Linux on other architectures than what the Core group is able to do. Our first major build there is for the ARM 64bit platform called Aarch64. CentOS Linux 7 has been in beta there for a few weeks and is nearing the end of the beta term. If you have an ARM 64 bit platform, we would appreciate feedback on the distro. ref: http://lists.centos.org/pipermail/arm-dev/2015-July/000309.html -------- Other: * the SCL sig has been making great progress, we now have their use cases fully supported in cbs.centos.org; Honza posted an update recently on their status for the devtools-3 effort at : http://lists.centos.org/pipermail/centos-devel/2015-July/013682.html * Some of our GSoC Students have been blogging at http://seven.centos.org about their projects and the great work they are doing in their areas. Its worth a read through. -------- Tip: there are some great installation tips and tricks on the wiki at http://wiki.centos.org/TipsAndTricks/KickStart - and we maintain a collection of community contributed kickstarts at https://github.com/CentOS/Community-Kickstarts - its a great resource to get ideas for your own kickstarts, and also a fantastic place, with a low barrier for people to contribute their own tips and kickstarts! -------- Engage: As some of you might already know, I've been running office hours every Wed at 16:00 UTC and every Thu at 08:30 UTC over in #centos-devel on irc.freenode.net; you also have the option to call me on the phone for a chat during these times. The last few weeks have been really fruitful, with many great conversations. If there is anything you want to talk about or have questions around the CentOS ecosystem, feel free to drop in. Office hours are run as a open house, free question and answer sessions. regards, -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

8 11

Re: [CentOS] Fedora change that will probably affect RHEL
by James B. Byrne 29 Jul '15

29 Jul '15

On Tue, July 28, 2015 19:46, Warren Young wrote: > > iPads canât be coopted into a botnet. The rules for iPad passwords > must necessarily be different than for CentOS. > http://www.tomsguide.com/us/ios-botnet-hacking,news-19253.html -- *** 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

2 1

Semi-OT: configuring mongodb for sharding
by m.roth＠5-cent.us 29 Jul '15

29 Jul '15

Anyone know about this? Googling, all I can find is mongodb's 3.x manual, nothing for the 2.4 we get from epel. What I need to do, CentOS 6.6, is start it as a service, not a user, and have it do sharding. I see examples of how to start it as a user... but I can't find if there's a syntax for /etc/mongodb.conf to tell it that, and I don't want to have to edit /etc/init.d/mongod.... Clues for the poor? mark

2 1

CentOS-announce Digest, Vol 125, Issue 12
by centos-announce-request＠centos.org 29 Jul '15

29 Jul '15

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://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:1513 Important CentOS 7 bind Security Update (Johnny Hughes) 2. CESA-2015:1515 Important CentOS 5 bind97 Security Update (Johnny Hughes) 3. CESA-2015:1514 Important CentOS 5 bind Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 29 Jul 2015 01:43:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1513 Important CentOS 7 bind Security Update Message-ID: <20150729014333.GA58191(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1513 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1513.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9c5c7ecb8477d65dbee21c713bc1682a186491a9b81885e5369fc85cf6db2ca1 bind-9.9.4-18.el7_1.3.x86_64.rpm 62eab23efa33dc6860cebfc4fa472778386c953783327068459cb832852aa470 bind-chroot-9.9.4-18.el7_1.3.x86_64.rpm 4d038f6059f4b05e0eef1d3e54ea0d30384e7184e484c7298c68de4d14a4ba34 bind-devel-9.9.4-18.el7_1.3.i686.rpm 3a6e11021ddadfecd3ae3ad6e44c9967655cbd03cbce5b3e81dec1894780bae6 bind-devel-9.9.4-18.el7_1.3.x86_64.rpm c373ece790e2529f3712cf6b949a50560811381d1275bd4a8a395a91f1533aec bind-libs-9.9.4-18.el7_1.3.i686.rpm 412969a1cf5a64b6e2b76f61fbd80e0b398710091cc5675c83294ec5ea60a1b9 bind-libs-9.9.4-18.el7_1.3.x86_64.rpm 5ca41fdbb73ea32acfcc9ee32ea8732090165d131970ea6cba1df926f1c3a207 bind-libs-lite-9.9.4-18.el7_1.3.i686.rpm 06fcfad4fe46cf5bb869aeeaf5d2aa39e1252ce2d98164eef25595883ee3741c bind-libs-lite-9.9.4-18.el7_1.3.x86_64.rpm b4bdecc323c44527ad29102062a902c61e0d49e19f90ec9a3a2c94e83cb33b7b bind-license-9.9.4-18.el7_1.3.noarch.rpm f3bc495f2f068075712f59bb446ff262771371b9729d946ed58e2d380655326b bind-lite-devel-9.9.4-18.el7_1.3.i686.rpm ba5e6f001722090f86e6d6f7c5f13a70aaa2fd83d494793da689324c2a7603d1 bind-lite-devel-9.9.4-18.el7_1.3.x86_64.rpm 091830f725b50163e503be86e4973ab95613b3cc9934a2151285305d79e3c4d0 bind-sdb-9.9.4-18.el7_1.3.x86_64.rpm 4b4bb1c576931457478a6f4864fd10c085ec5d612698650d029bb33a95919090 bind-sdb-chroot-9.9.4-18.el7_1.3.x86_64.rpm 0ec01671e720be4e5678b2ee2593668fe98d8b5db83215e94abc10b346bdd2c7 bind-utils-9.9.4-18.el7_1.3.x86_64.rpm Source: b0702c059ab0c337a06f36f078a2e036291bcb53fa53f6eea65a2bdc2c66b119 bind-9.9.4-18.el7_1.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 29 Jul 2015 02:03:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1515 Important CentOS 5 bind97 Security Update Message-ID: <20150729020350.GA25864(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1515 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1515.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 70be08407007ee373075a7f4c0e8f30f9ae9486cc6e86d758e145c7e0452fbba bind97-9.7.0-21.P2.el5_11.2.i386.rpm 4b4e40fca6cf07b64db40860a6b5c9102f4d1968d3996bd0cff8804a92273bce bind97-chroot-9.7.0-21.P2.el5_11.2.i386.rpm 2f4ca3bb619d4fb2a98e61d36b1a415a8f774da3ee48cdec5b36b3c2c4ae883e bind97-devel-9.7.0-21.P2.el5_11.2.i386.rpm 5e1cd26638a0ad32eb0e77c7bdff74283dc67eaf98d6b43883fecf1cbd8c1e8e bind97-libs-9.7.0-21.P2.el5_11.2.i386.rpm a3d8ecd851aeb1600abc328b35b48e1afaa6f64b3ac9bae46033e7cfc1db7353 bind97-utils-9.7.0-21.P2.el5_11.2.i386.rpm x86_64: b826b3406eec2980fb56649f18d0b5372589d49ede9656ea0a8fcca3634e3943 bind97-9.7.0-21.P2.el5_11.2.x86_64.rpm 6a39f618114777091a0a35f879465d6fb7365b253a53f8802d4cb328d70fffaa bind97-chroot-9.7.0-21.P2.el5_11.2.x86_64.rpm 2f4ca3bb619d4fb2a98e61d36b1a415a8f774da3ee48cdec5b36b3c2c4ae883e bind97-devel-9.7.0-21.P2.el5_11.2.i386.rpm 415af4cc884957116f9b7111dbe75a65bdfe60fb52d9c864cb2718b04bf8711c bind97-devel-9.7.0-21.P2.el5_11.2.x86_64.rpm 5e1cd26638a0ad32eb0e77c7bdff74283dc67eaf98d6b43883fecf1cbd8c1e8e bind97-libs-9.7.0-21.P2.el5_11.2.i386.rpm d8045281af26202376e42d47bed00998946e2005db418c114843da05b728bc05 bind97-libs-9.7.0-21.P2.el5_11.2.x86_64.rpm 93d966dcf44c39c8f07a3b46d74d46ae0cd57fa29d6ffab510fb0a5d1acbe7c8 bind97-utils-9.7.0-21.P2.el5_11.2.x86_64.rpm Source: baa5aa7d9bf6f235fdebe677c8e716c4495471bac02acec7f51b66ae7d20bdd0 bind97-9.7.0-21.P2.el5_11.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 29 Jul 2015 02:04:03 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1514 Important CentOS 5 bind Security Update Message-ID: <20150729020403.GA25901(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1514 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1514.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e94c5d303a687961e27faefb38542d43f85e8d50bfcb2eec97b29a4b401a7e94 bind-9.3.6-25.P1.el5_11.3.i386.rpm 2602a6619c15b9352753ca9a59f645ac19ec16eeb07c1186a1a48295b3dcba30 bind-chroot-9.3.6-25.P1.el5_11.3.i386.rpm e90145a4e6f3bcbac6fb566d92385361c212af5171a429ac09680bf20996a70f bind-devel-9.3.6-25.P1.el5_11.3.i386.rpm 67f04bc05d5ccb05e4c13f8b8fe4d65b1fc1b611c6d8510c85685235e2e07b4e bind-libbind-devel-9.3.6-25.P1.el5_11.3.i386.rpm ccf15a3e6dc0e09b007de214a97790d5d0f330994fc71a7fc31e61ab8959401a bind-libs-9.3.6-25.P1.el5_11.3.i386.rpm 5e964b2eeabebdcc277c67cb9c66ab948a1bab42ffa1709072672d0e31975c8e bind-sdb-9.3.6-25.P1.el5_11.3.i386.rpm 272cdaa8afedde309f4c056bf81bacd0040aba1ba9c6bd74b06c3447d19f5d79 bind-utils-9.3.6-25.P1.el5_11.3.i386.rpm 3a6ef4acad542497ad5dd4b9cf6f9a5f929f201c5da4ef0ea8edf08f36a42491 caching-nameserver-9.3.6-25.P1.el5_11.3.i386.rpm x86_64: 121cd9c943ab2f9a2e2e3e9085df43ea552e62c31d2160f390a41779645ddf3c bind-9.3.6-25.P1.el5_11.3.x86_64.rpm 60939ff13f60f6bfe4e0fcfe176573c88b659b12b42755d389f5cc4b6ddcf7d2 bind-chroot-9.3.6-25.P1.el5_11.3.x86_64.rpm e90145a4e6f3bcbac6fb566d92385361c212af5171a429ac09680bf20996a70f bind-devel-9.3.6-25.P1.el5_11.3.i386.rpm 93b096322b3b84c88f7d193dd600098f5571e1257532d49fa27dfcc8a6488973 bind-devel-9.3.6-25.P1.el5_11.3.x86_64.rpm 67f04bc05d5ccb05e4c13f8b8fe4d65b1fc1b611c6d8510c85685235e2e07b4e bind-libbind-devel-9.3.6-25.P1.el5_11.3.i386.rpm c99671bfe37a76a782e93e046f96983080327bc00d721c5e9d7808585f14f373 bind-libbind-devel-9.3.6-25.P1.el5_11.3.x86_64.rpm ccf15a3e6dc0e09b007de214a97790d5d0f330994fc71a7fc31e61ab8959401a bind-libs-9.3.6-25.P1.el5_11.3.i386.rpm 7cc7bb6a588e4ad88cfd7e230ae8b74d400e171d243b10bfbdb1106dd1773193 bind-libs-9.3.6-25.P1.el5_11.3.x86_64.rpm be171ab4bcd0022a9d84ff36b68e38d5fd91d9d64e65527e6c3752a4cffdc2e0 bind-sdb-9.3.6-25.P1.el5_11.3.x86_64.rpm a3ed13e15585701c1d9161d4e137d1492c740ef8601b9e9b1200cacf641c7830 bind-utils-9.3.6-25.P1.el5_11.3.x86_64.rpm 41ecfadef75c7f423f87e0fc32ee9ecb0f279db8167cbc16ffe985d17b3249eb caching-nameserver-9.3.6-25.P1.el5_11.3.x86_64.rpm Source: 07f2f7dda39914aeef316af6aa9e48ca450dba8b39393b210073f4482a42ec42 bind-9.3.6-25.P1.el5_11.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 125, Issue 12 ************************************************

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