summaryrefslogtreecommitdiffstats
path: root/test/afalgtest.c
diff options
context:
space:
mode:
authorMatt Caswell <matt@openssl.org>2016-06-01 23:15:12 +0100
committerMatt Caswell <matt@openssl.org>2016-06-13 17:28:40 +0100
commit25b9d11c002e5c71840c2a6733c5009d78f2c9db (patch)
tree58aa1f4eb04a77bdeb321d37b1a0bd5ae1067ee2 /test/afalgtest.c
parent74726750ef041ba5fdf0516cbd060a202f7092c1 (diff)
Handle inability to create AFALG socket
Some Linux platforms have a suitably recent kernel to support AFALG, but apparently you still can't actually create an afalg socket. This extends the afalg_chk_platform() function to additionally check whether we can create an AFALG socket. We also amend the afalgtest to not report a failure to load the engine as a test failure. A failure to load is almost certainly due to platform environmental issues, and not an OpenSSL problem. RT 4434 Reviewed-by: Andy Polyakov <appro@openssl.org>
Diffstat (limited to 'test/afalgtest.c')
-rw-r--r--test/afalgtest.c9
1 files changed, 7 insertions, 2 deletions
diff --git a/test/afalgtest.c b/test/afalgtest.c
index 3baced72ad..7fc03ba147 100644
--- a/test/afalgtest.c
+++ b/test/afalgtest.c
@@ -102,8 +102,13 @@ int main(int argc, char **argv)
e = ENGINE_by_id("afalg");
if (e == NULL) {
- fprintf(stderr, "AFALG Test: Failed to load AFALG Engine\n");
- return 1;
+ /*
+ * A failure to load is probably a platform environment problem so we
+ * don't treat this as an OpenSSL test failure, i.e. we return 0
+ */
+ fprintf(stderr,
+ "AFALG Test: Failed to load AFALG Engine - skipping test\n");
+ return 0;
}
if (test_afalg_aes_128_cbc(e) == 0) {