mirror of
https://github.com/qpdf/qpdf.git
synced 2024-06-21 03:12:20 +00:00
d71f05ca07
This makes all integer type conversions that have potential data loss explicit with calls that do range checks and raise an exception. After this commit, qpdf builds with no warnings when -Wsign-conversion -Wconversion is used with gcc or clang or when -W3 -Wd4800 is used with MSVC. This significantly reduces the likelihood of potential crashes from bogus integer values. There are some parts of the code that take int when they should take size_t or an offset. Such places would make qpdf not support files with more than 2^31 of something that usually wouldn't be so large. In the event that such a file shows up and is valid, at least qpdf would raise an error in the right spot so the issue could be legitimately addressed rather than failing in some weird way because of a silent overflow condition.
27 lines
778 B
C
27 lines
778 B
C
#ifndef RIJNDAEL_H
|
|
#define RIJNDAEL_H
|
|
|
|
#include <qpdf/qpdf-config.h>
|
|
#ifdef HAVE_INTTYPES_H
|
|
# include <inttypes.h>
|
|
#endif
|
|
#ifdef HAVE_STDINT_H
|
|
# include <stdint.h>
|
|
#endif
|
|
#include <stddef.h>
|
|
|
|
unsigned int rijndaelSetupEncrypt(uint32_t *rk, const unsigned char *key,
|
|
size_t keybits);
|
|
unsigned int rijndaelSetupDecrypt(uint32_t *rk, const unsigned char *key,
|
|
size_t keybits);
|
|
void rijndaelEncrypt(const uint32_t *rk, unsigned int nrounds,
|
|
const unsigned char plaintext[16], unsigned char ciphertext[16]);
|
|
void rijndaelDecrypt(const uint32_t *rk, unsigned int nrounds,
|
|
const unsigned char ciphertext[16], unsigned char plaintext[16]);
|
|
|
|
#define KEYLENGTH(keybits) ((keybits)/8)
|
|
#define RKLENGTH(keybits) ((keybits)/8+28)
|
|
#define NROUNDS(keybits) ((keybits)/32+6)
|
|
|
|
#endif
|