Discuss

discuss@lists.centos.org

34758 discussions

Start a nNew thread

CentOS-announce Digest, Vol 117, Issue 8
by centos-announce-request＠centos.org 14 Nov '14

14 Nov '14

1 0

Slow access from Windows 7 to samba share on CentOS 6.6 after upgrade
by Sorin Srbu 14 Nov '14

14 Nov '14

Hi all, Did anybody notice a really slow access from Windows 7 (especially from the MS Office suite) when trying to open a Word-doc for example, that sits on a samba share on a computer recently upgraded to CentOS 6.6? It can take up to two-three minutes to open a 20 kB Word-doc... I tested with the latest available LibreOffice for Windows on the same Word-docs, but this one doesn't show this sluggishness. Also opening PDF-documents on the samba share with Adobe Reader from Win7 gives this problem. Opening e.g. jpegs and regular plain text files with Irfanview and Notepad++ respectively is just fine. Pre-CentOS 6.6 opening any file on the samba share from Windows was lightning-fast. I'm not too sure where to start trouble-shooting. I've tried disabling the TCP autotune on Windows for starters, which a small improvement, but what next? Hints would be appreciated. Thanks. -- BW, Sorin ----------------------------------------------------------- # Sorin Srbu, Sysadmin # Uppsala University # Dept of Medicinal Chemistry # Div of Org Pharm Chem # Box 574 # SE-75123 Uppsala # Sweden # # Phone: +46 (0)18-4714482 # Visit: BMC, Husargatan 3, D5:512b # Web: http://www.orgfarm.uu.se ----------------------------------------------------------- # () ASCII ribbon campaign - Against html E-mail # /\ # # This message was not sent from an iProduct! # # MotD follows: # If it jams, force it. If it breaks, it needed replacing anyway.

2 1

Re: [CentOS] Not To James B. Byrne
by James B. Byrne 13 Nov '14

13 Nov '14

On Wed, November 12, 2014 15:50, g wrote: > > > On 11/12/2014 10:13 AM, Les Mikesell wrote: > >> >> Well, no. Per the headers: >> >> Authentication-Results: mx.google.com; spf=neutral (google.com: >> centos-bounces(a)centos.org does not designate permitted sender hosts) >> smtp.mail=centos-bounces(a)centos.org; dkim=neutral (body hash did not >> verify) header.i=@; dmarc=fail (p=QUARANTINE dis=NONE) >> header.from=harte-lyne.ca >> >> The p=quarantine setting from his server explicitly requests that >> the message be marked as spam if it s not sent from an authorized >> server, which don't include the centos list server. So it is accepted >> and dropped in the spam folder as requested. >> >> And at the moment, he is the only list member that posts regularly >> from a server with this setting. (We don't even see ones with >> p=reject, they'll bounce and get kicked off the list). > > Les, > > i believe problems are on your end, and not with server for James. > > i do not see "dmarc=fail" or "p=QUARANTINE" in *any* of his email > headers. > > therefore, i suggest that it is problem that _you_need_to_correct_. > The problem is not within the span of control of anyone receiving this message from the CentOS mailing list. Les is not in a position to deal with this issue any better than he already has. The people that are receiving my messages marked as spam are seeing the result of our DMARC disposition setting of quarantine. That simply tells conforming MX servers to mark the message as suspect and so allow the recipient to deal with it. And that is the proper thing for Google to do in our case. Messages coming from harte-lyne.ca certainly did not originate from centos.org notwithstanding that is who is transmitting them. And we are telling Google that messages from harte-lyne.ca should only be received from our authorized mails servers, which is perfectly correct. Google's course of action thereby leaves it in the hands of the recipient to manage what that fact means to them. It tells them that this message is routed in some unusual way and that it may be forged. That is important to know before one opens a message purporting to originate from a trusted source. As someone else pointed out, there is a philosophical question respecting who is the originator of any message that travels through a distribution list. And it remains unresolved. If the CentOS mailing list set the sender and from headers of all traffic routed through it to itself then the problems you are seeing with my messages would simply disappear. Because I would no longer be considered the originator. Something to that effect is what the changes to Mailman-2.1.18 enable while retaining or setting the Reply-To header to the original author's email address. I am not sure of the details. The retention of the originator's identity on mailing list mail is somewhat inconsistent with the premise that whoever transmits a message is the originator regardless of whoever wrote it. One can see premise that in the typical action of forwarding email from inside your MUA. The sender becomes the person forwarding the message, not the original author. One also must consider that when one subscribes to a digest of mailing list traffic, as I do to avoid the problems of identity that others experience, then the sender and the from are always the list itself as it technically impossible to have all of the the contributors designated as the Sender. It is therefore a valid question to ask how it comes to be that a collection of messages sent one at a time for a given source differs in origin than one sent as a single message from the same source? DMARC is all about forgery and is a response, albeit in my opinion a poor one, to the limitation found in most MUAs that only display the FROM header regardless of the Sender. Yahoo is draconian about this because, having had their client's email accounts compromised through a security lapse on their part, vast numbers of forged messages were sent to people with yahoo.com accounts who lacked the technical sophistication to detect the fraud. I apologise for the length of this reply. DMARC is not a simple subject to discuss. The topic of email identity is highly politicized and technical approaches to the question have already baffled some of the finest minds on the IETF. I doubt greatly that anyone here can propose any solution that has not already been considered and rejected for either political or technical reasons. -- *** E-Mail is NOT a SECURE channel *** 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-announce Digest, Vol 117, Issue 7
by centos-announce-request＠centos.org 13 Nov '14

13 Nov '14

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. CEBA-2014:1849 CentOS 6 perl BugFix Update (Johnny Hughes) 2. CESA-2014:1846 Moderate CentOS 7 gnutls Security Update (Johnny Hughes) 3. CEBA-2014:1850 CentOS 7 virt-who BugFix Update (Johnny Hughes) 4. CESA-2014:1826 Moderate CentOS 7 libvncserver Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 12 Nov 2014 10:38:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2014:1849 CentOS 6 perl BugFix Update Message-ID: <20141112103847.GA45032(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:1849 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1849.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 27aa56cf4d02f89172372b080b41950929dfd4122cae2ab38b5fe2572ddae5f7 perl-5.10.1-136.el6_6.1.i686.rpm 83777a0a728bc040f051817c61b4d62bdf181f1714c538e067af9b393495af6d perl-Archive-Extract-0.38-136.el6_6.1.i686.rpm 05accee109d027a5f496e85ea9bef509152998056ba65d345329d5606c2914aa perl-Archive-Tar-1.58-136.el6_6.1.i686.rpm 66ff0511347b25edc22e9749e22f0244d5fbbd04643ee568359432b2012e5dfb perl-CGI-3.51-136.el6_6.1.i686.rpm 49e65ccf00dae5312da4f423e67b0ee75ffbfec57b7c1e3c49629b43e94934cc perl-Compress-Raw-Bzip2-2.021-136.el6_6.1.i686.rpm a0fdf51548a16560381bd483903f37c891694b37ba2d2a561fa7ade09159bc18 perl-Compress-Raw-Zlib-2.021-136.el6_6.1.i686.rpm cc036519e57a5877b7f1103662debdd4722f9a77f996beddba49aa03978d8914 perl-Compress-Zlib-2.021-136.el6_6.1.i686.rpm 5217ed59d313169d723b2c087d59dacab220f17ff6bce037809ecced5222a979 perl-core-5.10.1-136.el6_6.1.i686.rpm 2151d6df58fabdea9c2ebc5b9e5778ed906cc3fa9a2a63357f95d9b2e60d453d perl-CPAN-1.9402-136.el6_6.1.i686.rpm 4e02c23533b55018a4f07de0b910f357005e34c73b19667a379712d261983161 perl-CPANPLUS-0.88-136.el6_6.1.i686.rpm 3d27d19ef1670b51db8de1a94a6e47b4b1d6091b60001141ebb1b6cb10ea6133 perl-devel-5.10.1-136.el6_6.1.i686.rpm 57559c293b8aa997bea6138e41d4c78f80c50b3970d3d9e4e31c1cf64024b077 perl-Digest-SHA-5.47-136.el6_6.1.i686.rpm 31427e7e9fa933ea6b5acc6e7f72e844c1496ab31feda7c186e8210e07714a41 perl-ExtUtils-CBuilder-0.27-136.el6_6.1.i686.rpm cc6bb53dcdaf5c709de7dd6c19c18edb1b1a284bf582d27a8b1c1a937abb8dff perl-ExtUtils-Embed-1.28-136.el6_6.1.i686.rpm bf63fa6278c3200cd558ca95fbd2b2162dff888eb16853c0a70488c4d9008c01 perl-ExtUtils-MakeMaker-6.55-136.el6_6.1.i686.rpm 286fd4bf83aa66102a304d701426dc4e3fada3cbb6772754c918a4eb3813a08e perl-ExtUtils-ParseXS-2.2003.0-136.el6_6.1.i686.rpm 69e5010c52ba1e1ef43aa15273bd57191d5343ba69db994b2c61032040ecd206 perl-File-Fetch-0.26-136.el6_6.1.i686.rpm 027aba00cc0fe75eba6c6e3ead9bb159b4a4bffca895dc4a270713545f80967c perl-IO-Compress-Base-2.021-136.el6_6.1.i686.rpm 797446e5205087faeea5bdfea7991a61264b3bc9b172305d0d15eed3230618d9 perl-IO-Compress-Bzip2-2.021-136.el6_6.1.i686.rpm eeb71513d9d213bc5fa99ac33fa00deaca80bb60a2f1bb837c90bcccac2016f7 perl-IO-Compress-Zlib-2.021-136.el6_6.1.i686.rpm 00f7cade8fc2619be052bf82872751eed0e9257e5f5b3d42a53dc6e462cfdd33 perl-IO-Zlib-1.09-136.el6_6.1.i686.rpm 8695330250409e398657776427a8c66f3e214e890071bd8f2d018fff74418d04 perl-IPC-Cmd-0.56-136.el6_6.1.i686.rpm 5be74897ee1307c5ce21d51b689fd7a740a2eadc8e3f4bcb712748a554e09e1b perl-libs-5.10.1-136.el6_6.1.i686.rpm a3245c4c403ea36fd736c80a9e64c373318de7a77a2a046c65a7b77f3a5e7f49 perl-Locale-Maketext-Simple-0.18-136.el6_6.1.i686.rpm adf8f31726566b8ba9edb5df9df4ca1db5412239a3eec75100e180d61112b15a perl-Log-Message-0.02-136.el6_6.1.i686.rpm 0dce4e0664dfd1861d1fc3ef3f81e0da0afd75e95e5caa44c216e984c54e9622 perl-Log-Message-Simple-0.04-136.el6_6.1.i686.rpm 81502512b3ee58aa300588f337c9fec0ea4173f5b169582f763fb9093fae9f88 perl-Module-Build-0.3500-136.el6_6.1.i686.rpm ef7a821e27704b2e7821dff0f0472660a1fd534f37ee13883bfa43f63667f92d perl-Module-CoreList-2.18-136.el6_6.1.i686.rpm 1815b922300dccf575b5c54f23f848d8594a132f143f35bbe2d6552464a67248 perl-Module-Load-0.16-136.el6_6.1.i686.rpm cf6b9d29796acf3096763ffaf4966680487f27c0df3ef76156b3152ad70db9e0 perl-Module-Load-Conditional-0.30-136.el6_6.1.i686.rpm 2fb53ff273369c233995de86ef42711aa58ea7fdfbaba3069db179a8ab687051 perl-Module-Loaded-0.02-136.el6_6.1.i686.rpm 2f26a2ef76e40e3580b2e90a5700262f28ad2e3a94c8b32db8f520cee324fdab perl-Module-Pluggable-3.90-136.el6_6.1.i686.rpm d25d3f0ef82f4a6a239be78593cfc5c3cd65a37aca253be7b3b0d20f363eadf6 perl-Object-Accessor-0.34-136.el6_6.1.i686.rpm 98599a64ad6ee0ea0e4f044c81c72d300746beab4351c823f314ec8a28a709e0 perl-Package-Constants-0.02-136.el6_6.1.i686.rpm b946dc37c227d8784fe4d14b259fdf10ecb520c41590fb589223e6fb123bd149 perl-Params-Check-0.26-136.el6_6.1.i686.rpm d8748ed65452b39d165677f9a837f16ad5609628019bec42025fee8773b172d1 perl-parent-0.221-136.el6_6.1.i686.rpm b2bb7f0d6fd40d4e1cc187a8e2bcc1d521bbcb7cc1b6ae42309ea6817fd526c7 perl-Parse-CPAN-Meta-1.40-136.el6_6.1.i686.rpm 92208914c367f0bcc84abacdfe8a4db2529afffdd2cde7af6c067ced5e0af772 perl-Pod-Escapes-1.04-136.el6_6.1.i686.rpm d0398cf96ab267d1ba8dc4e8ad71b5d10f27ee69de97f2195806417b9a1b0177 perl-Pod-Simple-3.13-136.el6_6.1.i686.rpm c2d7bb29c0911d377c1bb5e6637f5f56a9a163fce8a0c5827fb80baf0a6de2b5 perl-suidperl-5.10.1-136.el6_6.1.i686.rpm 507c50e553fb6ea170d8b0bc7a467f1feca9405c9d4071567632bf1a8dfe30b8 perl-Term-UI-0.20-136.el6_6.1.i686.rpm e3bd4e7edfd6d5d9f13f0669bdadd187e8d36de749eb96862dfa188ee47dcf90 perl-Test-Harness-3.17-136.el6_6.1.i686.rpm a942f40ede499e84a50eab5a22ce82a4cff9ec2bf6262b09704a7728604eadd4 perl-Test-Simple-0.92-136.el6_6.1.i686.rpm a650e7c98feb6f6ff8faa5bfceeae3c5855a9317e62e4af7d1e66b77a2bfebec perl-Time-HiRes-1.9721-136.el6_6.1.i686.rpm c36b4d3511e787581b5d2a7428987e287ae80546cc18e04c84d21c6945251eb6 perl-Time-Piece-1.15-136.el6_6.1.i686.rpm 7f5e5160d9114a66578a3cf37b0e2cf5f25394dfa3918cc678dcead1553d1b28 perl-version-0.77-136.el6_6.1.i686.rpm x86_64: 928157e20970588f7247bf6d2dbcd4b746f76c20fa42fb39f3a8a2bbc6ad40fa perl-5.10.1-136.el6_6.1.x86_64.rpm 483bc4b570b1afec57564d3670bff86e32280bb30aaa8559c3776e8e736a6c9c perl-Archive-Extract-0.38-136.el6_6.1.x86_64.rpm 4528fc7a55b631f628868eabf63282b820a6ed2d49c5a11d22e27bfc78b52c81 perl-Archive-Tar-1.58-136.el6_6.1.x86_64.rpm 665300c23395cb484dfb6a0267bd881253f8e3eb14d2f545273064aa40a6168f perl-CGI-3.51-136.el6_6.1.x86_64.rpm 9b708105476ff03203c22de1c64335d9e47bcf97f33a30706a4856bd6c270bff perl-Compress-Raw-Bzip2-2.021-136.el6_6.1.x86_64.rpm 97a9561912ab341a00f5d98fb38942caea2ebe1d01bead884889e32c0c3d841b perl-Compress-Raw-Zlib-2.021-136.el6_6.1.x86_64.rpm d21bf52a4c417333fcf116b4779a46c697c07b5e9554f37bbd9f78fffecc7edf perl-Compress-Zlib-2.021-136.el6_6.1.x86_64.rpm ef4c7110aed43a918559f044191ae8c17400a3cc79c5bf8da00e4f11b729dcad perl-core-5.10.1-136.el6_6.1.x86_64.rpm 5cf3892d8aff19b4bb532d83e12f3ce7ad198429a045e1f9b6e72519245a8a54 perl-CPAN-1.9402-136.el6_6.1.x86_64.rpm 20bb3ab8947b6b97dfaffc1f21cee10fe8725b017d931d05006f2d59144a7cdc perl-CPANPLUS-0.88-136.el6_6.1.x86_64.rpm 3d27d19ef1670b51db8de1a94a6e47b4b1d6091b60001141ebb1b6cb10ea6133 perl-devel-5.10.1-136.el6_6.1.i686.rpm e45c5cf770d30c089968019d6d6eb641b99fd76296a9f7e41aaf7a0cabce9c0b perl-devel-5.10.1-136.el6_6.1.x86_64.rpm a0560847d7301983daa4e68bbb0a9347a794fd4ef9c8a75a65fe6b74e420e812 perl-Digest-SHA-5.47-136.el6_6.1.x86_64.rpm 86ec6bdf61be970ba8f7e43b1a49f75079ec607192908f7931400bcba1f5ff67 perl-ExtUtils-CBuilder-0.27-136.el6_6.1.x86_64.rpm 8bce696f4261a7142f0de0041d9e68455911574abb42e7e72da3b04833f8acf4 perl-ExtUtils-Embed-1.28-136.el6_6.1.x86_64.rpm f671b3678e5eca8bb29401aedbfa764373cc3e50abfc5660a5e1e935fd20c549 perl-ExtUtils-MakeMaker-6.55-136.el6_6.1.x86_64.rpm 7229c105cdea871892c4a4a88add268dc71810b82ac091f7b8e836c14dad7776 perl-ExtUtils-ParseXS-2.2003.0-136.el6_6.1.x86_64.rpm 0601b303e9d6913579c8346437c8e61d7862a64968eca769140519d79b2f076f perl-File-Fetch-0.26-136.el6_6.1.x86_64.rpm 5020e12f2ec6ae36e701c5d9dc7c8042ea29cbdb92b7b2b6a210c96d25de0933 perl-IO-Compress-Base-2.021-136.el6_6.1.x86_64.rpm 539bc5f9a636ac4cf677a12102c9620f4bf003e0141ba380819cc984d73e4648 perl-IO-Compress-Bzip2-2.021-136.el6_6.1.x86_64.rpm 40dc995b7e3ab6f9ed166bae621ce68821942da462d9beb1526494d5f3993387 perl-IO-Compress-Zlib-2.021-136.el6_6.1.x86_64.rpm ad81f84422419e4cce158dc5f54988cfba5fc6130b4ae3d09a5963d5507e244e perl-IO-Zlib-1.09-136.el6_6.1.x86_64.rpm 4f9610749d363a40ffc5bcb28ed2c570aaff3358df6ef9608032c5664434fb1d perl-IPC-Cmd-0.56-136.el6_6.1.x86_64.rpm 5be74897ee1307c5ce21d51b689fd7a740a2eadc8e3f4bcb712748a554e09e1b perl-libs-5.10.1-136.el6_6.1.i686.rpm 0227749ca1ee84d6628ae6a4718c4d0340d707dc9e667c711d8253e2904de63b perl-libs-5.10.1-136.el6_6.1.x86_64.rpm 35067ed4c8ee054ba6407dcbc902b625f8b0eb3121ab24227673c1f8dd30a66c perl-Locale-Maketext-Simple-0.18-136.el6_6.1.x86_64.rpm f8c9edc89974fe828fda0df455b96af9842e2186d85b6f03bf6d76a891e58b1c perl-Log-Message-0.02-136.el6_6.1.x86_64.rpm d59764bc8cf1e149bc59f472fa279132f455e84812deb0c0628a59d5e3b3018e perl-Log-Message-Simple-0.04-136.el6_6.1.x86_64.rpm 867903280e33a5437a660d8df7f0604bfb9584041ebc28e258e68aab0afb4dc4 perl-Module-Build-0.3500-136.el6_6.1.x86_64.rpm fecdda7a2b75f5f45abf40f940b37615dd5d2b7cd58b1a1f3dce7fb3d53f9440 perl-Module-CoreList-2.18-136.el6_6.1.x86_64.rpm 4239948f58081df8df8562bf4b88ade02b58296c3c6728ea51df3745c6d6735a perl-Module-Load-0.16-136.el6_6.1.x86_64.rpm d3120fdb6e5fe332a0160e5bc50f2533aa13cf354a0a3c5a4b0b505f2c74c0c5 perl-Module-Load-Conditional-0.30-136.el6_6.1.x86_64.rpm 36b120312ac339e87c3b545e51c268667f3cbdb06c50189a5c3247d0af075c50 perl-Module-Loaded-0.02-136.el6_6.1.x86_64.rpm 105dc1d98274a56be2133c8b9405cd8f982b5157816abec24888ab1f16d4064e perl-Module-Pluggable-3.90-136.el6_6.1.x86_64.rpm ef04b2142e897a7a3830698f3eaecec2ae1d61679757abcb139bc45d2f654d05 perl-Object-Accessor-0.34-136.el6_6.1.x86_64.rpm 9c9f26e5b605dbba2a4bee3624945613da8a5af380557f7852d4fb104a32cc98 perl-Package-Constants-0.02-136.el6_6.1.x86_64.rpm e77085f1fd747e10b2d37476f548ac0d2f85851d24aaf71edd04665851d7412f perl-Params-Check-0.26-136.el6_6.1.x86_64.rpm aafda3ddb512ba51c7f4e440b6bb20ad58490755a135f9f57a49bd0bc1b2023e perl-parent-0.221-136.el6_6.1.x86_64.rpm 96be333e8f0205e8ad31155dad308db33704d0cdb0631f82abc8da111bad1dd3 perl-Parse-CPAN-Meta-1.40-136.el6_6.1.x86_64.rpm 2f19a8b570ed3bf3bb4734bdf0e2fc729429309b7fbfb68277a50ef2b91a5742 perl-Pod-Escapes-1.04-136.el6_6.1.x86_64.rpm f93af578e4da9f6255b00d5496555863756a329a0ccb3862ca75ea467b79a894 perl-Pod-Simple-3.13-136.el6_6.1.x86_64.rpm 5be559b743e879bd6683cc844194c0ffdbedcecaff29c58a25afd27c9b1b0471 perl-suidperl-5.10.1-136.el6_6.1.x86_64.rpm 075ba46583a6243ac1bfced8f9da7ac924ae8af4371e5abb1853068961de4dba perl-Term-UI-0.20-136.el6_6.1.x86_64.rpm ada0766e9fd100afc2529024cb1d8af9196269fa8cc0bd04bf98520835a1e6a0 perl-Test-Harness-3.17-136.el6_6.1.x86_64.rpm f416273667a466f072c455be99d09040af432598c57fb5ab4a6e806d6ceeab55 perl-Test-Simple-0.92-136.el6_6.1.x86_64.rpm b06f4e78322657195173bc49ab2852ff95ebf98661f7228d817cf1af40baa877 perl-Time-HiRes-1.9721-136.el6_6.1.x86_64.rpm bc503c12a6ad6317de3ee4464cd81a6081679c8c53aa2b30ef624bc037feec73 perl-Time-Piece-1.15-136.el6_6.1.x86_64.rpm 5e473fe3107a6158797ab4774a478ed14386260c9ef0a358c2324d8bcbc78ddc perl-version-0.77-136.el6_6.1.x86_64.rpm Source: bbda4e900dacb9f5857802f0067a87b26fafa46d5f2660115d0afb337b3cda45 perl-5.10.1-136.el6_6.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 12 Nov 2014 12:50:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2014:1846 Moderate CentOS 7 gnutls Security Update Message-ID: <20141112125047.GA64051(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:1846 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1846.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a2ea3c099a7ac3fde0b5765424f47f1dcca3f8ffdb7fb99107c69bf9652f14e1 gnutls-3.1.18-10.el7_0.i686.rpm bff7312e5e9c7df0a6ae2919ce752c57e2a942a2a69b4adcb00548d9634e4f4f gnutls-3.1.18-10.el7_0.x86_64.rpm 74c7b568d9e6fcfde96db5b5da7d26c2ebcc1e54c5e0e250e1fd5879a21fbb3e gnutls-c++-3.1.18-10.el7_0.i686.rpm 8a01f2101228abb001c804729e4236761ff16f71b9722cc748d6d212be776d63 gnutls-c++-3.1.18-10.el7_0.x86_64.rpm 764f7daae4d4e7a7523c82f88375cc96d45e31d7034565ea7b852c24f4d31e38 gnutls-dane-3.1.18-10.el7_0.i686.rpm 55a82123cd98cd4c708f2f46eb6ff75b2e04c3937a9843e8fc439fafcb6e4b15 gnutls-dane-3.1.18-10.el7_0.x86_64.rpm 7bfe2b443b51af2fd37df7528af6c3638646b779ae1bd3d7da50ce3ca5ccff6b gnutls-devel-3.1.18-10.el7_0.i686.rpm 1f889ac146f9869c7662b35ec85adc6515037d60a7e520c1b4ffbd488829c741 gnutls-devel-3.1.18-10.el7_0.x86_64.rpm 6da4085f5f2c07b626a75482f49edd6a70b25b50bc6537806dcaaf3b16653ca6 gnutls-utils-3.1.18-10.el7_0.x86_64.rpm Source: d457f71a919a21ee0fd6a5e8d64f0f87337651fb359cc7d146abc4900f4d82fd gnutls-3.1.18-10.el7_0.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Wed, 12 Nov 2014 12:51:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2014:1850 CentOS 7 virt-who BugFix Update Message-ID: <20141112125102.GA64125(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:1850 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1850.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a47f31f1e1fceef2f5821c905ce21ed452dfe0bd5cf95c8ba8ae0c633b8e7892 virt-who-0.8-15.el7_0.noarch.rpm Source: 278953fae130206e846aa517eb3fa66e7363022e125c38806dccc1acc8f1b924 virt-who-0.8-15.el7_0.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Wed, 12 Nov 2014 12:51:19 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2014:1826 Moderate CentOS 7 libvncserver Security Update Message-ID: <20141112125119.GA64208(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:1826 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1826.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ec7ff8e89213e1f67ab4b0a3eca064b6968c1b308e03695e35bfb799a28493c8 libvncserver-0.9.9-9.el7_0.1.i686.rpm 1720f5c8df837269ae5be9c5dc10598ab4ca90281d4fb1d56cf52a44b6aa1760 libvncserver-0.9.9-9.el7_0.1.x86_64.rpm 073e759f54508f76cfbeb11e077107e88f6fc854b37d5fbbd2cb450806b805de libvncserver-devel-0.9.9-9.el7_0.1.i686.rpm a0f6d7d3c1fd46803c1826a3f67e78d813330c8ce81890cc368a0b5ca0459e50 libvncserver-devel-0.9.9-9.el7_0.1.x86_64.rpm Source: e3c8ed18fe9d8decdb2923b46340f5447322aeb4d768a7657ced40c5c0dce433 libvncserver-0.9.9-9.el7_0.1.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 117, Issue 7 ***********************************************

1 0

Re: [CentOS] Keepalived - spurious failovers
by John Horne 12 Nov '14

12 Nov '14

On Wed, 2014-11-12 at 16:45 -0500, m.roth(a)5-cent.us wrote: > John Horne wrote: > <snip> > > Given that failover only occurs if Apache, Tomcat or the NIC fail, I > > can't find anything in log rotation that could cause this effect. For > > failover to occur the Apache/Tomcat process must be non-existent (in our > > case keepalived checks for them using pgrep). We have secondary > > monitoring of these processes (Xymon using checks of 'ps'), and that > > shows no such failure. Simply logging into the servers and running ps > > shows that they are running. I would hope that something would be logged > <snip> > I don't suppose there was anything in dmesg, either on the guests or the > host? > Nope. John. -- ---------------------------------------------------- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK

1 0

Anyone have any experience with Epson EasyMP projectors?
by Fred Smith 12 Nov '14

12 Nov '14

The folks at my office have acquired a new Epson EasyMP wireless projector, which requires a windows/MacOS plugin to use. Of course, they don't provide one for Linux. Here's their web page on it: http://www.epson.com/cgi-bin/Store/support/supDetail.jsp?BV_UseBVCookie=yes… Do any of you folks out there know of any way to use Linux with one of those devices? Thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ---------------------------- Do you not know? Have you not heard? The LORD is the everlasting God, the Creator of the ends of the earth. He will not grow tired or weary, and his understanding no one can fathom. ----------------------------- Isaiah 40:28 (niv) -----------------------------

1 0

Re: [CentOS] Keepalived - spurious failovers
by John Horne 12 Nov '14

12 Nov '14

On Wed, 2014-11-12 at 10:27 -0500, m.roth(a)5-cent.us wrote: > John Horne wrote: > > > > We are using CentOS 6.6 and keepalived 1.2.13 on two servers for > > failover, no load-balancing. Failover is governed by the NIC being > > present, and the Apache and Tomcat processes being present. Both servers > > are configured as 'EQUAL' (not master/backup). An initial priority of > > 100 is set, and if a process or NIC fails, then this is reduced by 60 - > > causing a lower priority to be seen and failover to take place. > > Generally this works well. If we stop the network or one of the > > processes, this is logged (to /var/log/messages) and failover happens > > within a few seconds. > > > > However, we have had failovers occur during the night several times. It > > happened last night, and the night before. Nothing was logged in the > > messages file about the NIC being down, or the Apache/Tomcat processes > > being unavailable. Nothing was logged by the Apache or Tomcat processes > > in their own log files. The failovers have happened at 03:56 on both > > nights. > > > > The most obvious suspect causing this would be some nighttime process > > such as log rotation or automatic updates. However, I can see nothing > > obvious occurring during the night that would cause the keepalived > > virtual interface to failover. > <snip> > I trust you've looked at the crontab, and /etc/cron.daily, etc. > Yes. Nothing obvious that would cause a problem to apache/tomcat or the network. > The other option: have you looked *outside* the systems? Do you have a > cable between the two, or is it over the network? Is there a network > thing going on? For example, are the servers on a UPS, and the switch > they're on not on one? > They are both virtual servers - so no UPS. Failover communication is over the network. John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK

2 2

Re: [CentOS] To James B. Byrne
by James B. Byrne 12 Nov '14

12 Nov '14

On Tue, November 11, 2014 19:33, Igor Zubkov wrote: > On Tue, Nov 11, 2014 at 6:16 PM, Alexander Farber wrote: >> Dear James, >> >> everyday I look into my Gmail SPAM folder and your mails (sent to >> Centos list) are there. Noone else is there but you. >> >> Please finally fix your MX records or whatever is needed. No offence > > I bit a tired of this too. > > James, be the Man and fix your mail server. Or what else. > >> Greetings from Germany >> Alex > > Greetins from Ukraine (Donetsk). > But, the mail server is not broken. It is entirely to RFC specifications. Google decides how to treat the resulting confusion respecting mail forwarded by the CentOS list. Yahoo I understand simply drops it into the bit bucket and the recipient never knows. Your complaint would be better directed at the consortium of Email providers, including Google and Yahoo, who forced DMARC on the IETF; or rather entirely by-passed the IETF and put this Rube Goldberg hack into play regardless. The people who run mailing lists screamed blue murder but it happened nonetheless. In any case the fix to this for Mailman already exists. It just needs to be accepted by RedHat and rolled out as an update. I tried to build it myself and succeeded in getting a working version on CentOS6. But, the source package layout does not fit the HFS used by RedHat and I could not deploy it for that reason. Nor could I figure out the patches necessary to restructure the project layout into something resembling HFS. Nor could I figure out the interim changes between the current Mailman version and that shipped with CentOS to back-port the fixes in a systematic way. I apologise for the number of messages presently originating from me. This one included. Once I get past my ignorance with CentOS7 and can manage on my own I will stop annoying the list with questions and replies. -- *** E-Mail is NOT a SECURE channel *** 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

Re: [CentOS] Keepalived - spurious failovers
by John Horne 12 Nov '14

12 Nov '14

On Wed, 2014-11-12 at 11:12 -0500, m.roth(a)5-cent.us wrote: > John Horne wrote: > >> > > They are both virtual servers - so no UPS. Failover communication is > > over the network. > > Um, bingo: are the host systems on UPS's? What happens on the *host* > systems at 03:56? They don't, perhaps, take snapshots of the guests then? > No, no snapshots are taken. As said this is a spurious event which has happened at 03:56 for the past two nights. However, we ran for a few days before then with no problems. Before that it happened at something like 5AM. It does not happen every night, nor at the same time (usually). I have set up a couple of cronjobs to check ifconfig and ping the interface every few seconds. I also have a job that will monitor the main interface for VRRP traffic since that should show what the priority value is when a server claims to have received a higher priority from another server. John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK

1 0

Re: [CentOS] To James B. Byrne
by James B. Byrne 12 Nov '14

12 Nov '14

On Tue, November 11, 2014 13:05, Alexander Farber wrote: > And ignore the Chrome people getting > the certificate warning at https://harte-lyne.ca too ;-) > We operate our own CA. If you 'TRUST' us then you can add the the root cert for our CA by visiting http://ca.harte-lyne.ca/CA_HLL_ISSUER_01/ca.crt and accepting the cert (presumably after reading the CP and CPS statements). Then the warning will disappear. If not then you can leave or proceed, accepting the exception permanently or not, as your inclination dictates. That web site is ancient and was designed for straight http access. It is in the process of revision but that is not in my hands and given past events I have no expectation of anything changing soon. We have since gone to "https everywhere" and thus the certificate is now an issue. Most of our sites are blocked to outside access or require authentication in any case. That said, the issue of Trusted certificates is problematic. In my opinion, the present state of the PKI CA's is in such disarray that anyone that is counting on the 'Trusted' CA's that come pre-installed in browser packages is living in blissful ignorance of the underlying risks presented thereby. Users are rarely aware, or realise the implications, of the fact that any 'Trusted' CA can issue a valid certificate for ANY domain. Any browser that 'Trusts' that CA will accept any site presenting said certificate as legitimate. This is the singular weakness of imposing a hierarchical requirement on top of a distributed solution. DNSSEC is representative of the alternative approach that I believe eventually will be adopted for all forms of network identities, including email. Our company policy at the moment does not properly address the Trusted CA issue either; Other than we have set up and exclusively use our own CA for our own use. I am pushing to have all default trusted roots removed from all user's browsers and only approved roots added back. This is not feasible at the present time because of the lack of any automated tool (of which I am aware and that is FLOSS) to enforce it. For that matter, we are still waiting for our registrar to support DNSSEC, for which we have been ready since early 2012 and the .ca. registrar since 2013. -- *** E-Mail is NOT a SECURE channel *** 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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss