sbase/crypt.h

/* See LICENSE file for copyright and license details. */
struct crypt_ops {
	void (*init)(void *);
	void (*update)(void *, const void *, unsigned long);
	void (*sum)(void *, uint8_t *);
	void *s;
};

int cryptcheck(int, char **, struct crypt_ops *, uint8_t *, size_t);
int cryptmain(int, char **, struct crypt_ops *, uint8_t *, size_t);
int cryptsum(struct crypt_ops *, int, const char *, uint8_t *);
void mdprint(const uint8_t *, const char *, size_t);
Add license file details at top of files 2013-10-07 12:03:26 -04:00			`/* See LICENSE file for copyright and license details. */`
Add crypt.[ch] and update md5sum and sha1sum Factor out the code from md5sum and sha1sum into a util function. Use FILE * instead of a file descriptor. This will make it a bit easier/more consistent when we implement support for the -c option. 2013-07-07 10:29:45 -04:00			`struct crypt_ops {`
			`void (init)(void );`
			`void (update)(void , const void *, unsigned long);`
			`void (sum)(void , uint8_t *);`
			`void *s;`
			`};`

Refactor cryptcheck() to allow multiple list-files and stdin Previously, it was not possible to use sha1sum test.c \| sha1sum -c because the program would not differenciate between an empty argument and a non-specified argument. Moreover, why not allow this? sha1sum -c hashlist1 hashlist2 Digging deeper I found that using function pointers and a modification in the crypt-backend might simplify the program a lot by passing the argument-list to both cryptmain and cryptcheck. Allowing more than one list-file to be specified is also consistent with what the other implementations support, so we not only have simpler code, we also do not silently break if there's a script around passing multiple files to check. 2015-03-01 16:51:52 -05:00			`int cryptcheck(int, char *, struct crypt_ops , uint8_t *, size_t);`
Forgot to remove argc from function decl Thanks FRIGN for noticing this. 2013-11-30 16:11:19 -05:00			`int cryptmain(int, char *, struct crypt_ops , uint8_t *, size_t);`
Don't use buffered IO (fread) when not appropriate fread reads the entire requested size (BUFSIZ), which causes tools to block if only small amounts of data are available at a time. At best, this causes unnecessary copies and inefficiency, at worst, tools like tee and cat are almost unusable in some cases since they only display large chunks of data at a time. 2017-01-01 20:00:33 -05:00			`int cryptsum(struct crypt_ops , int, const char , uint8_t *);`
We do not name parameters in declarations 2013-11-22 08:40:08 -05:00			`void mdprint(const uint8_t , const char , size_t);`