| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
permission (#170)
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
There seems to be one opening parenthesis too many here on both lines.
Discovered after running into the following errors while cross-compiling for PowerPC/Qoriq:
```
src/_csrc/sha2.c: In function 'SHA256Final':
src/_csrc/sha2.c:484: error: expected ')' before ';' token
src/_csrc/sha2.c:485: error: expected ')' before '}' token
src/_csrc/sha2.c:485: error: expected ';' before '}' token
```
|
| |
|
|
|
|
|
|
| |
* we need to define these if they don't exist on any platform
* clean up some warnings
* swap decls to __cplusplus defines
|
| |
|
|
|
|
|
|
| |
* add bcrypt pbkdf bindings
* fix some headers
* stdint is not a thing older VS has, but we shouldn't need it
|
|
|
* swap to using openbsd bcrypt
* we should probably call this 3.0
* update tests to handle slight change in behavior, test better
* strip out code we're not using
* define this for linux
* py3 fix
* add a changelog to the readme
* maybe work with windows
* portable endian header, replace swaps, other windows fixes
* handle older windows compilers properly, handle glibc < 2.9, retab
* remove a todo, that's definitely the limit
* make these definitions conditional since some BSDs may already have them
* add $2a$ tests from crypt_blowfish-1.3
* update readme to note supported prefixes
* almost pointless commit
* add support for $2y$
test vectors from openwall crypt-blowfish1.3
|