hi all,
I have got an exclusive info for you now you can change the permissions of all your untrusted java midlets to always allowed . First apply the famous c2z patch by fca
(thanks to him for his great discovery) and then copy the two files (jtwi_r1.xpf and midp2_rp.xpf) which i am attaching here to
c:\system\data\midp2\security\policy\
And you will gain all the java permissions. Now after this you can say that symbian is completely open.
Now go to app.manager to change the permission setting of all your apps according to your will.
For your convenience i am also attaching the c2z patch file.
Note:this is only possible with the newest update of c2z patch by fca it will not work with old patch delete the old patch and apply this patch.
After applying this method you will not get any more annoying prompts like READ USER DATA or WRITE USER DATA.
note:the new c2z patch works fully with the latest version of rom patcher by zorn. This is because this c2z.rmp file contain three patches inside a single file which can only be fully interpretted by the latest rom patcher.
If any one is still having problem with this method then pm me your jwti_r1.xpf and midp2_rp.xpf files from z:\system\data\midp2\security\policy\
I will mod them for you and this the best i can do.
You can also mod the files by your self just to increase or decrease the capabilities
Firstly i will explain you some terms.
No=no file access
Oneshot=this mean that permission is needed before every act.(ask every time)
Session=this means that you have to permit permissons to every java midlet at every startup.(ask once).
Blanket=this means that no permission needed. (never ask)
To do any thing by your self you can open the midp2_rp.xpf file and cheak the capabilities for different acts read user data, write user data, connectivity.network connectivity etc. Different policy is defined for different domains MFD=manufacture domain
Opd, ttpd etc
At the bottom of the page the policy is defined for the untrusted midlets ie midlets without any cert.
Here you will see the permissions for different capcilities of unsigned java apps.
Here the word function group refers to function like( read user data, write user data) for example
function group bindings:"local connectivity"
Means the ability to use local connectivity
Under it there would be two options ie
Default means the capability which you want to give to untrusted apps just after Installation
If default=Blanket it means always allowed
Which is the highest abllity granted to any midlet but if you want to provide full acess from default then the line beneath it ie maximum which means the maximum access you want to provide untrusted midlets for local connectivity must also be at Blanket because how can you give always allowed access to any domain when its maximum ability is one shot ie ask every time.
i have made the modifications so you don,t need to do any thing just copy and paste the attached file.
How it works.
1.Why you need the c2z patch?
Efsrv.dll is the file which collects the info from the z:\drive and provide it the phone to process it. When fca realized that making these small small patches would not help him to do what he want because most of the files in the z drive are not present in rom, and the other patches except the c2z patch cover only a single file he tried to patch the big fish ie the EFSrv.dll and programmed this file to cheak any required file requested from any phone process first from c drive and the from z drive. Mean if any file is present in c drive at the same root as it is in z drive then the phone will prefer the c drive. Thanks to fca for his excellent work.
1.Why i recomend to use c2z patch instead of patching the dll file ie midpsecuritypolicyv2.dll this is because in simple words you can say the midptosecuritypolicyv2.dll is non_patchable file. You can,t patch this file in fp1 phones as in my nokia 5700 the rom patcher gives an error when tried to patch that file because in my phone and some other fp1 phones it cannot find the .dll file because it is stored in the z drive but does not comes under rom just like most of the similar processes in these phones maybe in some phones the rom patcher can patch this file but it would not be able to force the phone to use the function
epoc:allocshadowpage
Mean use patched file insted of real file because the control is in the hands of Efsrv.dll file.
so most easiest way to escape from this mess was to wait for fca to release another alpha version of c2z patch which he did today. There are no limitations of prefp1 or fp1 so you would be able to use it on any 3rd edition phone and change the permisions.
Warning:According to fca this patch is still an alpha version and the testers may damage their phone so use this at your own risk.
c2z patch removed since it is already posted HERE - swankyleo
Attachment updated.
Some restriction were present on ssl port, http port, socket port.
The untrusted midlets only had access to c:\data now you can access any folder on c:\drive.
Change log. 12 may 2008.
1.ssl port restriction, socket post restriction and http port restriction removed. Now you would be able to use all network ports just like MFD(manufacture domain)
2.Full access to all folders on c:\ and e:\ provided..