GitLab

Why, oh why, am I making these mistakes? ;)
Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>

Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>

Braino. At least this would've just caused a slow memory leak. Nothing
to see here. Move along. ;)
Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>

We needs this sanity checking in multiple places, so create a new
function internal to libpushover: `pushover_message_priority_sane`.
Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>

Ensuring sane values for any user-defined input is always a good idea.
Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>

Introduce `pushover_free_ctx` and `pushover_free_message`.
Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>

To prevent UAF bugs, use double indirection to set the pointer to NULL
if the message was dynamically allocated.

In order to know whether to free the pushover_message_t object itself,
add a 64-bit wide flags member to the object.
Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>

Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>

Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>