On Wed, Sep 11, 2019 at 10:25:49PM +1000, Andras Toth wrote:
> This is the same as saying it's Amazon's fault that people make their S3
> buckets public and information gets exposed.
Misconfigure it once, shame on you. Misconfigure it 1,000 times, shame on
the system.
Also, AWS have been doing
The world was much simpler when ISP's could just print Invoices direct to
customer printers on Windows 95 dialup connections..
On Thu, 12 Sep 2019 at 08:20, Matt Palmer wrote:
> On Wed, Sep 11, 2019 at 10:25:49PM +1000, Andras Toth wrote:
> > This is the same as saying it's Amazon's fault
Hi Noggers,
There's a NAB online banking scam sending SMS messages with a URL to a
.services domain which poses as NAB Internet Banking.
"NAB Alert - We have detected a potential issue and blocked your internet
banking. Please visit to confirm your device."
If you are the telco with
You just have to keep telling me until I do.
scott
--- b...@bradleyamm.com wrote:
From: Bradley Amm
To: Matthew Moyle-Croft
Cc: ausnog mailing list
Subject: Re: [AusNOG] Came across this
Date: Wed, 11 Sep 2019 11:39:03 +0800
I'd tell you a joke about UDP but you might not get it
On
Hey All,
Does anyone know anything about the cable cuts in the Japan region? We are
seeing latency, congestion and fairly suboptimal paths via a couple of carriers
who are trying to route around it.
David Hooton
Founder | Ordnance
Cloud Scale, Carrier Grade
AU Cell: +61 415 850 000 US Voice:
Hi,
There's a NAB online banking scam sending SMS messages with a URL to a
.services domain which poses as NAB Internet Banking.
"NAB Alert - We have detected a potential issue and blocked your internet
banking. Please visit to confirm your device."
If you are the telco with these DIDs,
Maybe I do, maybe I dont.
On Wed, 11 Sep 2019 at 4:47 pm, Scott Weeks wrote:
>
> You just have to keep telling me until I do.
>
> scott
>
>
>
> --- b...@bradleyamm.com wrote:
>
> From: Bradley Amm
> To: Matthew Moyle-Croft
> Cc: ausnog mailing list
> Subject: Re: [AusNOG] Came across this
>
The person that got access to their system was not an AWS employee when the
breach happened. The person got access via a misconfigured server/system
that wasn't Amazon's fault.
See the original court case for details:
http://regmedia.co.uk/2019/07/29/capital_one_paige_thompson.pdf
This is the
