summaryrefslogtreecommitdiffstats
path: root/Modules/_hashopenssl.c
Commit message (Collapse)AuthorAgeFilesLines
* Untabify C files. Will watch buildbots.Antoine Pitrou2010-05-091-30/+30
|
* Do not compile stubs for the sha2 series hashes in the openssl hashlibGregory P. Smith2010-01-191-0/+12
| | | | | | | module when the openssl version is too old to support them. That leads both compiled code bloat and to unittests attempting to test implementations that don't exist for comparison purposes on such platforms.
* Issue #3745: Undo the requirement for new buffer API only objects to be passedGregory P. Smith2010-01-021-46/+23
| | | | | | to hashlib functions in python 2.x. The module now uses the 's*' for argument parsing which auto encodes unicode objects to the system default encoding for us.
* More yearly updates.Georg Brandl2010-01-011-1/+1
|
* cleanup applied patch to match style that is already in py3k branch.Gregory P. Smith2009-05-041-15/+8
|
* Issue #4751: For hashlib algorithms provided by OpenSSL, the PythonGregory P. Smith2009-05-041-49/+106
| | | | GIL is now released during computation on data lengths >= 2048 bytes.
* - Issue #3745: Fix hashlib to always reject unicode and non buffer-apiGregory P. Smith2009-02-131-38/+77
| | | | | | supporting objects as input no matter how it was compiled (built in implementations or external openssl library). (backported from a py3k branch)
* fix possible integer overflows in _hashopenssl #3886Benjamin Peterson2008-09-181-9/+42
|
* This reverts r63675 based on the discussion in this thread:Gregory P. Smith2008-06-091-6/+6
| | | | | | | http://mail.python.org/pipermail/python-dev/2008-June/079988.html Python 2.6 should stick with PyString_* in its codebase. The PyBytes_* names in the spirit of 3.0 are available via a #define only. See the email thread.
* Renamed PyString to PyBytesChristian Heimes2008-05-261-6/+6
|
* #1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and ↵Christian Heimes2007-12-191-1/+1
| | | | Py_REFCNT. Macros for b/w compatibility are available.
* email address updateGregory P. Smith2007-09-091-1/+1
|
* PEP 3123: Provide forward compatibility with Python 3.0, while keepingMartin v. Löwis2007-07-211-3/+2
| | | | | backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT.
* Make use of METH_O and METH_NOARGS where possible.Georg Brandl2006-05-291-15/+6
| | | | Use Py_UnpackTuple instead of PyArg_ParseTuple where possible.
* Properly fix Py_SAFE_DOWNCAST-triggerd bugs.Thomas Wouters2006-03-021-7/+10
|
* Py_SAFE_DOWNCAST isn't quite doing the right thing for going from Py_ssize_tThomas Wouters2006-03-021-7/+4
| | | | | | to an unsigned int (and back again) on 64-bit machines, even though the actual value of the Py_ssize_t variable is way below 31 bits. I suspect compiler-error.
* Make Py_ssize_t-clean.Thomas Wouters2006-03-011-8/+13
|
* Revert backwards-incompatible const changes.Martin v. Löwis2006-02-271-2/+2
|
* Fix icc warnings: HASH_OBJ_CONSTRUCTOR was not defined and using #if ↵Neal Norwitz2006-01-081-0/+4
| | | | HASH_OBJ_CONSTRUCTOR
* Fix icc warnings: extra semi-colon and signed vs unsignedNeal Norwitz2006-01-071-8/+8
|
* Add const to several API functions that take char *.Jeremy Hylton2005-12-101-2/+2
| | | | | | | | | | | | | | | | | | | In C++, it's an error to pass a string literal to a char* function without a const_cast(). Rather than require every C++ extension module to put a cast around string literals, fix the API to state the const-ness. I focused on parts of the API where people usually pass literals: PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type slots, etc. Predictably, there were a large set of functions that needed to be fixed as a result of these changes. The most pervasive change was to make the keyword args list passed to PyArg_ParseTupleAndKewords() to be a const char *kwlist[]. One cast was required as a result of the changes: A type object mallocs the memory for its tp_doc slot and later frees it. PyTypeObject says that tp_doc is const char *; but if the type was created by type_new(), we know it is safe to cast to char *.
* [ sf.net patch # 1121611 ]Gregory P. Smith2005-08-211-0/+487
A new hashlib module to replace the md5 and sha modules. It adds support for additional secure hashes such as SHA-256 and SHA-512. The hashlib module uses OpenSSL for fast platform optimized implementations of algorithms when available. The old md5 and sha modules still exist as wrappers around hashlib to preserve backwards compatibility.
generated by cgit v0.12 at 2025-03-10 09:44:20 (GMT)