| 02:28.20 | *** join/#n9 ToAruShiroiNeko (~White_Cat@wikimedia/ToAruShiroiNeko) |
| 02:28.56 | *** join/#n9 ToAruShiroiNeko (~White_Cat@wikimedia/ToAruShiroiNeko) |
| 02:39.16 | *** join/#n9 ToAruShiroiNeko (~White_Cat@wikimedia/ToAruShiroiNeko) |
| 03:06.15 | Dhraakellian | damnit... openmode prevents device lock? |
| 03:06.18 | Dhraakellian | fail |
| 04:35.28 | *** join/#n9 auenf (David@171.72.233.220.static.exetel.com.au) |
| 06:10.24 | DocScrutinizer05 | the wonders of aegis |
| 06:10.40 | DocScrutinizer05 | and the dang M-Shield |
| 06:11.46 | DocScrutinizer05 | N9 is a HS device. There's no true open mode unless Nokia would provide the private key for signing 1st stage bootloader with it |
| 06:15.09 | DocScrutinizer05 | which is sth Nokia never would do. They offered that 2nd stage (signed) bootloader will not refuse to load kernels that are not signed by Nokia, but it switches M-Shield into a "tainted mode" while loading such unsigned kernel. This means that certain areas which are considered relevant for device security as Nokia defines it are no longer accessible - lockcode affected by this as well as some account credentials etc |
| 06:16.18 | DocScrutinizer05 | the whole thing allegedly been designed to protect users from whatever, actually it been a terribly messed up implementation of TrustedComputing and only serves one purpose |
| 06:16.22 | DocScrutinizer05 | ~aegis |
| 06:16.22 | infobot | http://www.developer.nokia.com/Community/Wiki/Harmattan:Developer_Library/Developing_for_Harmattan/Harmattan_security/Security_guide , or "The purpose of this framework is: ... to make sure that the platform meets the requirements set by third party software that requires a safe execution environment.", or http://en.wikipedia.org/wiki/Trusted_Computing#Criticism, or http://en.qi-hardware.com/w/images/1/10/ME_382_LockedUpTechnology2.gif |
| 06:17.43 | DocScrutinizer05 | IOW ensure that nobody can record that video stream you're watching, ensure that after 4 weeks you can't listen to that song and read that e-book anymore that you "leased" for 4 weeks |
| 06:21.27 | DocScrutinizer05 | btw N900 also is a HS device, but there 1st stage bootloader drops out of secure mode already, per default. So nothing in whole maemo5 is using M-Shield protected stuff, and the only thing you can't hack to your liking is xLoader 1st stage bootloader |
| 06:25.43 | DocScrutinizer05 | since the only three relevant tasks of xLoader are: "debouncing" the powerbutton (switch off immediately again if power button gets not held pressed for a minimum time to power up the device), loading 2nd stage bootloader, and optionally ensuring that 2nd stage BL is correctly signed, and the latter is not enabled in N900 xLoader, it's not really bad that you can't hack xLoader of N900 |
| 06:46.12 | *** join/#n9 ToAruShiroiNeko (~White_Cat@wikimedia/ToAruShiroiNeko) |
| 09:56.06 | *** join/#n9 ToAruShiroiNeko (~White_Cat@wikimedia/ToAruShiroiNeko) |
| 10:35.58 | *** join/#n9 ToAruShiroiNeko (~White_Cat@wikimedia/ToAruShiroiNeko) |
| 10:36.45 | *** join/#n9 fredy (~fredy@snf-535807.vm.okeanos.grnet.gr) |
| 12:22.28 | *** join/#n9 lordross (~lordross@kokiche.atia.com) |
| 15:26.00 | *** join/#n9 ToAruShiroiNeko (~White_Cat@wikimedia/ToAruShiroiNeko) |
| 20:50.52 | *** join/#n9 ToAruShiroiNeko (~White_Cat@wikimedia/ToAruShiroiNeko) |
| 22:30.28 | Dhraakellian | heh |
| 22:31.37 | Dhraakellian | wouldn't mind getting the sailphone, were it smaller, 4G- (or even 3.5G-) capable in the US, etc |
| 22:32.38 | Dhraakellian | so I think what I'll probably do is look at compatibility lists and hunt down an Android phone with Cyanogen and Mer ports that are doing fairly well |
| 22:55.58 | DocScrutinizer05 | sounds like a plan |
