Skip to content

TurboGears/tgext.utils

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

42 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

About tgext.utils

https://travis-ci.org/TurboGears/tgext.utils.png?branch=master https://coveralls.io/repos/TurboGears/tgext.utils/badge.png?branch=master

tgext.utils is a collection of utilities for the TurboGears2 web framework.

Installing

tgext.utils can be installed from pypi:

pip install tgext.utils

should just work for most of the users.

CSRF Protection

Note

Before CSRF protection, be sure to protect your app from XSS attacks

tgext.utils.csrf provides two decorators @csrf_token and @csrf_protect which generate a CSRF token for inclusion in a form and check that the token is valid.

You must apply @csrf_token decorator to the action that exposes the form, and put an <input type="hidden"> into the form with a request.csrf_token as the value and _csrf_token as name:

You must make sure sessions are enabled You also should register the CSRFConfigurationComponent in it's application configuration and configure at least csrf.secret in the blueprint/ini file (uuid4 is a good choice)

@csrf_token
@expose()
def form(self):
    return '''
    <form method="POST" action="/post_form">
        <input type="hidden" name="_csrf_token" value="%s">
        <input type="submit"/>
    </form>''' % request.csrf_token

The action that receives the form must have @csrf_protect decorator, no particular action or check is required on this action:

@csrf_protect
@expose()
def post_form(self, **kwargs):
    return 'OK!'

The generated cookie uses HMAC with sha384, sessionid and a timestamp, so each request gets a different token. A signed cookie is also used to follow the double submit guideline https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html#double-submit-cookie

Handling of the error is configurable through crsf.error_handler it should be a function that accepts a str that is the reason of the failure. by default it logs the warning and returns 403 to the user. A custom handler should either raise exceptions or raise tg.abort or tg.redirect.

Warning

This impacts user experience and usability. You may find the browser's back button "takes the user to expired forms" You may get additional expiration issues when the user uses multiple tabs of their browser

Warning

If you're stuck with TG<2.4 then upgrading this package (after 0.0.4) requires some (little) additional configuration work

Warning

To make the double submit cookie technique more effective, using HSTS is highly recommended

MetaTags

tgext.utils.meta.metatags provides a convenient way to generate common meta tags for a web page.

In lib/helpers.py add:

from tgext.utils.meta import metatags

Then in your pages:

${h.metatags(title="pagetitle", description="Page Description", image="http://url/myimage.png")}

Slug

tgext.utils.slug provides a way to generate slug for your page

to generate a slug use:

from tgext.utils.slug import slugify
myslug = slugify(model_id, string_to_be_inserted_in_the_url)

to get the id from a slug use:

from tgext.utils.slug import slug2entityid
slug2entityid(myslug)

Storage

tgext.utils.storage is a tool for storing files into /public dir in separated folders.

from tgext.utils.storage import store

filename = store(ufile)  # ufile is an instance of cgi.FieldStorage

file is stored inside /public/storage/${uuid1} folder thus also accessible using internal tg file serving.

Changelog

  • v0.0.5 CSRF module: improved csrf module, config as per tg 2.4+
  • v0.0.4 META module: xss prevention
  • v0.0.3 STORAGE module: implemented SLUG module: minor fix and documentation

About

Collection of utility methods for TurboGears2

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages