On 02/06/2014 10:41 AM, Phelps, Matt wrote: > On Thu, Feb 6, 2014 at 11:12 AM, Fabian Arrotin > <fabian.arrotin at arrfab.net>wrote: > >> On 06/02/14 16:26, Phelps, Matt wrote: >>> On Wed, Feb 5, 2014 at 12:30 AM, Robert Arkiletian <robark at gmail.com> >> wrote: >>>> new potential remote code exploit in Chromium flash. >>>> >> http://googlechromereleases.blogspot.ca/2014/02/stable-channel-update.html >>>> Doesn't look like these repos are being updated. >>>> http://people.redhat.com/tpopela/rpms/ >>>> http://people.centos.org/hughesjr/chromium/6/ >>>> >>>> Any info on this issue would be welcome. >>>> >>> >>> Yes, please. Can the CentOS folks check with their newly minted Red Hat >>> brethren on this issue? >>> >>> This is getting critical for us. We have over a hundred CO6 desktops that >>> are currently running an insecure version of chromium. The security >> people >>> are all over us on this! >>> >>> We need to run chrome/chromium in order to manage our Google Apps for >>> Government deployment (for over 1000 users). It doesn't work right with >>> firefox. >>> >>> If we need to apply pressure elsewhere, please let us know where to >> direct >>> our fury. >>> >> ... to Google ? (especially because it's *their* browser to support >> *their* Google Apps ....) >> >> > Of course we already have notified Google. > > I was hoping for a little more granularity. Google is a large place; as is > Red Hat I know. There was word that Red Hat was working with Google on a > solution, and I was hoping to hear if there was any movement. > > I can't ask Red Hat since we don't pay for it, but perhaps the new CentOS > relationship with them can offer a channel of communication for the > Community. Sure, we talked to them (redhat). That does not make the code actually build any faster. The code does not build (as is) on EL6 and each build needs to be troubleshot and error corrected to make it work. Currently there are several pieces not building ... just like there were before. The 31 tree was finally made to build, after several changes, The 32 tree is not building. I like to use chromium as well ... but the only supported browser is Firefox ... that is the one with EL support. Chromium is a best effort to get to build (and it always will be) ... Google has no interest in supporting it, so we are taking the code that they release and working with it until it builds on EL6. WRT your google apps docs ... OK, so have 2 browsers on your system. Use the chromium for your google apps and firefox for everything else. I told everyone that the chromium support was as can be made to work. If you REALLY need it to work, hire someone to maintain it :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20140208/237ef0af/attachment-0004.sig>