[PS3 ] PSN SOE被駭是內賊所為?
http://www.ps3hax.net/2011/05/psn-and-soe-attacks-an-inside-job/
According to online reports, Sony had fired ~200 employees from SOE a
few days before the PSN massive attack which led to the compromise of
user personal information. A 2 week notice was handed out on March
31st, 2011 which gave whomever enough time to think, plan and act on
the PSN attack – and would have all the clearance to easily to do it
. Whats even worse is that if it DID turn out to be a inside job then
the ex-employee could potentially have the tools to un-hash the stolen
passwords and possibly even have the tools/resources to decrypt the
important information such as your credit card numbers.
根據網路新聞報導,SONY在 PSN與 SOE被駭造成大量個資外洩的前幾天一口氣炒
了一盤 200人左右的大盤魷魚。SONY在三月底發出資遣通知,剛好給了這些人一
段思考的時間,也許他們就趁這段時間決定拿攻擊 PSN作為被資遣的報復,而且
這些人在職位或是技術上都是沒問題的。若以上推論屬實,則事態可能更進一步
惡化因為這些人很可能有能夠對雜湊過的密碼資料進行「反雜湊(*1)」的工具,
也許他們還能把SONY聲稱有加密過的信用卡資料進行解碼。
******
*1 雜湊函數(hash function) 通常是多對一函數,所以沒有確切的反函數,但
這邊沒有人看過SONY是怎麼實做他們家的雜湊函數,也許跟他們的亂數函數
一樣簡單也說不定,比如說:
輸入資料 → 跟某個金鑰進行 XOR運算 → 雜湊後的資料
那 XOR運算是一對一運算,反函數也是使用同一把金鑰的 XOR運算,所以有
雜湊後的資料 → 跟同一個金鑰進行 XOR運算 → 雜湊前的資料
XOR 布林運算邏輯如下:
true XOR true = false false XOR true = true
true XOR false = true false XOR false = false
--
○ ____ _ _ _ _ ____ _ _ ____ _____ ____
。 ★(_ _)( \( )( \/ )( ___)( \( )(_ _)( _ )( _ \
o _)(_ ) ( \ / )__) ) ( )( )(_)( ) / ● ‧
(____)(_)\_) \/ (____)(_)\_) (__) (_____)(_)\_) ★
o
--
※ 發信站: 批踢踢實業坊(ptt.cc)
◆ From: 122.117.54.160
推
05/03 09:20, , 1F
05/03 09:20, 1F
→
05/03 09:21, , 2F
05/03 09:21, 2F
推
05/03 09:24, , 3F
05/03 09:24, 3F
→
05/03 09:26, , 4F
05/03 09:26, 4F
→
05/03 09:27, , 5F
05/03 09:27, 5F
推
05/03 09:48, , 6F
05/03 09:48, 6F
推
05/03 10:51, , 7F
05/03 10:51, 7F
→
05/03 10:51, , 8F
05/03 10:51, 8F
→
05/03 10:52, , 9F
05/03 10:52, 9F
推
05/03 12:57, , 10F
05/03 12:57, 10F
推
05/03 13:09, , 11F
05/03 13:09, 11F
推
05/03 13:37, , 12F
05/03 13:37, 12F
→
05/03 13:37, , 13F
05/03 13:37, 13F
→
05/03 13:38, , 14F
05/03 13:38, 14F
推
05/03 17:54, , 15F
05/03 17:54, 15F
→
05/03 23:57, , 16F
05/03 23:57, 16F
→
05/03 23:58, , 17F
05/03 23:58, 17F
→
05/04 00:23, , 18F
05/04 00:23, 18F
→
05/04 00:23, , 19F
05/04 00:23, 19F
→
05/08 03:02, , 20F
05/08 03:02, 20F