---------- Forwarded message ---------- From: Benson Margulies <bimargul...@gmail.com> Date: Sun, Mar 1, 2009 at 8:46 PM Subject: Re: Usage model - no source XML, just api calls To: Dave Brosius <dbros...@mebigfatguy.com>
This whole story doesn't make sense entirely from a security standpoint. Let's see if I've got this straight: people you don't trust to look at the data are allows to write and render stylesheets. The JVM is connected to a database full of data they aren't allowed to see in detail, only in summary. You are concerned that they will go fishing for functions that would allow them to grab what they cannot see. >From a security standpoint, I'd say that you need some more architecture here. Like, put the sensitive data behind a web service, require authentication, and have the web service API be just the allowed aggregating functions. Then turn them loose on Xalan/xslt, secure in the knowledge that all they can do by being cute is shoot themselves in the feet. On Sun, Mar 1, 2009 at 7:58 PM, Dave Brosius <dbros...@mebigfatguy.com> wrote: >>> So is there any way of limiting which java classes >> >> can be accessed as extensions? > > > I doubt it. > > I'm assuming you have a set of classes that provide all the secure > information, however. If a user altered the style sheet, added their own > extension functions, don't they still have to add some point then call your > classes to get the secure information, and therefore, isn't that the point > were you > can enforce security. Perhaps, i'm still not grasping the entirety of your > problem. > > ----- Original Message ----- From: "Johan Zxcer" <nab...@zurahn.com> > To: <xalan-j-users@xml.apache.org> > Sent: Sunday, March 01, 2009 4:39 PM > Subject: Re: Usage model - no source XML, just api calls > > >> >> Yes, extensions are where I started and provide exactly what I need - >> except >> that I couldn't find any mechanism for limiting the set of java classes >> that >> are available as Xalan extensions. Given that a style sheet is editable >> by >> a non-privileged user, it would be a glaring security hole that isn't >> mentioned in the xalan docs, the below link, or any other examples of >> extensions I've found. So is there any way of limiting which java classes >> can be accessed as extensions? >> >> Thanks for your patience.. >> >> johan >> >> >> Dave Brosius-2 wrote: >>> >>> Perhaps xalan extension functions are what you are after. >>> >>> http://www.ibm.com/developerworks/library/x-xalanextensions.html >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Usage-model---no-source-XML%2C-just-api-calls-tp22264025p22278384.html >> Sent from the Xalan - J - Users mailing list archive at Nabble.com. >> > >
