For those interested, this is the Xen bug they were fixing with the reboots
http://xenbits.xen.org/xsa/advisory-108.html
-Grant
On Wed, Sep 24, 2014 at 8:41 PM, Reed Loden r...@reedloden.com wrote:
On Wed, 24 Sep 2014 21:39:39 -0400
Peter Beckman beck...@angryox.com wrote:
Likely some sort
On Wed, Oct 01, 2014 at 11:01:37AM -0700, Grant Ridder wrote:
For those interested, this is the Xen bug they were fixing with the reboots
http://xenbits.xen.org/xsa/advisory-108.html
Ouch. Good thing Bashpocalypse is still capturing everyone's attention...
Interestingly, Amazon *didn't*
On 01/10/2014 4:29 PM, Matt Palmer wrote:
On Wed, Oct 01, 2014 at 11:01:37AM -0700, Grant Ridder wrote:
For those interested, this is the Xen bug they were fixing with the reboots
http://xenbits.xen.org/xsa/advisory-108.html
Ouch. Good thing Bashpocalypse is still capturing everyone's
read: http://www.xenproject.org/security-policy.html
they have a sensible, commonly used security policy that involves private
notification to large customers in advance where it is practical and there
is not evidence of ongoing exploits in the wild.
this is kind of incident handling 101 and
On 10/01/2014 02:59 PM, Todd Underwood wrote:
read: http://www.xenproject.org/security-policy.html
they have a sensible, commonly used security policy that involves private
notification to large customers in advance where it is practical and there
is not evidence of ongoing exploits in the
On Oct 1, 2014, at 4:59 PM, Todd Underwood toddun...@gmail.com wrote:
this is kind of incident handling 101 and shouldn't be surprising to anyone.
There’s always people who feel “left out of the loop” when these things occur.
I’ve found
there’s no one location for centralized data after
As an FYI, it looks like Amazon is doing a mass reboot of the physical
hosts in us-west-2 across all AZ's and it is scheduled to start tomorrow
and take a couple days.
Go to *https://console.aws.amazon.com/ec2/v2/home?region=us-west-2#Events
Bash related?
On Sep 24, 2014, at 4:47 PM, Grant Ridder shortdudey...@gmail.com wrote:
As an FYI, it looks like Amazon is doing a mass reboot of the physical
hosts in us-west-2 across all AZ's and it is scheduled to start tomorrow
and take a couple days.
Go to
Likely not, since it's affecting Windows instances as well.
Also not just us-west-2 -- we have tons of instances scheduled for
downtime in us-east-1 and eu-west-1 as well.
-Peter
On 09/24/2014 04:51 PM, Gabriel Blanchard wrote:
Bash related?
On Sep 24, 2014, at 4:47 PM, Grant Ridder
Doubt it since a bash patch shouldn't require a reboot
On Wed, Sep 24, 2014 at 1:51 PM, Gabriel Blanchard g...@teksavvy.ca wrote:
Bash related?
On Sep 24, 2014, at 4:47 PM, Grant Ridder shortdudey...@gmail.com
wrote:
As an FYI, it looks like Amazon is doing a mass reboot of the
Just got the same email. Not just US. Servers in Sydney we have also. Why
such short notice?
On Sep 24, 2014 4:58 PM, Grant Ridder shortdudey...@gmail.com wrote:
Doubt it since a bash patch shouldn't require a reboot
On Wed, Sep 24, 2014 at 1:51 PM, Gabriel Blanchard g...@teksavvy.ca
wrote:
On Wed, Sep 24, 2014 at 3:56 PM, Grant Ridder shortdudey...@gmail.com wrote:
Doubt it since a bash patch shouldn't require a reboot
Unless you have a long-running bash script in the background providing
a vital system service, and that service is so important in your
environment that you might
Likely some sort of potentially serious bug or flaw in EC2 or Xen. AWS
Security is really on the ball on such things and do everything they can to
make invisible fixes with no customer impact, but sometimes a reboot is
required in order to apply the changes necessary to keep customer instances
On Wed, 24 Sep 2014 21:39:39 -0400
Peter Beckman beck...@angryox.com wrote:
Likely some sort of potentially serious bug or flaw in EC2 or Xen. AWS
Security is really on the ball on such things and do everything they can to
make invisible fixes with no customer impact, but sometimes a reboot is
14 matches
Mail list logo
