On 2009.05.07 at 09:26:34 +0400, Andrey Koltsov wrote:
> And one remark. This file "engines/ccgost/readme.gost" has an example
> configuration for GOST engine
>
>[gost_section]
>engine_id = gost
>dynamic_path = /usr/lib/ssl/engines/libgost.so
>default_algorithms = ALL
>crypt_
Thanks, static compilation works fine.
And one remark. This file "engines/ccgost/readme.gost" has an example
configuration for GOST engine
[gost_section]
engine_id = gost
dynamic_path = /usr/lib/ssl/engines/libgost.so
default_algorithms = ALL
crypt_params = id-Gost28147-89-Crypt
On 2009.05.05 at 13:47:50 +0200, Dr. Stephen Henson wrote:
>
> Yes it's just a case of hacking util/mkmf.pl and/or some Makefiles. If OpenSSL
> is compiled without shared library engines (enable-static-engine) in the
> command line you *do* get the GOST engine under VC++.
And I think that static
On Tue, May 05, 2009, Victor B. Wagner wrote:
> On 2009.05.05 at 09:27:30 +0400, Andrey Koltsov wrote:
>
> > As I understand, GOST engine works on Windows with mingw support only.
> > Is it planned to make it to compile with VC++ also?
> > If no, is it because technical problems or some legal iss
On 2009.05.05 at 09:27:30 +0400, Andrey Koltsov wrote:
> As I understand, GOST engine works on Windows with mingw support only.
> Is it planned to make it to compile with VC++ also?
> If no, is it because technical problems or some legal issues?
There should be no techincal problems. Code is port
As I understand, GOST engine works on Windows with mingw support only.
Is it planned to make it to compile with VC++ also?
If no, is it because technical problems or some legal issues?
Thanks,
Andy Koltsov
__
OpenSSL Project