| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
as a fallback for 'default_rounds', 'min_rounds', and 'max_rounds'.
this makes it easier to specify a django-style policy of "deprecate all hashes
which have a differing rounds value".
* removed special handling from 'rounds' from CryptContext parser
* tweaked affected CryptContext serialization tests
* added test for new behavior
|
| |
|
|
|
|
|
|
|
|
| |
only legitimate use was for 'vary_rounds' option, which is being phased out,
and other uses like 'min_rounds' were a security issue.
* fixed CryptContext() tests to stop uses "all" kwds
* issue dep warning if "all" scheme is used
* issue config warning if anything but "vary_rounds" is used,
since config needs to be changed (regardless of passlib version)
|
| |
|
|
|
|
|
| |
and not worth the amount of code it requires to support it.
* stripped out vary_rounds from all internal presets
* added deprecation warning if it's ever used
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
.encrypt()
----------
hash.encrypt() & context.encrypt() have been renamed to .hash().
this should take care of the long-standing issue 21 (the poor naming of .encrypt).
per docs, legacy aliases will remain in place until passlib 2.0.
.genhash() / .genconfig()
-------------------------
taking advantage of this reorganization to also deprecate .genconfig()
and .genhash() -- they're not really useful in a modern system,
nor as needed for historical support as initially thought:
.genconfig() will be retired completely in passlib 2.0;
.genhash() is rolled into the new .hash() method along with .encrypt().
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
the context,
and they will only be passed on for the hashes that support them (fixes issue 63).
|
| |/ |
|
| | |
|
| |
|
|
| |
comment 7) (transplant of r1f5b8860b743 from default branch)
|
| |
|
|
|
|
|
|
|
|
|
| |
* added some backwards-compat & error handling notes to CryptContext,
as suggested by Thomas Waldmann (https://code.google.com/p/passlib/issues/detail?id=27#c2)
* clarified alg descriptions and internal comments for lmhash, md5_crypt, cisco, et al
* deprecated_method() decorator now checks if ".. deprecated::" stanza already present in docstring
* hash_needs_update() won't be removed until release 2.0
|
| | |
|
| |
|
|
|
|
|
| |
against deprecated list (closes issue 39)
* also added some unittests to catch 3 cases covered in issue 39,
and some others as well.
|
| | |
|
| |
|
|
| |
reference
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
large amount of integration example code
|
| |
|
|
|
|
|
|
|
|
|
|
| |
=====================
* CryptContext docs finished
* README / LICENSE updated
* license text changed to correct BSD wording
* embarassingly, the history.rst is kinda off about release versions.
tried to make it give readers better outline.
* misc doc updates
* some handler names (eg: 'context', 'all') now forbidden by register_crypt_handler()
* bumped setup.cfg to b1
|
| | |
|
|
|
little to do with eachother
|
