See the following documentation for more information. You can configure Reader to allow writing to a specific directory by making a Windows registry edit and creating a custom policy, as documented in section 2.2.6: http://learn.adobe.com/wiki/download/attachments/64389123/AcrobatApplicationSecurity.pdf?v ersion=1
Yes what but what about the AddRule?
What about writing a broker Process as well in order to make the plugin work?
what about the follwoing :
If your plug-in uses the Acrobat SDK APIs provided to you for file I/O, etc. then Reader X will handle all the brokering for you and you won’t even need to worry about the sandbox… unless you try to reference objects outside the trusted areas. If you make direct Windows OS API calls which fall into low rights categories, writing to the registry, for example, you will need to create your own broker and a sample in the new SDK will show you how.
I used the new SDK but the errors stayed.
where are the samples?
My understanding is that there is no AddRule() API. Also even native Windows API calls work if you try to write to a trusted area (like %TEMP%). Even using Adobe API-s for file IO won't help when trying to write to a non-trusted area. There are no samples in the SDK and the only thing that works is ProtectedModeWhiteList.txt.
This is just based on my experience with the Sandbox while developing a reader plugin, wrote a bit more about it at our blog: http://www.perfectline.ee/blog/adobe-reader-protected-mode
I've read ur post on your blog and replied to it but i didn't see my reply being posted.
The issue with us is that whenever we open Adobe Reader our plugin opens "myApp.exe".
with protected mode on, it gives an exception: shell execute exeception cannot launch "myApp.exe" (something like that)
and in the protected mode Log on, i can see that we need to use the whitelist policy " process_All_exec"
using that pointing to our "myApp.exe" this removes the initial error but tries to open "myApp.exe" from C:\Windows\sytem32 which is weird because "myApp.exe" is in programFiles.
and in your blog i read something dangerous "The general rule seems to be: don’t try to talk to other processes " if so, why do we have process_all_exec ?
i am kinda turning in looops in all the forums... and no real solution, no samples..
If you're developing for Adobe Reader then you will have a Reader Integration Key, and support is part of that package. You should refer any Reader plugin development questions to the contact provided when your key was supplied.
isn't Adobe Reader for Free?
is this License for Developping within Reader?
is this license to be used for each user we give the plugin to? or just for develooppment?
we have Acrobat Key, does that work? or this is something related directly to Reader?
Please if you can provide me with more info about this and send me some links if possible so that i know what to do and how to proceed.