Update On PlayStation Network: Hacked

It’s been about 4 days that the PlayStation Network has been down.  Sony official admits that its been three days; Whatever!   Last night our friends at Sony admitted to being hacked which is why they chose to take-down the PlayStation Network along with other services.

To Quote what was written on PlayStation blog:

Posted by Patrick Seybold // Sr. Director, Corporate Communications & Social Media
“An external intrusion on our system has affected our PlayStation Network and Qriocity services. In order to conduct a thorough investigation and to verify the smooth and secure operation of our network services going forward, we turned off PlayStation Network & Qriocity services on the evening of Wednesday, April 20th. Providing quality entertainment services to our customers and partners is our utmost priority. We are doing all we can to resolve this situation quickly, and we once again thank you for your patience. We will continue to update you promptly as we have additional information to share.”

I am glad Sony has come forward and admitted this to the public, however the question I now ask is… To what extent were they hacked?  Is my account info safe?


PlayStation Network Down (Again)

It would seem once again Sony’s PlayStation Network is down again. After trying many of the online tips and even going as far as to boot my router (problem is so not my router) this issue persists.

It seems that Sony has responded to the issue and acknowledges there are ongoing problems, but offer not details to what this problem is or an ETA for its resolution.  Even attempts to log into their website indicate they are under some site maintenance and the server (WHAT SERVER) is down.

The error code provided on the console “80710A06” also uninformative.


Update 1: PSN is acknowledging on its EU blog that the network outage may be a result of “the possibility of targeted behavior by an outside party.” Still no ETA for when services will be restored.

Update 2: PSN is now reporting that the network may be offline for “a full day or two.”


Facebook – Up, Up, Down, Down

It seems that Facebook is down once again. After a while of troubleshooting my computer, then my home network. Its official! It’s not my side where the problem exists.

Faced with this I took a walk over to the folks at to checkup on the up-time of Facebook… It seems they are indeed having issues and I am not the only one experiencing it.


More updates:


Configure Firefox to use SSH tunnel for DNS

If you are using SSH to tunnel your web traffic, to keep your information private, you might be vulnerable to a DNS man-in-the-middle attack.  If your DNS requests are not tunneled, the operator of the hostile (or locked down) network can still see where you are navigating to on the web when your client makes DNS requests to resolve hostnames to IP addresses. For these reasons (and for many others), it’s a good idea to tunnel DNS through your SSH tunnel too.  This can be done very easily in Firefox.

In the Firefox URL address bar, enter “about:config“.
In the Filter text field, enter “network.proxy.socks_remote_dns“.
Double-click “network.proxy.socks_remote_dns” to set the value to true.

By |How-To, Technical|Comments Off on Configure Firefox to use SSH tunnel for DNS

How I got my eth0 back

After a recent Ubuntu Linux (server) installation inside in a virtual machine, I decided to move the virtual machine to new a new host where I can run it.  After the move I noticed that I could no longer connect to my system via the IP I had assigned.  So the story begins.

With the discovery that I no longer had network connectivity, I did an ‘ifconfig’ and noticed that my eth0 was missing.  So, I tried to force it to start by issuing the command ‘ifup eth0’ and go the following error:

eth0: ERROR while getting interface flags: No such device…
SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth0

I did some searching, as I have run into this issue in my past and could not remember for the life of me what I needed to do to correct this problem (the right way).  The method I used in the past was to edit /etc/network/interfaces and change iface eth0 inet (static or dhcp) to eth1  This would change my static or dynamic settings to use the new interface…  This is not what I wanted to; “lazy admin approach”.

What I did do is… wait! Here is some background info:  When a Virtual Machine starts up, it generates a new MAC address and a new UUID for the guest system. My system had already known of a MAC address and thus made a new one.

Back to what I did to correct my problem

Locating the file /etc/udev/rules.d/70-persistent-net.rules, I removed the former MAC address info and modified the new one, changing the existing eth1 to eth0, and issued a restart

# PCI device 0x8086:0x100f (e1000)
SUBSYSTEM==”net”, DRIVERS==”?*”, ATTRS{address}=”[bad mac]”, NAME=”eth0″

By |How-To, Technical|Comments Off on How I got my eth0 back
Secured By miniOrange