Tony Abbott's passport number revealed after Instagram Post

[p--and--t]

Ah. Those were the days.

Seems they still do get several freebies.

Federal Register of Legislation - Parliamentary Business Resources (former Prime Ministers) Determination 2017

www.legislation.gov.au

 

[pagingjoan]

Seems they still do get several freebies.

Federal Register of Legislation - Parliamentary Business Resources (former Prime Ministers) Determination 2017

www.legislation.gov.au

I see that The Hon Julia Eileen Gillard AC still has the odd battle to fight:

Schedule—The Hon Julia Eileen Gillard AC
(Act s 16(1))

"If the former Prime Minister engages a driver on his personal staff...."
and
"The former Prime Minister has the option of engaging a driver on his personal staff....."

 

[TheRealTMA]

Seems they still do get several freebies.

Federal Register of Legislation - Parliamentary Business Resources (former Prime Ministers) Determination 2017

www.legislation.gov.au

They all do, inspite of their publicly funded largesse for life.

 

[2infinity]

Alex's blog was a great read.

Funnily enough, I used that 'inspect' option on the blog page and found Alex's phone number. I rang him to let him know about the issue

 

[MattA]

It's a long watch, but I thought this hacker talk about security issues around PNRs that someone posted in response to the Abbott story was fascinating...

 

[pauleg]

It's a long watch, but I thought this hacker talk about security issues around PNRs that someone posted in response to the Abbott story was fascinating...

MattA - thank you that was terrific and terrifying!!!! Most appreciated.

 

[Flashback]

It's a long watch, but I thought this hacker talk about security issues around PNRs that someone posted in response to the Abbott story was fascinating...

Haven't watched the video, but that was a PC game I played as a kid many times and thoroughly enjoyed it! Back then, Istanbul was Constantinople in the game......

 

[pagingjoan]

It's a long watch, but I thought this hacker talk about security issues around PNRs that someone posted in response to the Abbott story was fascinating...

Wow!
That was really worth watching.
Scary, though.
Thank you for posting.

 

[2infinity]

It's a long watch, but I thought this hacker talk about security issues around PNRs that someone posted in response to the Abbott story was fascinating...

I have deemed watching that video as a valuable use of an hour of work's time.

OMG. How can the travel system companies, such as Amadeus, think the current situation is acceptable. I'm sure their internal IT system has all the modern firewalls and protections.

It seems the only way the travel industry will change is when there is a major hack that affects many many people worldwide and they are forced to modernise. I just hope I'm not travelling at that moment in time.

 

[33kft]

OMG. How can the travel system companies, such as Amadeus, think the current situation is acceptable. I'm sure their internal IT system has all the modern firewalls and protections.

You can have all of the fancy hardware that you like, but when you have a house of cards consisting of old legacy mainframe apps with layers upon layers of integration with other systems and providers, you can't just change your patch. What has happened here is an 80s system has stayed an 80s system and we still rely on it today. Nobody has made the economic case for a complete replacement of this system by all parties involved because as they point out, that would affect all of Expedia's automations, the airlines systems, the revenue, ticketing, reservation, routing, award, codeshare, etc systems

Ask any one of those participants when a good time to swap out to a new system is. And then work out how they can all do it, at the same time, without grounding flights (they can't, they won't, which means even if there is already a modern replacement, it will be phased in very slowly - we'll be left with this situation for the next decade plus).

Now would have been a fantastic time to do it, in hindsight. What was missing was the foresight to have a plan in place for the very unlikely event we have just seen, and so instead of a rewrite, we get bandaids. The shutting down of sites that don't conform to security standards (ie moving the problem out to the edge not the core, where you have n instances of different security models and flaws vs 1) and sticking low effort captcha codes on everything.

I've seen a lot of this... a lot. I saw at a very large institution that we would all not like to think does this sort of thing (and holds lots of $$) that every year when a disaster recovery test was scheduled for the big ol 80s mainframe that has all of the logic in it for all of the products across the group, every product team with exposure to it would chuck a tantrum at the potential impact and veto it, so you have ancient systems which haven't even been tested for resilience due to their... age and importance,,,

Anyway, perhaps I should have cut my teeth on mainframe tech instead. I'd have a job for life.

 

[2infinity]

You can have all of the fancy hardware that you like, but when you have a house of cards consisting of old legacy mainframe apps with layers upon layers of integration with other systems and providers, you can't just change your patch. What has happened here is an 80s system has stayed an 80s system and we still rely on it today. Nobody has made the economic case for a complete replacement of this system by all parties involved because as they point out, that would affect all of Expedia's automations, the airlines systems, the revenue, ticketing, reservation, routing, award, codeshare, etc systems

Ask any one of those participants when a good time to swap out to a new system is. And then work out how they can all do it, at the same time, without grounding flights (they can't, they won't, which means even if there is already a modern replacement, it will be phased in very slowly - we'll be left with this situation for the next decade plus).

Now would have been a fantastic time to do it, in hindsight. What was missing was the foresight to have a plan in place for the very unlikely event we have just seen, and so instead of a rewrite, we get bandaids. The shutting down of sites that don't conform to security standards (ie moving the problem out to the edge not the core, where you have n instances of different security models and flaws vs 1) and sticking low effort captcha codes on everything.

I've seen a lot of this... a lot. I saw at a very large institution that we would all not like to think does this sort of thing (and holds lots of $$) that every year when a disaster recovery test was scheduled for the big ol 80s mainframe that has all of the logic in it for all of the products across the group, every product team with exposure to it would chuck a tantrum at the potential impact and veto it, so you have ancient systems which haven't even been tested for resilience due to their... age and importance,,,

Anyway, perhaps I should have cut my teeth on mainframe tech instead. I'd have a job for life.

Yep understand the why...........but one day this is going to happen and I hope I'm not travelling at that moment or needing to anytime shortly after

(aptly taken from the Movie: Flying High)

 

[pauleg]

Yep understand the why...........but one day this is going to happen and I hope I'm not travelling at that moment or needing to anytime shortly after
View attachment 228609
(aptly taken from the Movie: Flying High)

Great reference!!!!!!