cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jorg Heymans ...@domek.be>
Subject Re: AW: How to protect a Cocoon project
Date Wed, 22 Oct 2003 09:30:30 GMT
have look at the wiki (or google because the wiki seems to be down for 
the moment) for xsltc, a stylesheet compiler.

wiki.cocoondev.org


Derek Hohls wrote:

> Jorg
>  
> Are there guidelines for how to do the precompiling
> of XSL *and* XSP?
>  
> Thanks
> Derek
>
> >>> jh@domek.be 22/10/2003 10:34:15 >>>
> you can precompile the stylesheets to classes so at least it's not
> plaintext anymore. Ultimately that's what cocoon does.
> Put your XML into a database or something.
> I don't know how you would go on about masking the sitemap.
>
> jorg
>
> Jörn Heid wrote:
>
> >It's about a demo (with an installer).
> >I can't say: Before you install, please create a new user and forget the
> >password of him :)
> >
> >-----Ursprüngliche Nachricht-----
> >Von: news [_ mailto:news@sea.gmane.org] 
> <mailto:news@sea.gmane.org%5D>_ Im Auftrag von Olivier Billard
> >Gesendet: Mittwoch, 22. Oktober 2003 09:54
> >An: _users@cocoon.apache.org <mailto:users@cocoon.apache.org>_
> >Betreff: Re: How to protect a Cocoon project
> >
> >
> >Hi Joern,
> >
> >Isn't it the goal of filesystems, to protect file from beeing read by 
> non
> >authorized
> >persons ? It's possible with WinNT, 2000, XP, and of course Unix-like 
> OSes.
> >Just give the right rights to the right persons ;)
> >
> >--
> >Olivier BILLARD
> >
> >
> >On 22/10/2003 09:47, Jörn Heid wrote:
> >
> >
> >>Hello.
> >>
> >>I want to give my customer a demo of my Cocoon based application which
> >>runs with Jetty on their local machine. But the problem is everybody
> >>can see the internals of the app. All the pipelines in sitemap.xmap,
> >>all XSL and XML. It can be used to find backdoors in the sitemap for
> >>example.
> >>
> >>So the question is, how to protect files from being read directly.
> >>
> >>A solution would probably be to encrypt (for example via XOR) all the
> >>files. After that, Cocoon (Jetty) has to be started with modified
> >>Java-IO classes (via bootclasspath).
> >>
> >>Does anybody know which classes have to be changed or if there's
> >>somebody who has done something like that...
> >>
> >>
> >>JOERN_HEID
> >>
> >>
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: _users-unsubscribe@cocoon.apache.org 
> <mailto:users-unsubscribe@cocoon.apache.org>_
> >For additional commands, e-mail: _users-help@cocoon.apache.org 
> <mailto:users-help@cocoon.apache.org>_
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: _users-unsubscribe@cocoon.apache.org 
> <mailto:users-unsubscribe@cocoon.apache.org>_
> >For additional commands, e-mail: _users-help@cocoon.apache.org 
> <mailto:users-help@cocoon.apache.org>_
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: _users-unsubscribe@cocoon.apache.org 
> <mailto:users-unsubscribe@cocoon.apache.org>_
> For additional commands, e-mail: _users-help@cocoon.apache.org 
> <mailto:users-help@cocoon.apache.org>_
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
> Mailscanner thanks transtec Computers <http://www.transtec.co.uk/> for 
> their support. 



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message