70w ago - Following up on the previous revisions, this weekend PlayStation 3 hacker naehrwert has updated SCETool to version 0.2.1 which now includes full PS3 SELF file support.

Download: PS3 SCETool v0.2.1 / ZLib1.dll File (Required)

To quote: scetool 0.2.1 - SELFs should be fully supported now.

Finally, from the included ReadMe file:

scetool 0.2.1 (C) 2011-2012 by naehrwert

Notes:

• zlib is required to use scetool.
  
• 'sdk_type' was changed to 'revision' in data/keys.
  

Keyfile format:
[keyname]
type={SELF, RVK, PKG, SPP, OTHER}
revision={00, ..., 18, 8000}
version={..., 0001000000000000, ...}
self_type={LV0, LV1, LV2, APP, ISO, LDR, UNK_7, NPDRM}
key=...
erk=...
riv=...
pub=...
priv=...
ctype=...

USAGE: scetool [options] command
COMMANDS           Parameters       Explanation
 -h, --help                         Print this help.
 -k, --print-keys                   List keys.<br...

123w ago - Today Waninkoko mentioned he agrees with Hermes and Naima's recent views on the discussion of PS3 NPDRM SELFs, how their encryption differs, GeoHot and what PS3 Firmware 3.60 may bring to combat PlayStation 3 hackers.

Below is a rough translation from Elotrolado, to quote:

"Let's see... speaking of bans and stories...

I like to play magic, astrology and / or fortune-telling, so what is written below is not from any of the three.

The first consequence that will bring the firmware 3.60 is that all applications signed with the utility in make_self_npdrm created by Geohot stop working.

Oh Wait! That's not what I had said 'sceners' by the mouth of all are phrases like 'are key signed with Sony, you can not do anything'

That would be true if they were well signed, but the truth is that they are not.

Without going into deep detail about how the Sony npdrm I will explain briefly, when Sony makes the process to generate an executable npdrm valid, generates a random key pair unique for each executable, those keys are encrypted...