Make sure to use unsigned char for is*() functions
authorRichard Levitte <levitte@openssl.org>
Sun, 14 Feb 2016 12:02:15 +0000 (13:02 +0100)
committerRichard Levitte <levitte@openssl.org>
Sun, 14 Feb 2016 18:31:55 +0000 (19:31 +0100)
commit18295f0c2db084fe00d935d8506d6e964f652d21
tree81e661fc1e2052c698b5daee8aae711e574bc0e4
parentef8ca6bd544e4baea67f9a193ae896b8629944d0
Make sure to use unsigned char for is*() functions

On some platforms, the implementation is such that a signed char
triggers a warning when used with is*() functions.  On others, the
behavior is outright buggy when presented with a char that happens
to get promoted to a negative integer.

The safest thing is to cast the char that's used to an unsigned char.

Reviewed-by: Andy Polyakov <appro@openssl.org>
apps/apps.c
apps/apps.h
apps/ca.c
apps/ocsp.c
apps/s_client.c
apps/s_server.c
test/danetest.c