195eaac041
https://www.djangoproject.com/weblog/2013/feb/19/security/ - Host header poisoning: an attacker could cause Django to generate and display URLs that link to arbitrary domains. - Formset denial-of-service: an attacker can abuse Django's tracking of the number of forms in a formset to cause a denial-of-service attack. - XML attacks: Django's serialization framework was vulnerable to attacks via XML entity expansion and external references. - Data leakage via admin history log: Django's admin interface could expose supposedly-hidden information via its history log. |
||
---|---|---|
.. | ||
DESCR | ||
PLIST | ||
README |
$OpenBSD: README,v 1.2 2011/06/02 13:41:41 ajacoutot Exp $ +----------------------------------------------------------------------- | Running ${FULLPKGNAME} on OpenBSD +----------------------------------------------------------------------- Documentation ============= Complete project documentation may be found in: ${PREFIX}/share/doc/${LNAME}/ or online: http://docs.djangoproject.com/en/${MODPY_EGG_VERSION}/ Release notes about the changes that occurred in this release may be found online at: http://docs.djangoproject.com/en/dev/releases/${MODPY_EGG_VERSION}/ Databases ========= Django supports number of different databases, but you need to install Python database adapter(s) to use them: * py-mysql - for MySQL database, * py-psycopg2 - for PostgreSQL database. SQLite works out-of-the-box. UTF-8 ===== Django assumes that you're running UTF-8 capable system, but it doesn't enforce any locales, which results in regressions when running in an environment without enabled UTF-8 locale. This means that, unless you've got UTF-8 locale enabled for your profile, you need to enable UTF-8 while starting Django process: $ env LC_CTYPE=en_US.UTF-8 ./manage.py runserver or configure your application server to pass this setting.