| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `disable_shortcut` option served as a workaround in case
`__PCT_CTR_SHORTCUT__` leaked through a wrapper object, but I don't
think anyone actually used it, and it was a bad idea to expose it as
part of the public API.
Now that we do strong type checking inside block_template.c, there
shoujld be no need to ever use this option. It's now a no-op, retained
for backward compatibility only. It will be removed in some future
version of PyCrypto.
|
| |
|
|
|
|
|
| |
This should fix compilation on HP-UX 11.31. Thanks Adam Woodbeck for
reporting this.
|
| |
|
|
|
|
|
|
|
| |
We use <sys/inttypes.h> on Solaris platforms that don't have <stdint.h>.
This should fix https://bugs.launchpad.net/pycrypto/+bug/518871, reported by
Sebastian Kayser.
|
| |
|
|
|
|
|
|
|
| |
These are the easy ones. We don't release the GIL on cipher initialization,
hash initialization, or hash finalization, because those functions might make
Python API calls, and we would need to add a mechism for re-acquiring the GIL
in those cases.
|
|
|
|
|
| |
- Add check_wraparound_func pointer to PCT_CounterObject
- Call check_wraparound_func from block_template.c
|
|
|
|
|
| |
The old behaviour can be obtained by explicitly setting allow_wraparound=True
when invoking Counter.new
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In an attempt to simplify the copyright status of PyCrypto, I'm placing my
code into the public domain, and encouraging other contributors to do the
same.
I have used a public domain dedication that was recommended in a book on FOSS legal
issues[1], followed by the warranty disclaimer boilerplate from the MIT license.
[1] _Intellectual Property and Open Source: A Practical Guide to Protecting
Code_, a book written by Van Lindberg and published by O'Reilly Media.
(ISBN 978-0-596-51796-0)
|
| |
|
|
This change allows CTR-mode ciphers to bypass the Python function call
mechanism when using counter objects created using Crypto.Util.Counter.
|