Skip to content

Use jinja2 sandboxing by default #12733

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 1, 2023
Merged

Use jinja2 sandboxing by default #12733

merged 2 commits into from
Nov 1, 2023

Conversation

eyurtsev
Copy link
Collaborator

@eyurtsev eyurtsev commented Nov 1, 2023

  • This is an opt-in feature, so users should be aware of risks if using jinja2.
  • Regardless we'll add sandboxing by default to jinja2 templates -- this
    sandboxing is a best effort basis.
  • Best strategy is still to make sure that jinja2 templates are only loaded from trusted sources.

Copy link

vercel bot commented Nov 1, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
langchain ⬜️ Ignored (Inspect) Visit Preview Nov 1, 2023 7:55pm

@baskaryan baskaryan merged commit 0e1aedb into master Nov 1, 2023
@baskaryan baskaryan deleted the eugene/jinja_sandbox branch November 1, 2023 21:54
xieqihui pushed a commit to xieqihui/langchain that referenced this pull request Nov 21, 2023
* This is an opt-in feature, so users should be aware of risks if using
jinja2.
* Regardless we'll add sandboxing by default to jinja2 templates -- this
  sandboxing is a best effort basis.
* Best strategy is still to make sure that jinja2 templates are only
loaded from trusted sources.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants