No, you got that right, NULL being 'safe' to free varies with OS.
But - you aren't calling free() directly, THIS makes it safe. That's one of the
other benefits of having objects allocated and released by internal functions
rather than doing it directly.
void BN_MONT_CTX_free(BN_MONT_CTX *mont)
You can also add some more macros to the perlasm which already translates a
LOT of opcodes into something older assemblers won't choke on.
Pete
-"openssl-dev" wrote: -To:
robert.go...@igt.com
From: Jeremy Farrell via RT
Sent by: "openssl-dev"
Date: 02/13/2016 03:46AM
Cc: openssl-dev@ope
The problem with making those little "Oh we'll allow it for
interoperability' choices is that they may end up as security
vulnerabilities elsewhere. Particularly when there are multiple of them
made.
So - it is quite reasonable to reject a change like that because it's near
impossible to check al
bn/bn_prime.c
static int probable_prime(BIGNUM *rnd, int bits)
{
int i;
prime_t mods[NUMPRIMES]; <==
BN_ULONG delta, maxdelta;
This one is also excessive.
The problem is that even on OS's with dynamic thread stack if you do cause
a stack overrun, the entire process ge
(See attached file: ibmupdate1.tgz)
This is an update to the sources (only) for the CMAC, CCM and GCM code we
donated previously.
It rolls up various bug fixes for those who need them collected in one
place, but isn't a full patch to OpenSSL.
Current status.
GCM appears solid now with a 96 bit I
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
Potentially useful, but ...
A problem we frequently hit is multiple instances of libraries in a single
process - often due to applications dragging in shared library
dependencies they aren't explicitly aware of.
For that reason, this is only "mostly safe" if you can reference count
somehow, o
IBM is using OpenSSL as the base for providing a FIPS 140-2 certified
software crypto. solution for a number of it's products.
The project started some time ago and consists of OpenSSL "libcrypt" with
the changes below, and an IBM wrapper which provides the extra
functionality needed for FIPS
Yes, there's a larger patch with the rest of our changes, the OpenSSL mail
filters seem to have eaten it. I'm on leave at the moment, I'll forward
it again next week.
The larger patch is fairly ugly, I wouldn't expect it to be accepted
as-is, but it does have bits (like the config changes), wh
This code was developed by IBM staff and is donated to the OpenSSL project
under the terms of the OpenSSL license.
Attached. Assembler optimizations for PowerPC Linux, 32 and 64 bit.
(See attached file: linux_ppc32.s)(See attached file: linux_ppc64.s)
We have complied with IBM's legal requi
This code was developed by IBM staff and is donated to the OpenSSL project
under the terms of the OpenSSL license.
Attached. Assembler optimizations for AIX, 32 and 64 bit.
(See attached file: aix_ppc32.s)(See attached file: aix_ppc64.s)
We have complied with IBM's legal requirements and US
This code was developed by IBM staff and is donated to the OpenSSL project
under the terms of the OpenSSL license.
Attached. Assembler optimizations for zSeries Linux, 32 and 64 bit.
(See attached file: linux_zser32.s)(See attached file: linux_zser64.s)
We have complied with IBM's legal req
12 matches
Mail list logo
