Threatening cracks at another neglected building

On 28th March 2013 a neglected wall at the CUB Brewery site fell onto Swanston Street, killing three pedestrians. So how many other abandoned buildings around Melbourne are at risk of falling over?

Massive crack in the facade of 243-251 Flemington Road, North Melbourne

I found one at the corner of Abbotsford Street and Flemington Road in North Melbourne recently, attracted by the ‘Wheelwright’ and ‘Shoeing Forge’ signs on the facade.

'Wheelwright' and 'Shoeing Forge' signs on the facade

However I didn’t notice the massive crack in the brickwork, until a Twitter follower sent me a link to a Google Street View image showing how bad it really was.

Close up view of the cracked brick wall

As it happens, it was luck that I took my photos when I did, because by the first week of April, the entire building had been reduced to a pile of rubble.

243-251 Flemington Road, North Melbourne reduced to a pile of bricks

So how long had that crack in the wall been there? When I looked into the history of the site, I found this was yet another case of an abandoned building being neglected by property developers, and becoming a risk to public safety.

History of the site

Located on the corner of Abbotsford Street at 243-251 Flemington Road, North Melbourne, the building has been abandoned for a number of years. A search of the City of Melbourne planning register bring up the first relevant result in 2004:

Permit Number:
TP-2004-1184
Date Received:
23/11/2004
Proposed Use or Development:
Construct building for use as a medical centre,child care centre, function hall and dwellings
Objections Received:
82
Decision:
Refusal – 22/12/2005

With concerns about the intensity of the land use, and a massive number of objections, the City of Melbourne refused to issue a planning permit. As a result the developer appealed the decision at Victorian Civil and Administrative Tribunal (VCAT) in 2006, which upheld the decision, but two years later the developer revised the design, and tried again to gain approval:

Permit Number:
TP-2007-387
Date Received:
7/05/2007
Proposed Use or Development:
Demolition of existing buildings and development of a three storey building to be used for a child care centre, child play centre (indoor recreation facility), and five dwellings
Objections Received:
18
Decision:
Refusal – 11/12/2007
Permit – 18/08/2008

The City of Melbourne refused this proposal at a council meeting on 4 December 2007, but VCAT overturned the decision, and a planning permit being issued. From the date the building fell into limbo, and with the developer not commencing construction, the planning permit expired two years later. For this reason, in 2011 the development again went before council:

Permit Number:
TP-2011-652
Date Received:
16/08/2011
Proposed Use or Development:
The use of the building for a childcare centre, medical centre and food and drink premises, reduction in the provision of car parking, the construction of a building and the construction or carrying out of works, waiving the requirement for loading and unloading facilities
Objections Received:
11
Decision:
Refusal – 17/02/2012
Permit – 28/02/2012

With a new planning permit granted in 2012, the developer set the ball rolling for construction, requesting a demolition permit for the building:

Permit Number:
TP-2012-1026
Date Received:
24/12/2012
Proposed Use or Development:
Demolition of the building
Objections Received:
0
Decision:
Permit – 24/12/2012

So was the building ever heritage listed?

While the site is affected by the Heritage Overlay (North and West Melbourne precinct), the structure was never listed – it was just an ungraded building in the Heritage Places Inventory. So why wasn’t this building listed when everything else in the area was added the register – no one seems to know.

Further reading

PTV website redesign, and a trail of broken links

On 21 April 2013 Public Transport Victoria launched their new public transport information website, saying in their press release:

The website has been redesigned to make it quicker and easier for you to access the information you need.

However they missed one big item in the move to the new website – redirecting each of their old URLs to the relevant page on the new website. I came across the issue while using Google to find information relating to concession tickets.

Google Search results pointing to broken pages on the PTV website

The first search result from Google was to this URL:

http://www.ptv.vic.gov.au/fares-tickets/concessions/

Which when clicked on lead me to a useless error page:

'Page not found' error for an old URL on the PTV website

After a bit of clicking around on the new PTV website, I finally found the page I was originally supposed to land on:

The page that should be found on the PTV website

Note the URL up in my browser bar:

http://www.ptv.vic.gov.au/tickets/concessions/

The only difference between the old and the new URLs is one word in the middle, where the ‘fares-tickets’ portion on the old has been replaced by ‘tickets’ on the new one. Nothing else!

I touched on the issue of website migrations leaving a legacy of broken links a few months ago, when I encountered a similar issue with the Fairfax ‘Metro Media Publishing’ newspaper websites.

In the case of Public Transport Victoria, they have done two things wrong:

  • When they moved their website, PTV didn’t bother to keep the URLs the same between the new and the old systems.
  • If keeping the old URLs was not possible, then PTV should have set up redirects to the new URL, to ensure any links already out on the internet continue to work after the move was complete.

So when will all of the broken links disappear from Google Search? The ‘page not found’ page on the PTV website returns a correct ‘HTTP 404′ status code, so in time Google will purge the bad links from their database, and replace them with the correct links when they next crawl the website.

'HTTP 404' response from the redesigned PTV website

All this messing around, all because someone decided to change ‘fares-tickets’ to just ‘tickets’!

The wardriving tram and ‘hacking’ Myki machines

As an eagle-eyed observer of Melbourne’s Myki ticketing system, I have stumbled across many different error messages displayed on the Tram Driver Consoles located inside the cab of each of Melbourne’s trams. But this message is a new one…

Playing around with WiFi SSID (network names) on a Tram Driver Console

If you really squint, one of the lines on the display reads ‘myki was p0wned’. So how did it get there?

Background

The story starts on my tram home from work, when I noticed the Tram Driver Console in the rear cab was stuck in a reboot loop. The first screen was a simple ‘Launching application’ message on the standard Windows CE desktop.

Myki tram driver console stuck in a reboot loop

Next was a Myki splash screen, and the message ‘Install Manager Loading. Please Wait’

Myki 'Melbourne Install Manager' starting up

After a moment the splash screen disappeared, leaving the console back at the Windows CE desktop, and a wireless network configuration dialog.

Tram Driver Console on a 'wardriving' mission, displaying the names of all nearby WiFi networks

And so the cycle repeated. As I continued on my trip home, I realised that the list of networks displayed onscreen changed, as the WiFi signals dropped in and out of range of the tram – it was on a wardriving mission!

A short distance down the tracks, and a new set of WiFi networks

I then realised I could have a little fun with Myki screen, setting up my phone as a wireless hotspot with a smart alec SSID (network name), and wait for the rebooting console to pick it up.

‘myki was p0wned’ was an obvious one.

Wireless network called 'myki was p0wned' displayed on a Tram Driver Console

Getting my name up there with ‘wongm was here’ was another.

Wireless network called 'wongm was here' displayed on a Tram Driver Console

And ‘Penis!’ appealed to the immature part of me.

Wireless network called 'penis!' displayed on a Tram Driver Console

I was the only one there to notice it, but it was a giggle while it lasted.

So how bad is this flaw?

For a start, the reboot loop I saw isn’t an everyday occurrence – this is the first time I’ve seen one just like it. The cause was hidden in an error message that flashed up when the ‘Melbourne Installation Manager’ program was starting up. After many attempts, I managed to snap a photo while it flashed up on screen for a fraction of a second.

The reason the Tram Driver Console was rebooting: an incorrect SD card was installed

If you can’t read it, the details are:

Configuring this device to the new SD card
An SD card from another device has been detected

The above suggests a few things:

  • The startup process for the Tram Driver Console goes: Boot screen > Windows CE desktop > Myki ‘Melbourne Installation Manager’ program
  • The device has a SD card slot so that software updates can be carried out to the console.
  • The Myki software has some form of security check when reading from the SD card, ensuring that only data from authorised media is loaded.

From that, it seems that at least some security has been baked into the update process: while the Tram Driver Console is locked up inside the cab, even if one gained physical access to the device in order to insert an external storage device, the software won’t update itself from anything you give it – some form of validation is occurring.

However, the device itself isn’t locked down enough to avoid showing the Windows CE desktop: once someone had physical access to the machine, it seems that loading and executing an arbitrary piece of software on the console might be possible before the ‘Melbourne Installation Manager’ program starts up. Tram driver playing solitaire anyone?

As for WiFi access being enabled – why is it even needed for it on a tram travelling the streets of Melbourne? The reason lies in the way Myki is architected: the card is the source of truth of all data, with the backend systems needing to kept in sync on a regular basis. In the case of railway stations the list of online topups and blocked cards can be updated in real time via a hardwired network connection, but for moving vehicles likes trams they need some other way.

Back in the early 2000s when Myki was being scoped, ubiquitous data connections through the 3G network were still new, so instead it was decided to install a WiFi connection covering each bus and tram depot, which the Myki devices automatically connect to when they head home each night. This intermittent connection also explains why Myki online topup doesn’t happen instantly – the request to topup your card needs to reach the reader on the tram before it can be applied.

Look out for hackers?

So is this a hack, or just a mere intellectual curiosity? Definitely the latter – every day millions of people turn on their WiFi enabled smartphones and laptops looking for wireless networks to connect to, and malicious wireless network names aren’t crashing their devices – using them to send passive-aggressive notes to neighbours seems to be as bad as it gets. If you did the same thing to a friend’s mobile phone you aren’t even a script kiddie, let along a hacker.

Footnote

A search of the Common Vulnerabilities and Exposures database shows that broadcasting a maliciously named SSID over the air isn’t a common attack vector, with Microsoft TechNet also draws a blank.

Also, I spent a moment investigating the significance of the ‘CW981′ title of the wireless network dialog box. The first relevant hit on Google was a forum thread where someone was trying to get a wireless network card working – where the ‘CW981′ is an internal code inside the Windows Registry. The device in question was a NETGEAR MA701 Wireless CF Card, which was designed for Windows CE devices. Possibly the Tram Driver Console uses one of these to access the wireless network?

‘Jaywalking’ in the Melbourne CBD

It seems that every second month the Victoria Police decide to hold a jaywalking ‘blitz’ in the Melbourne CBD – in the 2011-12 financial year they issued 5690 fines to pedestrians. So what actual offence do the infringement notices have written on them?

Police book jaywalkers outside Flinders Street Station

The VicRoads road rules for pedestrians page has the following to say:

Fines apply to pedestrians who commit the following offences:

  • cross against an amber or red traffic light
  • cross against an amber or red pedestrian light
  • cross the road within 20 metres of a pedestrian crossing
  • fail to cross to the nearest edge of the road after getting off a tram
  • fail to obey a traffic instruction from a police officer
  • fail to use the shortest or most direct route across a road
  • get out of from a moving vehicle
  • walk along or fail to give way when crossing a bicycle path
  • walk improperly on a road (by not keeping to the far side facing oncoming traffic when walking along a road where it is not practicable to use the footpath or nature strip)
  • cross a level crossing when not permitted
  • disobey a ‘no pedestrian’ sign.
  • cause a traffic hazard by moving into the path of a driver

While not crossing against the red man is obvious, the interesting offence is “cross the road within 20 metres of a pedestrian crossing” – this means you could just walk down the street a little bit from the traffic lights and wait for a gap in the traffic, and you’re home free. So how can you know you’re more than 20 metres from an intersection in the Melbourne CBD? Trams are your perfect measuring stick!

Melbourne’s single carriage trams are around 15 metres long (Z3 class are 16.64 metres to be exact) so you’ll need to add a few meters to find your legal crossing location.

Z3.194 heads west on Victoria Street at Errol Street in North Melbourne

The two carriage B2 class trams are 23.63 metres long, so if one is stopped at the traffic lights, the tail end is probably a legal crossing location.

B2.2118 heads north on Elizabeth Street at Lonsdale

As for the modern low floor trams, they are all far longer – the C2 class ‘Bumblebee’ trams are 32.52 metres from nose to to tail.

When you think about it, 20 metres isn’t very far in the Melbourne CBD!

Footnote

I’m no lawyer, just a guy who knows where to find where our laws are published (the AustLII website is one).

In addition, while crossing more than 20 metres from a pedestrian crossing might be a legitimate option, common sense is still required – you could get booked for “failing to use the shortest or most direct route across a road” or “causing a traffic hazard by moving into the path of a driver” – and as a tram passenger they could get you for “failing to cross to the nearest edge of the road after getting off a tram”.

I’m hoping the ‘pay attention to traffic and not blabber away on your phone’ bit should be obvious!

Again, oblivious to traffic because of their mobile phone, and about to get booked for jaywalking

The not in service ‘in service’ Myki reader

Myki has a reputation for being a complete balls up: and the Myki check device at the northbound tram stop outside Melbourne Central Station is no exception.

A completely nonsensical message - 'In service / Please use another myki check'

If a device is ‘in service’ then I should be able to use it – so why are you telling me to use another device?

I first spotted the nonsensical error message back on March 20. One week later on March 27 I went past it again, still showing the same screen.

Myki check reader at Melbourne Central still stuck 'In service'

Fast forward to the evening of April 7, when Twitter user @mttb123 posted a photo of the very same screen:

Soon after that @mykimate, the official Myki representative on Twitter, replied:

It seems that things work slowly at Myki towers, because when I went past again on April 10 the same ‘In service’ message was still being shown.

Broken for four weeks now: Myki check reader at Melbourne Central still stuck 'In service'

Footnote

I’m going to assume that Myki equipment has some kind of remote monitoring software installed on them, so that if anything goes wrong, a service crew can be despatched to fix it. The blue Myki check readers are the possible exception, as they lack a network connection to talk back to the main Myki system.

And still more

A commenter mentioned that out-of-service Myki readers also display the same message. I found an example for myself the other week:

Myki reader onboard a tram, stuck with the nonsensical 'In service: Processing, please wait' message