Hi all,
Are there any plans to build new Fedora 19 20 cloud images with a fixed
bash?
Thanks
...Juerg
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct:
On Tue, Sep 30, 2014 at 11:40:40AM +0200, Juerg Haefliger wrote:
Are there any plans to build new Fedora 19 20 cloud images with a fixed
bash?
The security team didn't ask us to, as they did with heartbleed. I expect
it's because a yum update _without_ a reboot is sufficient in this case, but
On 09/30/2014 07:04 AM, Matthew Miller wrote:
On Tue, Sep 30, 2014 at 11:40:40AM +0200, Juerg Haefliger wrote:
Are there any plans to build new Fedora 19 20 cloud images with a fixed
bash?
The security team didn't ask us to, as they did with heartbleed. I expect
it's because a yum update
On Tue, Sep 30, 2014 at 07:07:46AM -0500, Joe Brockmeier wrote:
The security team didn't ask us to, as they did with heartbleed. I
expect it's because a yum update _without_ a reboot is sufficient in
this case, but maybe it's worth doing anyway
+1
Do we need to file a ticket with
- Original Message -
From: Matthew Miller mat...@fedoraproject.org
To: j...@redhat.com, Fedora Cloud SIG cloud@lists.fedoraproject.org
Sent: Tuesday, September 30, 2014 5:27:16 AM
Subject: Re: Shellshocked cloud images
On Tue, Sep 30, 2014 at 07:07:46AM -0500, Joe Brockmeier wrote
On Tue, Sep 30, 2014 at 07:07:46AM -0500, Joe Brockmeier wrote:
The security team didn't ask us to, as they did with heartbleed. I
expect it's because a yum update _without_ a reboot is sufficient in
this case, but maybe it's worth doing anyway
+1
Do we need to file a ticket with
On Tue, Sep 30, 2014 at 09:40:42AM -0400, Robyn Bergeron wrote:
I think it might be useful to actually have a process in place for how we
handle things like this.
Yes. See https://fedorahosted.org/cloud/ticket/43 and
https://fedorahosted.org/cloud/ticket/51 and
