[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <007b01cd4208$b336d860$19a48920$@net>
Date: Sun, 3 Jun 2012 23:15:39 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: GOST symbol names (was: linux-x86-opencl build error)
>From: Solar Designer [mailto:solar@...nwall.com]
>> What version of OpenSSL is this? It looks like it has support for
>> GOST, so we clash with it. If so, we need to rename gost_init() and
>> perhaps a couple other functions.
>
>Can't we have these symbols local to just one source file and thus
>declared static? Then we don't need to rename them.
>
>Disclaimer: I haven't looked at the code.
There is a .c file that contains the crypt, and a .c file that is the
format. The gost_init is in the crypt file (gost_plug.c). the crypt is
written in the model of OpenSSL (ctx model). Likely it is the exact same
code in our gost_plug.c file as in the openssl.
We 'may' be able to simply use #defines within gost_plug.c and if we can
detect that gost is installed within the openssl (and compatible version),
then we simply use the OSSL, and the gost_plug.c becomes a module where all
code is commented out.
Just a thought (if there is 'something' we can detect at compile time).
Jim.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
