Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
But they may well not want to just lose that history.terryc wrote
Don McKenzie wrote
HUH?
Could they possibly be running a windows Operating System,
Almost definitely.
without full back up and recovery, for an ambulance dispatch system?
Wouldn't fix this problem. you need to remove the "infection"
A full reinstall and restore from a backup made before the infection
would do it. Mind you, determining when the infection occurred might
be difficult.
Perhaps just a full reinstall. It's an ambulance dispatch system -
what happened yesterday is already history.
Nope, no one will buy that line now.Don McKenzie <5...@2.5A> wrote
Computer virus shuts down Ambulance dispatch service
The Ambulance Service of NSW computer dispatch system
became infected by a virus at about 1pm (AEDT) on Saturday,
forcing staff to shut it down and revert to co-ordinating the state's
paramedics and ambulances via a manual paper-based system.
The cause and source of the virus were unknown and the system
was still offline at 1pm (AEDT) on Sunday and it was not
known when it would be back up and running, Willis said.
http://www.arnnet.com.au/article/376471/computer_virus_shuts_down_amb...
HUH?
Could they possibly be running a windows Operating System, without
full back up and recovery, for an ambulance dispatch system?
Which will be another reason to push for internet censorship.
No reason for it to be net connected even if it does use the google maps database.To "protect" vital infrastructure.
Your "backup service is definitely nota FULL backup system.FULL means FULL.
So don't compare them.My service provider backs up my FULL server
(http://server.the-wizard-from-oz.com/) every 4 hours, and saves 30 days
of these backups. The system is capable of providing hundreds of
recovery points per day. I have access to restore a backup, from any
point at any time.
And I'm running a 2 bob shopping cart, not a life critical ambulance
dispatch system.
Not just Ambulance service that are "over securtitising" a Network toPetzl wrote:
Best I could make out was that even at the best of times (worse still
on Sundays), all IT administrators are such utter bastards, that they
block innocent sites such as Twitter, Myspace, FriendFace, gmail and all
porn sites from their corporate networks, the users have to wait till
they get home to use their own ISP (or steal it from their neighbours)
before they can whine on usenet about how hard off they.
Not that hard was it
I get that bit, what I don't get is how you gleaned that assumption
about the Ambulance service, what it has to do with them, and more
importantly, how do you know how they work to be able to make the
assumption that their IT administrators are utter totalitarian bastards.
Or lazy smucks who don't care about network security.
The original report doesn't give enough to point to either conclusion.
You didn't read my PC backup procedure also Terry?Don McKenzie wrote:
FULL means FULL.
Your "backup service is definitely nota FULL backup system.
My service provider backs up my FULL server (http://server.the-wizard-from-oz.com/) every 4 hours, and saves 30 days
of these backups. The system is capable of providing hundreds of recovery points per day. I have access to restore a
backup, from any point at any time.
And I'm running a 2 bob shopping cart, not a life critical ambulance dispatch system.
So don't compare them.
Think network.
And the Carbon Tax ? will that get anywhere ?kreed wrote
Don McKenzie <5...@2.5A> wrote
Computer virus shuts down Ambulance dispatch service
The Ambulance Service of NSW computer dispatch system
became infected by a virus at about 1pm (AEDT) on Saturday,
forcing staff to shut it down and revert to co-ordinating the state's
paramedics and ambulances via a manual paper-based system.
The cause and source of the virus were unknown and the system
was still offline at 1pm (AEDT) on Sunday and it was not
known when it would be back up and running, Willis said.
http://www.arnnet.com.au/article/376471/computer_virus_shuts_down_amb....
HUH?
Could they possibly be running a windows Operating System, without
full back up and recovery, for an ambulance dispatch system?
Which will be another reason to push for internet censorship.
Nope, no one will buy that line now.
To "protect" vital infrastructure.
No reason for it to be net connected even if it does use the google maps database.
Probably, because most of the 'independant' fools and the greens want it.Rod Speed <rod.speed....@gmail.com> wrote
kreed wrote
Don McKenzie <5...@2.5A> wrote
Computer virus shuts down Ambulance dispatch service
The Ambulance Service of NSW computer dispatch system
became infected by a virus at about 1pm (AEDT) on Saturday,
forcing staff to shut it down and revert to co-ordinating the
state's paramedics and ambulances via a manual paper-based system.
The cause and source of the virus were unknown and the system
was still offline at 1pm (AEDT) on Sunday and it was not
known when it would be back up and running, Willis said.
http://www.arnnet.com.au/article/376471/computer_virus_shuts_down_amb...
HUH?
Could they possibly be running a windows Operating System, without
full back up and recovery, for an ambulance dispatch system?
Which will be another reason to push for internet censorship.
Nope, no one will buy that line now.
To "protect" vital infrastructure.
No reason for it to be net connected even if it does use the google maps database.
And the Carbon Tax ? will that get anywhere ?
Ahh, run by shmucks obviously...Not just Ambulance service that are "over securtitising" a Network to
the point where it stil gets trojans or viruses. But is not productive
for it's intended use.
Just a while ago I went to send a email to my syate MP and get a
bounce
*******
Delivery to the following recipient failed permanently:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
recipient domain. We recommend contacting the other email provider for
further information about the cause of this error. The error that the
other server returned was: 501 501 Syntax error - Badly formatted
address. (state 14).
*******
Which is and was bull.
Only in Australia
My employer's e-mail system rejects anything vaguely executable, youPetzl wrote:
Not just Ambulance service that are "over securtitising" a Network to
the point where it stil gets trojans or viruses. But is not productive
for it's intended use.
Just a while ago I went to send a email to my syate MP and get a
bounce
*******
Delivery to the following recipient failed permanently:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
recipient domain. We recommend contacting the other email provider for
further information about the cause of this error. The error that the
other server returned was: 501 501 Syntax error - Badly formatted
address. (state 14).
*******
Which is and was bull.
Only in Australia
Ahh, run by shmucks obviously...
I had a problem with a client some time back, he couldn't download the
connection software for our gear, from our web site. His end objected
to the .exe installation file.
So I emailed the exe on its own. Still blocked.
So I renamed it, and tried again. Found it interrogates files, and
still blocks it.
So I zipped it, and tried yet again. Nope, it opens zips and checks
inside too.
I still had a password protected zip to try, but thought better of it.
I burnt a CD and sent it via snail mail. A three hundred year old
technology by-passed their modern day data security.
Though, truth be said, I can't really blame the admin for that, it was
probably a four-brain-celled-upper management directive. To this day I
still wonder how they manage to undo their zipper before pissing. Or
that they managed to get their pants on in the first place...
Looks to me like this was a "closed" network not connected to internetOn 15/02/2011 3:05 AM, John Tserkezis wrote:
Petzl wrote:
I still had a password protected zip to try, but thought better of it.
I burnt a CD and sent it via snail mail. A three hundred year old
technology by-passed their modern day data security.
Though, truth be said, I can't really blame the admin for that, it was
probably a four-brain-celled-upper management directive. To this day I
still wonder how they manage to undo their zipper before pissing. Or
that they managed to get their pants on in the first place...
My employer's e-mail system rejects anything vaguely executable, you
just add another extension to make it something like fred.exe.zzz and
get the recipient to strip the extra extension before use.
Stupid implementation. Its completely trivial to reject stuff done like that too.keithr <keith@nowhere.com.au> wrote
John Tserkezis wrote
Pretzl wrote
I still had a password protected zip to try, but thought better
of it. I burnt a CD and sent it via snail mail. A three hundred
year old technology by-passed their modern day data security.
Though, truth be said, I can't really blame the admin for that,
it was probably a four-brain-celled-upper management directive.
To this day I still wonder how they manage to undo their zipper before
pissing. Or that they managed to get their pants on in the first place...
My employer's e-mail system rejects anything vaguely executable,
you just add another extension to make it something like fred.exe.zzz
and get the recipient to strip the extra extension before use.
Guess again.Looks to me like this was a "closed" network not connected to internet
Or they just arent interested in anything executable entering their system.The IT do not seem to of not updared "virus" definitions
Guessing, as always.The infection most likley by USB or CD
You'll never know what it missed.I just use Security Essentials which you have already paid
for from Microsoft. So far always picked up and trojan/virus
as it was being download, Malware sites incucled
On Tue, 15 Feb 2011 20:29:05 +1100, keithr<keith@nowhere.com.au
wrote:
On 15/02/2011 3:05 AM, John Tserkezis wrote:
Petzl wrote:
I still had a password protected zip to try, but thought better of it.
I burnt a CD and sent it via snail mail. A three hundred year old
technology by-passed their modern day data security.
Though, truth be said, I can't really blame the admin for that, it was
probably a four-brain-celled-upper management directive. To this day I
still wonder how they manage to undo their zipper before pissing. Or
that they managed to get their pants on in the first place...
My employer's e-mail system rejects anything vaguely executable, you
just add another extension to make it something like fred.exe.zzz and
get the recipient to strip the extra extension before use.
Looks to me like this was a "closed" network not connected to internet
??The IT do not seem to of not updared "virus" definitions
The infection most likley by USB or CD
I just use Security Essentials which you have already paid for from
Microsoft. So far always picked up and trojan/virus as it was being
download, Malware sites incucled
--
Petzl
http://home.iprimus.com.au/petzl/Mono.htm
There is always a way around it as long as any file attachment isPretzl wrote
keithr<keith@nowhere.com.au> wrote
John Tserkezis wrote
Pretzl wrote
I still had a password protected zip to try, but thought better
of it. I burnt a CD and sent it via snail mail. A three hundred
year old technology by-passed their modern day data security.
Though, truth be said, I can't really blame the admin for that,
it was probably a four-brain-celled-upper management directive.
To this day I still wonder how they manage to undo their zipper before
pissing. Or that they managed to get their pants on in the first place...
My employer's e-mail system rejects anything vaguely executable,
you just add another extension to make it something like fred.exe.zzz
and get the recipient to strip the extra extension before use.
Stupid implementation. Its completely trivial to reject stuff done like that too.
Nope, not if its binned if there is any possibility that the attachment is executable.Rod Speed wrote
Pretzl wrote
keithr<keith@nowhere.com.au> wrote
John Tserkezis wrote
Pretzl wrote
I still had a password protected zip to try, but thought better
of it. I burnt a CD and sent it via snail mail. A three hundred
year old technology by-passed their modern day data security.
Though, truth be said, I can't really blame the admin for that,
it was probably a four-brain-celled-upper management directive.
To this day I still wonder how they manage to undo their zipper
before pissing. Or that they managed to get their pants on in
the first place...
My employer's e-mail system rejects anything vaguely executable,
you just add another extension to make it something like fred.exe.zzz and get the recipient to strip the extra
extension before use.
Stupid implementation. Its completely trivial to reject stuff done like that too.
There is always a way around it
Utterly mangled all over again.as long as any file attachment is allowed,
Irrelevant to what is being discussed.they are just trying to prevent attachments from auto-executing.
Like I said, theirs was much more restrictive, in that it looked withinMy employer's e-mail system rejects anything vaguely executable, you
just add another extension to make it something like fred.exe.zzz and
get the recipient to strip the extra extension before use.
Their choice.keithr wrote
My employer's e-mail system rejects anything vaguely executable,
you just add another extension to make it something like fred.exe.zzz
and get the recipient to strip the extra extension before use.
Like I said, theirs was much more restrictive, in that it
looked within the binary and worked out what the file was.
Nope.This is just way over the top,
Why should they bother ?and can be managed via other means.
Thats never the case.Back a billion years ago, the company I worked for had a minor issue
of a virus appearing on our distributed media. Thankfully, the source
wasn't our department, nor the "official" disk duplicator / machine
builder guy. Turns out, while he was on break, some other guys in
another department thought it was an easy job and thoughtfully took over.
As a result of that, an instant company-wide policy of "if you bring
media into our premises, you're out the door" was brought in.
(clearly before the unions made it impossible to fire idiots).
Some dont.At that time, I agreed with that stance, and appreciate it was the right course of action.
But that was when software was being sourced via official means and
we had no *real* need to bring our own "unofficially sourced" stuff in.
Or, where required, we had the option of writing tools ourselves
anyway - which we did on occasion.
Today however, EVERYONE uses software in some form or another.
Mindlessly silly.We have established procedures to look out for obvious clues to
infection, and have other procedures for handling the disinfection.
Preventing infection is also accounted for, while we block web
access to verified dodgy sites, users are otherwise free to
download the latest software of what they use.
Today, an outright blockage of executables - with no (electronic)
options offered, is just silly. It servers only to stop you working.
That must do interesting things to e-mail throughput. I'll keep that onekeithr wrote:
My employer's e-mail system rejects anything vaguely executable, you
just add another extension to make it something like fred.exe.zzz and
get the recipient to strip the extra extension before use.
Like I said, theirs was much more restrictive, in that it looked within
the binary and worked out what the file was.
In some areas of our company, especially in the remote support centres,This is just way over the top, and can be managed via other means.
Back a billion years ago, the company I worked for had a minor issue of
a virus appearing on our distributed media. Thankfully, the source
wasn't our department, nor the "official" disk duplicator / machine
builder guy. Turns out, while he was on break, some other guys in
another department thought it was an easy job and thoughtfully took over.
As a result of that, an instant company-wide policy of "if you bring
media into our premises, you're out the door" was brought in. (clearly
before the unions made it impossible to fire idiots).
At that time, I agreed with that stance, and appreciate it was the
right course of action.
But that was when software was being sourced via official means and we
had no *real* need to bring our own "unofficially sourced" stuff in.
Or, where required, we had the option of writing tools ourselves anyway
- which we did on occasion.
Today however, EVERYONE uses software in some form or another. We have
established procedures to look out for obvious clues to infection, and
have other procedures for handling the disinfection.
Preventing infection is also accounted for, while we block web access
to verified dodgy sites, users are otherwise free to download the latest
software of what they use.
Today, an outright blockage of executables - with no (electronic)
options offered, is just silly. It servers only to stop you working.
Did a large telco sack you Roddles????John Tserkezis wrote
keithr wrote
My employer's e-mail system rejects anything vaguely executable,
you just add another extension to make it something like fred.exe.zzz
and get the recipient to strip the extra extension before use.
Like I said, theirs was much more restrictive, in that it
looked within the binary and worked out what the file was.
Their choice.
This is just way over the top,
Nope.
and can be managed via other means.
Why should they bother ?
Back a billion years ago, the company I worked for had a minor issue
of a virus appearing on our distributed media. Thankfully, the source
wasn't our department, nor the "official" disk duplicator / machine
builder guy. Turns out, while he was on break, some other guys in
another department thought it was an easy job and thoughtfully took over.
As a result of that, an instant company-wide policy of "if you bring
media into our premises, you're out the door" was brought in.
(clearly before the unions made it impossible to fire idiots).
Thats never the case.
At that time, I agreed with that stance, and appreciate it was the right
course of action.
But that was when software was being sourced via official means and
we had no *real* need to bring our own "unofficially sourced" stuff in.
Or, where required, we had the option of writing tools ourselves
anyway - which we did on occasion.
Today however, EVERYONE uses software in some form or another.
Some dont.
We have established procedures to look out for obvious clues to
infection, and have other procedures for handling the disinfection.
Preventing infection is also accounted for, while we block web
access to verified dodgy sites, users are otherwise free to
download the latest software of what they use.
Today, an outright blockage of executables - with no (electronic)
options offered, is just silly. It servers only to stop you working.
Mindlessly silly.
Not possible given that I have never been employed by one.Rod Speed <rod.speed.aaa@gmail.com> wrote
John Tserkezis wrote
keithr wrote
My employer's e-mail system rejects anything vaguely executable,
you just add another extension to make it something like
fred.exe.zzz and get the recipient to strip the extra extension
before use.
Like I said, theirs was much more restrictive, in that it
looked within the binary and worked out what the file was.
Their choice.
This is just way over the top,
Nope.
and can be managed via other means.
Why should they bother ?
Back a billion years ago, the company I worked for had a minor issue
of a virus appearing on our distributed media. Thankfully, the
source wasn't our department, nor the "official" disk duplicator /
machine builder guy. Turns out, while he was on break, some other
guys in another department thought it was an easy job and
thoughtfully took over.
As a result of that, an instant company-wide policy of "if you bring
media into our premises, you're out the door" was brought in.
(clearly before the unions made it impossible to fire idiots).
Thats never the case.
Did a large telco sack you Roddles????
At that time, I agreed with that stance, and appreciate it was the
right course of action.
But that was when software was being sourced via official means and
we had no *real* need to bring our own "unofficially sourced" stuff
in. Or, where required, we had the option of writing tools ourselves
anyway - which we did on occasion.
Today however, EVERYONE uses software in some form or another.
Some dont.
We have established procedures to look out for obvious clues to
infection, and have other procedures for handling the disinfection.
Preventing infection is also accounted for, while we block web
access to verified dodgy sites, users are otherwise free to
download the latest software of what they use.
Today, an outright blockage of executables - with no (electronic)
options offered, is just silly. It servers only to stop you working.
Mindlessly silly.