Re: Securing GStringTemplateEngine…

["cristian.spiescu" <cr...@crispico.com>]

Hello jamie,

Did you find a solution for your issue? We are thinking of integrating a
templating mechanism powered by Groovy, and we are wondering about the
security implications.

Thank you!
Regards,
Cristian.





--
View this message in context: http://groovy.329449.n5.nabble.com/Securing-GStringTemplateEngine-tp5723378p5727506.html
Sent from the Groovy Users mailing list archive at Nabble.com.

Re: Securing GStringTemplateEngine…

[Keegan Witt <ke...@gmail.com>]

I missed this thread.  I see no reason not to make the change you
proposed.  I'll do some tests, if nothing breaks (and nobody comes up with
a reason not to), I'll commit this change.

-Keegan

On Fri, Sep 4, 2015 at 10:00 AM, JamieEchlin <ja...@gmail.com> wrote:

> Hi Cristian,
>
> I did it pretty much like I suggested, ie duplicating GStringTemplateEngine
> and adding a type for "out".
>
> cheers, jamie
>
>
>
> --
> View this message in context:
> http://groovy.329449.n5.nabble.com/Securing-GStringTemplateEngine-tp5723378p5727510.html
> Sent from the Groovy Users mailing list archive at Nabble.com.
>

Re: Securing GStringTemplateEngine…

[JamieEchlin <ja...@gmail.com>]

Hi Cristian,

I did it pretty much like I suggested, ie duplicating GStringTemplateEngine
and adding a type for "out".

cheers, jamie



--
View this message in context: http://groovy.329449.n5.nabble.com/Securing-GStringTemplateEngine-tp5723378p5727510.html
Sent from the Groovy Users mailing list archive at Nabble.com.