openbsd/src/lib/libcrypto/modes/ccm128.c, branch OPENBSD_6_8_BASE A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE 2019-05-08T14:18:25+00:00 Make sure that the tag buffer size is equal to the tag size 2019-05-08T14:18:25+00:00 tb 2019-05-08T14:18:25+00:00 urn:sha1:a32a0f9c7ce589f17b76a740fcf6998b70bd28e6 in CRYPTO_ccm128_tag(). Otherwise the caller might end up using the part of the tag buffer that was left uninitialized. Issue found by Guido Vranken. ok inoguchi Remove assert() or OPENSSL_assert() of pointers being non-NULL. The policy 2015-02-10T09:46:30+00:00 miod 2015-02-10T09:46:30+00:00 urn:sha1:03858c0228d8ccda7d170fe43e0be79cd0dc6e5b for libraries in OpenBSD is to deliberately let NULL pointers cause a SIGSEGV. ok doug@ jsing@ tags as requested by miod and tedu 2014-06-12T15:49:31+00:00 deraadt 2014-06-12T15:49:31+00:00 urn:sha1:59f4f2c61d71e266d37dd2fc97615b3fd35b4721 Get __STRICT_ALIGNMENT from <machine/endian.h> and decide upon it, rather 2014-05-07T22:05:48+00:00 miod 2014-05-07T22:05:48+00:00 urn:sha1:93133951820983264b9940472403df1d23e0ccb3 than defining it for not (i386 and amd64 (and sometimes s390)) only. Compile-time tests remain compile-time tests, and runtime-test remain runtime-test instead of being converted to compile-time tests, per matthew@'s explicit demand (rationale: this makes sure the compiler checks your code even if you won't run it). No functional change except on s390 (which we don't run on) and vax (which we run on, but noone cares about) ok matthew@ Import OpenSSL 1.0.1g 2014-04-13T15:16:40+00:00 miod 2014-04-13T15:16:40+00:00 urn:sha1:52628ee3f51f011b463aaedb1a28aa0524b43cb3 import OpenSSL-1.0.1c 2012-10-13T21:23:50+00:00 djm 2012-10-13T21:23:50+00:00 urn:sha1:228cae30b117c2493f69ad3c195341cd6ec8d430