From ae7ec4c71de74fa52c5d89e32e28445c6602990d Mon Sep 17 00:00:00 2001 From: Geoff Thorpe Date: Wed, 22 Oct 2008 12:00:15 +0000 Subject: [PATCH] Apparently '__top' is also risky, obfuscate further. (All this to avoid inlines...) --- crypto/bn/bn.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/crypto/bn/bn.h b/crypto/bn/bn.h index eedde6a016..2333682a17 100644 --- a/crypto/bn/bn.h +++ b/crypto/bn/bn.h @@ -752,12 +752,12 @@ int RAND_pseudo_bytes(unsigned char *buf,int num); #define bn_correct_top(a) \ { \ BN_ULONG *ftl; \ - int __top = (a)->top; \ - if (__top > 0) \ + int _t371q = (a)->top; \ + if (_t371q > 0) \ { \ - for (ftl= &((a)->d[__top-1]); __top > 0; __top--) \ + for (ftl= &((a)->d[_t371q-1]); _t371q > 0; _t371q--) \ if (*(ftl--)) break; \ - (a)->top = __top; \ + (a)->top = _t371q; \ } \ bn_pollute(a); \ } -- 2.25.1