[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201206040828.15088.sftp.mtuci@gmail.com>
Date: Mon, 4 Jun 2012 08:28:14 +0400
From: "Sergey V." <sftp.mtuci@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: GOST symbol names (was: linux-x86-opencl build error)
On Monday 04 of June 2012 08:15:39 jfoug wrote:
>> 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.
I can prepare a patch with renames soon.
>>
>> 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.
As I know, openssl support only CryptoPro S-boxes.
> 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.
