[PATCH] lib: Remove md5 and sha1 implementations.

2017-10-16 Thread Mark Wielaard
Only the testcase md5-sha1-test used them. So also remove that testcase. Signed-off-by: Mark Wielaard --- .gitignore| 1 - ChangeLog | 4 + lib/ChangeLog | 7 + lib/Makefile.am | 4 +- lib/md5.c | 438 -

Re: [PATCH] lib: sha1, md5, use memmove to move bytes inside buffer, not memcpy.

2017-10-16 Thread Mark Wielaard
On Mon, 2017-10-16 at 13:00 +0200, Mark Wielaard wrote: > At the end of {sha1,md5}_process_bytes we move the contents of > ctx->buffer up to the start of the buffer. Since this means the > source and destination overlap we should use memmove, not memcpy. I am retracting this patch since I noticed

[PATCH] libdwfl: When the kernel is found, but not the modules warn, don't fail.

2017-10-16 Thread Mark Wielaard
For -k the argp parser could fail to find the modules after the kernel itself was already found. Calling failure at this point closes the Dwfl, which isn't necessary. Just warn about the missing modules and continue with the kernel only Dwfl. Signed-off-by: Mark Wielaard --- libdwfl/ChangeLog |

[PATCH] lib: sha1, md5, use memmove to move bytes inside buffer, not memcpy.

2017-10-16 Thread Mark Wielaard
At the end of {sha1,md5}_process_bytes we move the contents of ctx->buffer up to the start of the buffer. Since this means the source and destination overlap we should use memmove, not memcpy. Signed-off-by: Mark Wielaard --- lib/ChangeLog | 6 ++ lib/md5.c | 2 +- lib/sha1.c| 2 +-