The fix is that the NSA's of the world MUST also participate in risk reduction
to the world by submitting their newly found entry methods to the companies
that can fix it!
The expectation that this stuff would not eventually make its way to the rest
of the world, or that it wasn't already
How about a basic item (that I do not recall being requested of seen as yet)
Cmd line - 'ipconfig /all' - send us the results of that
Would be concerned if any IP address given is not on the desired network or is
one of the 169 set.
DHCP server should be yours - not some other unknown DHCP
I'm much more unnerved by the term 'blast radius'
Cal
-Original Message-
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Michael B. Smith
Sent: March 2, 2017 3:36 PM
To: ntsysadm@lists.myitforum.com
Subject: RE: [EXTERNAL]Re: [NTSysADM] AWS East
Agreed. Why did this happen and who of all the resident clients were affected
and why?
Curious that so many of their client sites/services were affected by this as
much as they were.
S3 has over a dozen more sites over the USA. Is this an issue of redundancy
failing, or clients not
4 matches
Mail list logo
