<br><br><div class="gmail_quote">On Wed, Apr 21, 2010 at 9:23 AM, Stuart Sheldon <span dir="ltr"><<a href="mailto:stu@actusa.net">stu@actusa.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
</div><div><div></div><div class="h5">Randy R wrote:<br>
> On Wed, Apr 21, 2010 at 2:55 PM, Fred Posner <<a href="mailto:fred@teamforrest.com">fred@teamforrest.com</a>><br>
> wrote:<br>
>> On Apr 21, 2010, at 4:50 AM, Gordon Henderson wrote:<br>
>><br>
>>> On Tue, 20 Apr 2010, Frank Bulk wrote:<br>
>>><br>
>>>> Please take note of their posting:<br>
>>>> <a href="https://aws.amazon.com/security/" target="_blank">https://aws.amazon.com/security/</a> which discusses the issue and<br>
>>>> what they're doing to improve response.<br>
>>> And is anyone on the list worthy of being considered a<br>
>>> "significant SIP provider" to be honoured with the privilege of<br>
>>> working with them?<br>
>>><br>
>>> Gordon<br>
>>><br>
>> None of the carriers I deal with have been contacted. Of course,<br>
>> them only contacting "significant" providers... does that mean it's<br>
>> ok if the attacks happen to non-significant providers or<br>
>> end-points?<br>
>><br>
>> ---fred <a href="http://qxork.com" target="_blank">http://qxork.com</a><br>
><br>
> If it got to their BS/PR page/blog it means they're hearing about<br>
> complaints on the net as well as people like you submitting. Everyone<br>
> please keep posting where you can and sooner or later, someone big<br>
> will pick up the story.<br>
><br>
> Funny, I'd think the most "worthy" people to comment on this issue<br>
> are on this list. That's the feedback they should be looking for and<br>
> working on at Amazon EC2.<br>
><br>
> /r<br>
><br>
<br>
</div></div>We might me reading their PR wrong... Maybe there were large SIP<br>
providers that were compromised due to this attack... Maybe they are<br>
keeping that quiet at the request of those providers... It could also be<br>
that the aliens in hiding in Colorado are behind the whole thing! ... Oh<br>
no! I've said too much!!! LOL...<br>
<br>
It could actually be the case that this whole issue went beyond what we<br>
are seeing, and they are trying to protect one of their Whale customers...<br>
<br>
Needless to say, what about the SSH brute force attacks that originate<br>
from their network? What about the SPAM that flows like a fountain from<br>
their net blocks?<br>
<br>
This was nothing more then PR hype...<br>
<br>
Stu<br clear="all"><br></blockquote><div><br>Assuming that every such spamming/hacking/attack site is funded on a<br>stolen identity/CC number, it will soon sink into Amazon that they are<br>getting a bad rep, and losing money on such problems, as all such charges<br>
are reversed when the identity theft is discovered... How they overcome<br>the problem, should be a tribute to the marvelous power of human ingenuity.<br><br>murf<br></div></div><br>-- <br>Steve Murphy<br>ParseTree Corp<br>
<br>