XUL Talk:Remote XUL bugs
(Jocelyn Raymond) What I would like to see for (our intranet) remote XUL application is the ability to add in the preference "signed.applets.codebase_principal_support" (or perhaps a specific privilege such as XPConnect) a domain[/path] (where [/path] means is optional).
Thus, if I could add this preference, it would essentially mean "Any XUL application coming from www.mydomain.com/path/to/my/app is granted XPConnect". Of course, this is not useful for anyone that wish to develop for an unknown audience (such as the internet), but only for secure controlled intranet. Would something like this be feasible? Would it be secure enough?
Of course, I think the best is to sign our remote XUL application which I did without success (i.e. the signed code was treated as if it was invalid so I must have done something wrong along the way). There is much more I would like to say but not sure this is the appropriate place.
(Hans Harder) Signing remote XUL applications sounds nice, but how about dynamic remote XUL application, in other words how do I sign XUL applications which are dynamicly generated by remote perl scripts ?
(Enn)"signed.applets.codebase_principal_support" is a debugging preference and should never be set on a enduser's machine.