I wouldn't think such pentest tools are a major concern, as I'd guess not
many users have to meet such requirements, and it would always be possible
to subclass the forms and set autocomplete=off where appropriate. Also the
referred mdn docs
Hello Alex!
Thanks for your work on this project, this is definitely something that I
believe would be useful in Django's core based on the number of times I
implemented a filtered queryset getter on Models.
I'm not totally sold on the API but having an analog of what ForeignObject
is to
Hi all,
I've run into many situations during my time using Django where I've wanted
to be able to express relations based on some other criteria than foreign
key equality. A few examples:
- descendants or children of a node in a tree structure
- saved search terms to search results
- a model
This type of enforced "complexity" does not increase security, and relevant
standards groups now recommend not trying to enforce these rules.
Quoting US NIST 800-63B, Appendix A:
> As noted above, composition rules are commonly used in an attempt to
increase the difficulty of guessing
Hi Everybody,
Django currently ships with the following password validators:
UserAttributeSimilarityValidator
MinimumLengthValidator
CommonPasswordValidator
NumericPasswordValidator
However, it is typical nowadays to require uppercase, lowercase, at least a
numeric character and a
Hi Dan.
Super!
On Tuesday, 28 August 2018 17:28:32 UTC+2, d...@thread.com wrote:
>
> I've run it on our codebase with ~1100 migrations and ~380 apps.
>
Yes! This is what I was looking for.
> There were no exceptions thrown - the script completed cleanly, although I
> haven't actually
Hi all,
Calendar Week 33 -- ending 19 August.
Triaged:
https://code.djangoproject.com/ticket/29672 -- Returns an empty model field
that is filled with a trigger in the database. (Invalid)
https://code.djangoproject.com/ticket/29656 -- Range Fields do not support
blank values via ModelForm
