[Windows Phone 7 Development and Hacking] :
Because they have a lack of functions, more can be done like buildin certificate installer and a all in one tool like this great work is apreciable.

Simple, he has just to consider to use common functions since he has already priviledges and can test by feedback, or i could just make an special version of emulator with same priviledges so each developper could test in same conditions or i could find 10 other way you didn't thought about because of instinctive reaction ;):) (sorry I don't like phrases which don't mean another thing than "could you explain me how... " without thinking before but i'm working on that^^)

thanks, yes all the difference is that i can edit all I want and build in rom after. I don't believe nobody has achieved to unlock the bootloader or found another way to flash modified roms. All wp7 community lose a lot since only few things are developed without this before.

Some other tools works but I think yours should be better and all-in-one and thought it could not take too much time to replace functions by default api's access, but if it's not case I understand, it's not a problem :)

For security you're right and we have discussed of that in thread before I was changing rules, but most of responses were open the case ^^ it makes me thought that when on wm6 nobody was thinking about that, it appears only after all security are here and limit utilisation. Yes an UAC would be great of course, but I'm not developper...

For the rest I think I should open a thread to describe that since I see a lot of people who are trying on other devices and it could help. The advantage of building rom is that I can do a lot of tests. So things like that should be interesant:

- Don't care about .policy.xml files they just here to make BasePolicy.xml and PolicyMeta.xml when building (official way not ours on hd2). Same for these files they just give accountdb.vol and policydb.vol but don't update at boot so it's useless.

- Use policyloader as I know don't give result since it has not the priviledges to update anything except when updating by zune, but possible there is a way

- you can edit accountdb.vol and policydb.vol under WM6.5 with database tools which use poom. I've only edited policydb.vol which contain rules but account gave me the rules.

- accountdb countain 2 things: a list of all accounts and you can see a number associated. a list of membership (what account is the member of what whith these numbers) so you can easily trace a cartography of memberships.

- policydb can be edited too but rules are in binary datas, so not interessant, I've modified all in hex. for that I've study the format of rules in hex. for exemple the number of account I was talking about, you put it in hex, after in little endian and it's what you find in binary rules. same for priviledges (you can find masks which apply on each namespaces in BasePolicy.xml)

In practice it's not very difficult (more difficult to discover how it works) but takes times to change manually rules, a simple tool or an updated program for .vol files which could traduce binary data in comprehensible form would be great^^

Regards

PS: for taskhost under TCB: it's not rally like that, I had another vision. Different because you must search a way ( and other who search root too) to gain PCB priviledges and In HD2 I can change rules themeselves. So I've don't changed the membership system to avoid problems. Accounts don't run under TCB, I've just taken priviledges from TCB and other high_groups and gave them to everyone_group. Taskhost and pcb are both (with intermediates) member of this group so they acquire the same priviledges. in fact all has the same priviledges (and more) than TCB had before but are not under TCB in terms of membership. it's funny no?