You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Chad La Joie <la...@itumi.biz> on 2012/02/06 13:17:31 UTC

Validate templates before use

Is there a way to "validate" a template prior to using it?  I'd like
to check that some user supplied templates are, at least, parsable
during system startup.

Thanks.

-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Re: Validate templates before use

Posted by Christopher Townson <ch...@gmail.com>.
this was also mentioned in a recent thread, which may be what you are
looking for:

http://code.google.com/p/velocity-validator/

Chris

On 6 February 2012 15:16, Chad La Joie <la...@itumi.biz> wrote:
> On Mon, Feb 6, 2012 at 10:14, Nathan Bubna <nb...@gmail.com> wrote:
>> Pre-validating templates would fall in the "advanced uses" category,
>> making it much more reasonable to interact with Template. :)
>
> Fair enough.  :)
>
> --
> Chad La Joie
> www.itumi.biz
> trusted identities, delivered
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
> For additional commands, e-mail: user-help@velocity.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Re: Validate templates before use

Posted by Chad La Joie <la...@itumi.biz>.
On Mon, Feb 6, 2012 at 10:14, Nathan Bubna <nb...@gmail.com> wrote:
> Pre-validating templates would fall in the "advanced uses" category,
> making it much more reasonable to interact with Template. :)

Fair enough.  :)

-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Re: Validate templates before use

Posted by Nathan Bubna <nb...@gmail.com>.
Pre-validating templates would fall in the "advanced uses" category,
making it much more reasonable to interact with Template. :)

On Mon, Feb 6, 2012 at 7:07 AM, Chad La Joie <la...@itumi.biz> wrote:
> Thanks, thats what I was looking for.  After my last email about the
> Template object I wasn't sure if I should really be calling
> getTemplate() or not.
>
> On Mon, Feb 6, 2012 at 09:58, Guillaume Polet <gu...@gmail.com> wrote:
>> I would go for the fundamentals of the developer guide:
>> http://velocity.apache.org/engine/releases/velocity-1.7/developer-guide.html
>>
>> // If not done yet, init an engine (here the one of the singleton pattern
>> but there is a non-static call that you can do if you don't use the
>> singleton pattern engine)
>> Velocity.init();
>>
>> Template template = null;
>> try {
>>  // Call getTemplate will automatically look up the template and parse it.
>>  template = Velocity.getTemplate("mytemplate.vm");
>> } catch( ResourceNotFoundException rnfe ) {
>>   // This should not happen in your case (although it could)
>> } catch( ParseErrorException pee ) {
>>   // Well pretty obvious that the template is not correct
>> } catch( MethodInvocationException mie ) {
>>   // I don't remember in which case this exception is thrown.
>> } catch( Exception e ) {
>> }
>>
>>
>> Cheers,
>> Guillaume
>>
>> Le 6/02/2012 15:44, Chad La Joie a écrit :
>>
>>> On Mon, Feb 6, 2012 at 09:41, sebb<se...@gmail.com>  wrote:
>>>>
>>>> Just because it's parseable does not mean it's safe to use ...
>>>> allowing an end-user to provide a template without manual checking
>>>> sounds like a recipe for inviting exploits.
>>>
>>> There's nothing I can do about that.  If the user wants to write a
>>> template that exploits their own system, that's up to them.  I'm just
>>> trying to provide what checking I can at startup time.
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
>> For additional commands, e-mail: user-help@velocity.apache.org
>>
>
>
>
> --
> Chad La Joie
> www.itumi.biz
> trusted identities, delivered
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
> For additional commands, e-mail: user-help@velocity.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Re: Validate templates before use

Posted by Chad La Joie <la...@itumi.biz>.
Thanks, thats what I was looking for.  After my last email about the
Template object I wasn't sure if I should really be calling
getTemplate() or not.

On Mon, Feb 6, 2012 at 09:58, Guillaume Polet <gu...@gmail.com> wrote:
> I would go for the fundamentals of the developer guide:
> http://velocity.apache.org/engine/releases/velocity-1.7/developer-guide.html
>
> // If not done yet, init an engine (here the one of the singleton pattern
> but there is a non-static call that you can do if you don't use the
> singleton pattern engine)
> Velocity.init();
>
> Template template = null;
> try {
>  // Call getTemplate will automatically look up the template and parse it.
>  template = Velocity.getTemplate("mytemplate.vm");
> } catch( ResourceNotFoundException rnfe ) {
>   // This should not happen in your case (although it could)
> } catch( ParseErrorException pee ) {
>   // Well pretty obvious that the template is not correct
> } catch( MethodInvocationException mie ) {
>   // I don't remember in which case this exception is thrown.
> } catch( Exception e ) {
> }
>
>
> Cheers,
> Guillaume
>
> Le 6/02/2012 15:44, Chad La Joie a écrit :
>
>> On Mon, Feb 6, 2012 at 09:41, sebb<se...@gmail.com>  wrote:
>>>
>>> Just because it's parseable does not mean it's safe to use ...
>>> allowing an end-user to provide a template without manual checking
>>> sounds like a recipe for inviting exploits.
>>
>> There's nothing I can do about that.  If the user wants to write a
>> template that exploits their own system, that's up to them.  I'm just
>> trying to provide what checking I can at startup time.
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
> For additional commands, e-mail: user-help@velocity.apache.org
>



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Re: Validate templates before use

Posted by Guillaume Polet <gu...@gmail.com>.
I would go for the fundamentals of the developer guide:
http://velocity.apache.org/engine/releases/velocity-1.7/developer-guide.html

// If not done yet, init an engine (here the one of the singleton pattern but there is a non-static call that you can do if you don't use the singleton pattern engine)
Velocity.init();

Template template = null;
try {
   // Call getTemplate will automatically look up the template and parse it.
   template = Velocity.getTemplate("mytemplate.vm");
} catch( ResourceNotFoundException rnfe ) {
    // This should not happen in your case (although it could)
} catch( ParseErrorException pee ) {
    // Well pretty obvious that the template is not correct
} catch( MethodInvocationException mie ) {
    // I don't remember in which case this exception is thrown.
} catch( Exception e ) {
}


Cheers,
Guillaume

Le 6/02/2012 15:44, Chad La Joie a écrit :
> On Mon, Feb 6, 2012 at 09:41, sebb<se...@gmail.com>  wrote:
>> Just because it's parseable does not mean it's safe to use ...
>> allowing an end-user to provide a template without manual checking
>> sounds like a recipe for inviting exploits.
> There's nothing I can do about that.  If the user wants to write a
> template that exploits their own system, that's up to them.  I'm just
> trying to provide what checking I can at startup time.
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Re: Validate templates before use

Posted by Chad La Joie <la...@itumi.biz>.
On Mon, Feb 6, 2012 at 09:41, sebb <se...@gmail.com> wrote:
> Just because it's parseable does not mean it's safe to use ...
> allowing an end-user to provide a template without manual checking
> sounds like a recipe for inviting exploits.

There's nothing I can do about that.  If the user wants to write a
template that exploits their own system, that's up to them.  I'm just
trying to provide what checking I can at startup time.


-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org


Re: Validate templates before use

Posted by sebb <se...@gmail.com>.
On 6 February 2012 12:17, Chad La Joie <la...@itumi.biz> wrote:
> Is there a way to "validate" a template prior to using it?  I'd like
> to check that some user supplied templates are, at least, parsable
> during system startup.

Just because it's parseable does not mean it's safe to use ...
allowing an end-user to provide a template without manual checking
sounds like a recipe for inviting exploits.

But perhaps I'm missing something here, and you have some other way of
protecting against valid (but faulty or malicious) templates.

> Thanks.
>
> --
> Chad La Joie
> www.itumi.biz
> trusted identities, delivered
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
> For additional commands, e-mail: user-help@velocity.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org