40 lines
716 B
Raw Normal View History

2013-07-22 04:34:07 -04:00
/* See LICENSE file for copyright and license details. */
#include <stdint.h>
2013-07-22 04:34:07 -04:00
#include <stdio.h>
2013-07-22 04:34:07 -04:00
#include "crypt.h"
#include "sha512.h"
#include "util.h"
2013-07-22 04:34:07 -04:00
2014-11-17 08:38:52 -05:00
static struct sha512 s;
2013-07-22 04:34:07 -04:00
struct crypt_ops sha512_ops = {
static void
eprintf("usage: %s [-c] [file ...]\n", argv0);
2013-07-22 04:34:07 -04:00
main(int argc, char *argv[])
int (*cryptfunc)(int, char **, struct crypt_ops *, uint8_t *, size_t) = cryptmain;
2013-07-22 04:34:07 -04:00
uint8_t md[SHA512_DIGEST_LENGTH];
case 'c':
cryptfunc = cryptcheck;
2014-05-05 04:05:01 -04:00
2013-07-22 04:34:07 -04:00
Add *fshut() functions to properly flush file streams This has been a known issue for a long time. Example: printf "word" > /dev/full wouldn't report there's not enough space on the device. This is due to the fact that every libc has internal buffers for stdout which store fragments of written data until they reach a certain size or on some callback to flush them all at once to the kernel. You can force the libc to flush them with fflush(). In case flushing fails, you can check the return value of fflush() and report an error. However, previously, sbase didn't have such checks and without fflush(), the libc silently flushes the buffers on exit without checking the errors. No offense, but there's no way for the libc to report errors in the exit- condition. GNU coreutils solve this by having onexit-callbacks to handle the flushing and report issues, but they have obvious deficiencies. After long discussions on IRC, we came to the conclusion that checking the return value of every io-function would be a bit too much, and having a general-purpose fclose-wrapper would be the best way to go. It turned out that fclose() alone is not enough to detect errors. The right way to do it is to fflush() + check ferror on the fp and then to a fclose(). This is what fshut does and that's how it's done before each return. The return value is obviously affected, reporting an error in case a flush or close failed, but also when reading failed for some reason, the error- state is caught. the !!( ... + ...) construction is used to call all functions inside the brackets and not "terminating" on the first. We want errors to be reported, but there's no reason to stop flushing buffers when one other file buffer has issues. Obviously, functionales come before the flush and ret-logic comes after to prevent early exits as well without reporting warnings if there are any. One more advantage of fshut() is that it is even able to report errors on obscure NFS-setups which the other coreutils are unable to detect, because they only check the return-value of fflush() and fclose(), not ferror() as well.
2015-04-04 15:25:17 -04:00
return cryptfunc(argc, argv, &sha512_ops, md, sizeof(md)) ||
!!(fshut(stdin, "<stdin>") + fshut(stdout, "<stdout>"));
2013-07-22 04:34:07 -04:00