From a5314a2ff4cb503ff41da13ffd0e907f49ee4009 Mon Sep 17 00:00:00 2001 From: Juuso Lapinlampi Date: Sat, 7 May 2016 14:40:25 +0000 Subject: Deprecate get_sha1() in Pomf 2.1.0 There are two issues with get_sha1(): - The function name doesn't follow the PSR-2 coding style guide for function naming, followed in Pomf since version 2.0.0. - SHA-1 is no longer considered resilient to collisions, versus SHA-256. In current plans, this feature is to be replaced with getHash() or similar function name in the next major version (Pomf 3.0.0). For consideration for future SHA-256 hashing implementation, the MySQL schema's hash value needs to be changed from char(40) to char(64) to accommodate the longer SHA-256 length of 64 bytes in hexadecimal string. --- CHANGELOG.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index 5b1594f..d4c935f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -22,6 +22,8 @@ This project adheres to [Semantic Versioning](http://semver.org/). - Swig banners. Use Swig templates or an alternative. (Juuso Lapinlampi) - Unused file expiration (`expire`). This feature may be removed in the next major version. (Juuso Lapinlampi) +- `get_sha1()` function. This API may be changed or removed in the next + major version, switching to SHA-256 hashes. (Juuso Lapinlampi) ## `2.0.2` - Unreleased -- cgit v1.2.3