RE: Xslt protect with password

This appears to boil down to the same problem countless people have
been trying to solve using DRM, and so far have failed to do, as once
you give the XSLT to a third party, they will need the clear-text in
able to run it through an XSLT processor. You could wrap both the XSLT
and a processor into compiled code, making this somewhat more complex,
but certainly not impossible for a person intend on extracting
determining the inner workings of your code.

The alternative would be to keep the XSLT on a server under your
control, and provide the transformation as a service.

It appears the problem is "I do not trust the vendor to play nice with
my code" and I suggest, instead of trying a technological solution
(which might be unacceptable to your vendor for various reasons), the
proper way to resolve this is a good contract with the vendor on what
it can do with the code and what not. The terms of your contract will
probably depend on the level of "general purposeness" versus "tailor
made for vendor" of your code, as well as the level of "vendor
lock-in" for future support on the code you want to achieve.

Hi Jeroen,

If, i am developing xslt for vendor(third person)
and I do not want that anybody open my xslt and see the logics.

I want that vendor can use xslt file without open it.

Thanks
Praveen

-----Original Message-----
From: jeroen@xxxxxxxx [mailto:jeroen@xxxxxxxx]
Sent: Monday, August 30, 2010 2:44 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Xslt protect with password

No answer will be forthcoming without some further explanation of the use
case in which you want to "protect an XSLT with a password". What is the
problem you want to solve; what is the scenario; against what adversary do
you want to protect, why would you use the "password"
solution, etc....

Jeroen.

Quoting "Ramkumar.V" <ramkumar.v@xxxxxxxxx>:

If we get answer for this question, it will be great. I am expecting
long for the right solution.

Regards,

Ram Kumar