summaryrefslogtreecommitdiff
path: root/src/cryptography/hazmat/primitives/padding.py
Commit message (Collapse)AuthorAgeFilesLines
* Use from __future__ import annotations everywhere (#8643)Alex Gaynor2023-03-311-0/+1
|
* Remove explicit subclassing of object now that all classes are new-style (#6830)Alex Gaynor2022-01-301-2/+2
| | | As someone who first with Python in 2.4 or so, this habit is going to be hard to break.
* type pkcs7 padder/unpadder return type (#6718)Paul Kehrer2021-12-221-2/+2
|
* Convert unpadding code to Rust (#5668)Alex Gaynor2021-02-211-5/+8
|
* Added typing for a bunch of methods (#5737)Alex Gaynor2021-02-011-4/+4
|
* add typing to padding and constant time modules (#5714)Paul Kehrer2021-01-301-33/+50
|
* Complete removal of py2 (#5533)Alex Gaynor2020-12-091-7/+4
| | | | | * Drop Python 2 * Black everything
* Remove __future__ import from our code (#5610)Alex Gaynor2020-12-091-1/+0
|
* Remove Python2 from CI and code that branched on it (#5607)Alex Gaynor2020-12-081-8/+2
| | | | | | | | | | | | | * Remove Python2 from CI and code that branched on it * Update setup.py Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com> * remove * review feedback Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
* padding: Tip-toe around bytes subclasses. (#5548)Benjamin Peterson2020-11-041-2/+8
| | | | | This change allows future's newbytes class to be padded again. Fixes https://github.com/pyca/cryptography/issues/5547.
* allow bytes-like for padding (#5462)Paul Kehrer2020-09-131-4/+4
| | | | this doesn't improve efficiency in any way (copies galore!), but it does make it consistent between a cipher context and a padding context
* Paint it Black by the Rolling Stones (#5324)Alex Gaynor2020-07-201-14/+22
|
* centralize our bytes check (#4622)Paul Kehrer2018-12-021-4/+2
| | | this will make life a bit easier when we support bytearrays
* Raise padding block_size limit to what is allowed by the specs. (#3108)Terry Chia2016-11-151-2/+2
| | | | | | | | | | | | | | | | | | | | * Raize padding block_size limit to what is allowed by the specs. * Add tests for raising padding limits. * Amend C code for padding check to use uint16_t instead of uint8_t. * Fix test to work in Python 3. * Fix typo. * Fix another typo. * Fix return type of the padding checks. * Change hypothesis test on padding. * Update comment.
* Don't use subclassCédric Krier2016-03-141-88/+112
|
* Make _padding and _check_padding abstractmethodCédric Krier2016-02-271-2/+10
|
* Add padding check for ANSI X.923Cédric Krier2016-02-271-1/+3
| | | | All padding bytes must be 0.
* Factorize out common byte paddingCédric Krier2016-02-271-18/+33
|
* Added support for padding ANSI X.923Cédric Krier2016-02-271-4/+33
|
* convert to cffi 1.0 precompile systemPaul Kehrer2015-06-071-15/+2
|
* Move padding code into .c and .h files.Terry Chia2015-03-031-41/+7
|
* move paddingPaul Kehrer2015-02-131-3/+19
|
* Update the license header for every source file, as well as the documentation.Alex Gaynor2014-11-161-12/+3
| | | | Fixes #1209
* Move the cryptography package into a src/ subdirectoryDonald Stufft2014-11-131-0/+164
Due to differences in how py.test determines which module to ``import`` the test suite actually runs against the cryptography which is in the *current* directory instead of the cryptography which is installed. The problem essentially boils down to when there is a tests/__init__.py then py.test adds the current directory to the front of the sys.path, causing it to take precedence over the installed location. This means that running the tests relies on the implicit compile that CFFI does instead of testing against what people will actually be runnning, which is the module compiled by setup.py.