|
3bd9bb8d
|
2022-04-04T13:28:40
|
|
sha256: support dynamically loaded openssl
|
|
|
8bc998f4
|
2021-12-12T12:44:13
|
|
sha1: remove generic implementation
Remove the "generic" implementation; it should never be used; it only
existed for a no-dependencies configuration, and our bundled sha1dc
satisfies that requirement _and_ is correct.
|
|
|
6a7d5d23
|
2021-12-13T11:54:49
|
|
sha: support Win32 for SHA256
Adding SHA256 support prompted an overdue refactoring of some of the
unnecessary complexity around the CNG/CryptoAPI abstraction.
|
|
|
6b4a6faa
|
2021-12-12T15:41:47
|
|
sha: support OpenSSL for SHA256
|
|
|
b3e3fa10
|
2021-12-12T15:34:35
|
|
sha: support mbedTLS for SHA256
|
|
|
83c27786
|
2021-12-12T15:14:21
|
|
sha: support CommonCrypto for SHA256
|
|
|
b900981c
|
2021-12-12T14:25:25
|
|
sha: add sha256 algorithm
Add support for a SHA256 hash algorithm, and add the "builtin" SHA256
hash engine (from RFC 6234).
|
|
|
c7b189ba
|
2021-12-12T13:19:36
|
|
sha1: refactor folder structure
Eliminate the `sha1` folder, move it down into `hash` so that future
impelmentations can share common code.
|
|
|
5fcfada5
|
2021-11-15T07:45:16
|
|
cmake: document CMakeLists.txt hierarchy
|
|
|
c3b7ace9
|
2021-11-14T16:43:53
|
|
refactor: make util an object library
Instead of simply including the utility files directly, make them a
cmake object library for easy reusability between other projects within
libgit2.
Now the top-level `src` is responsible for platform selection, while the
next-level `libgit2` and `util` configurations are responsible for
identifying what objects they include.
|