So everybody is complaining about bad software patents, but are there any good software patents which are actually doing something tricky/interesting worth patenting?

As somebody who left the network / sysadmin business before the attacks started from the inside (send enough malware to everybody inside a company and you will get lucky at a certain moment), how would you protect it best?

Airgap it (or properly firewall it), and people will complain about the costs of duplicate infrastructure, remote support from vendors will be a pain etc.

Monitor the network and spot anomalies, it's a hard task but could be the way to go. Except that you need skilled people there (not saying that there aren't, my experiences in a TAC shows that there aren't many).

Letting the attackers waste time in a honey-pot while your own network is isolated? At least you learn from it and you give them a false sense of victory.

What is wisdom, any thoughts?

I'm waiting for the sequel: More time.

(before anybody flames, I follow it every couple of days via http://geekwagon.net/projects/xkcd1190/).

Why was there no self-destruct happening?
Where was the guy with his finger on the "press here to explode rocket" button?

Like AS numbers, network blocks etc?

Oh wait, they don't make money out of that will be thrown out?

They said that in the article: It gets sold to a carrier which is not querying the US version of the Stolen Phone database.

We need something like DNS but then for IMEI numbers. .imei :-)

Mental note: Don't use these public chargers anymore...
(Google for "iphone charging point airport")

http://risky.biz/byodauscert

PRESENTATION: BYOD in government, a high level talk
Handy talk for CIOs and CSOs...

Start the discussion 0 Comments
May 23, 2013 --

The following is a recorded presentation from AusCERT. It's by Al Blake, the Chief Information Officer of the Department of Sustainability, Environment, Water, Population and Communities. In it he talks about BYOD, basically, from an Australian government perspective. It's not an overly technical talk, but it is a good overview of what a CIO like him has to consider when allowing staff to use their own devices in a heavily regulated environment.

"Only 50 were ever produced, this being the second example known to exist."

If there are 50 produced, then there are 50 known to exist.

Call me old-fashioned, but I prefer a proper Makefile which only compiles the files required and which separates between the build and install phase.

And it rated for people not living in heavily American culturally influenced and non native English speaking countries that they all had a lower IQ.

Oh wow.
Somebody who actually understands what unions are about. Too bad that the rest of the people here don't understand the whole of the concept about it.

Put it between the two routers[*] which are having a problem and actually see what the packets are.

(Of course you still need the skills to read the packets, but that is not a hardware issue :-)