beldmit> Cheers,
> beldmit> Richard
> beldmit>
> beldmit> In message
> beldmit> gmail.com> on Fri, 17
> beldmit> Nov 2017 11:08:34 +0300, Dmitry Belyavsky
> said:
> beldmit>
> beldmit> beldmit> Hello,
> beldmit> beldmit>
>
at should at least take away gcc's complaint
about '-pthread'... I cannot say if that'll fix the rest, I don't
know Solaris enough.
Cheers,
Richard
In message
mailto:cadqlbzkeqxgafwggaz5gyrqp9xgewjfj2fvtkln9srnrej%2b...@mail.gmail.com>>
on Fri, 17 Nov
know Solaris enough.
beldmit>
beldmit> Cheers,
beldmit> Richard
beldmit>
beldmit> In message
beldmit>
on Fri, 17
beldmit> Nov 2017 11:08:34 +0300, Dmitry Belyavsky said:
beldmit>
beldmit> beldmit> Hello,
beldmit> beldmit>
beldmit> beldmit> We e
7;s complaint
> about '-pthread'... I cannot say if that'll fix the rest, I don't
> know Solaris enough.
>
> Cheers,
> Richard
>
> In message gmail.com> on Fri, 17 Nov 2017 11:08:34 +0300, Dmitry Belyavsky <
> beld...@gmail.com> said:
>
> beldmit&
on Fri, 17 Nov 2017 11:08:34 +0300, Dmitry Belyavsky said:
beldmit> Hello,
beldmit>
beldmit> We experience problems building OpenSSL on Solaris.
beldmit>
beldmit> /usr/local/src/openssl-1.1.0g>uname -a
beldmit>
beldmit> SunOS pooh.tcinet.ru 5.10 Generic_147147-26 sun4u spa
Hello,
We experience problems building OpenSSL on Solaris.
/usr/local/src/openssl-1.1.0g>uname -a
SunOS pooh.tcinet.ru 5.10 Generic_147147-26 sun4u sparc
SUNW,SPARC-Enterprise
/usr/local/src/openssl-1.1.0g>gcc -v
Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6
1.0.1 is old, and not really supported, except some security fixes.
1.0.x does not provide the ability to compile out TLSv1.0 from 1.1 from 1.2.
The upcoming 1.1.x does.
If you disable tls1, then you’ve also disabled all later versions, so enable
tlsv1 at config time and use the SSL options to en
Hi,
I'm trying to build Openssl as a static library and use it in my projects.
Have you guys put any thought to port the Openssl library to UWP(Universal
Windows 10 Platform)?
Can you provide me any guidelines or useful information that i can use to
port the libraries unless ported already?
Any
>>> /bin/as: Execution
>>> of /bin/compat-as/as failed with error code 0
>
> You're trying to cross compile? What is th target?
>
> How did you call Configure?
On related note, similar problem was reported earlier, see for example
https://mta.openssl.org/pipermail/openssl-dev/2015-June/001768.h
On Wed, Feb 24, 2016 at 09:09:49AM -0800, Datta Prabhu Maddikunta wrote:
> > /bin/as: Execution
> > of /bin/compat-as/as failed with error code 0
You're trying to cross compile? What is th target?
How did you call Configure?
Kurt
--
openssl-dev mailing list
To unsubscribe: https://mta.openss
Reposting on openssl-dev for some solution.
-- Forwarded message --
From: Datta Prabhu Maddikunta
Date: Tue, Feb 23, 2016 at 5:06 PM
Subject: Re: Assembly code errors while building openssl-1.0.2f on Ubuntu
14.04
To: openssl-us...@openssl.org
Hi Team,
>
> I am trying to
fixed in master at commit f3f1cf8444f439c0be9de04bf3821a20d00fd956 thanks!
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4181
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https
all fixed in master with the perl-based test framework.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
If you sneeze on the FIPS code, you need a new CMVP change letter.
Setting realistic expectations, there are no plans at this time for any FIPS
work.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://m
Sorry we didn't get to this sooner. We're only taking security fixes for 1.0.1
now.
Please open a new ticket if this is still an issue with current releases.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: h
Sorry we didn't get to this sooner. We're only taking security fixes for 1.0.1
now.
Please open a new ticket if this is still an issue with current releases.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: h
Hello OpenSSL team,
I get errors when I build openssl 1.0.2e with -DREF_PRINT -DREF_CHECK
./config -ggdb -DREF_PRINT -DREF_CHECK
make
ec_key.c: In function 'EC_KEY_free':
ec_key.c:115:14: error: called object is not a function or function pointer
REF_PRINT("EC_KEY", r);
^
ec_ke
Tom Kacvinsky in gmane.comp.encryption.openssl.devel (Tue, 27 Oct 2015
13:15:45 -0400):
>I've seen several messages float by about building OpenSSL on Windows. My
>understanding is that I'll need a Perl distribution, in addition to a
>specific assembler (MS's Macro Assemb
Take a look at the INSTALL.W32 file in the tarball. This details all
the requirements and steps to compile the code.
On 10/27/2015 01:15 PM, Tom Kacvinsky wrote:
> Hi,
>
> I've seen several messages float by about building OpenSSL on
> Windows. My understanding is that
Hi,
I've seen several messages float by about building OpenSSL on Windows. My
understanding is that I'll need a Perl distribution, in addition to a
specific assembler (MS's Macro Assemble is not up to the task is what I
gather). Anything else I need to be aware of? I will be bu
In message on Mon,
6 Jul 2015 18:25:12 +, Lianghui Chen said:
liachen> Hi
liachen>
liachen> It is from https://github.com/openssl/openssl.git, branch master and
commit f66aad6.
Commit f66aad6 is this:
commit f66aad60f249e90d16d585859b4dd62368ed7ccd
Author: Ben Laurie
Date:
y 06, 2015 3:07 PM
To: openssl-dev@openssl.org
Subject: Re: [openssl-dev] System openssl headerfiles are used
when building openssl itself
> No, it doesn't. And it should not, right? As there is no folder openssl which
> has files like ssl.h.
In master, th
> No, it doesn't. And it should not, right? As there is no folder openssl which
> has files like ssl.h.
In master, there should be include/openssl/ssl.h
> But I did notice some files, like ssl_locl.h, are included in C files using
> "ssl_locl.h", instead of , already.
The file ssl_locl.h is loc
BR - Lianghui
From: openssl-dev [openssl-dev-boun...@openssl.org] on behalf of Salz, Rich
[rs...@akamai.com]
Sent: Monday, July 06, 2015 2:41 PM
To: openssl-dev@openssl.org
Subject: Re: [openssl-dev] System openssl header files are usedwh
> It is from https://github.com/openssl/openssl.git, branch master and commit
> f66aad6.
Suppose you edit ssl_err, ssl_err2, ssl_lib, and ssl_locl to replace the
brackets <> with quotes. Does that fix the problem?
___
openssl-dev mailing list
To unsub
@openssl.org
Subject: Re: [openssl-dev] System openssl header files are used when
buildingopenssl itself
> I think it is wrong to use a system version of ssl.h when building my own
That sounds like a bug. What version are you using?
___
open
> I think it is wrong to use a system version of ssl.h when building my own
That sounds like a bug. What version are you using?
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hi, all
I am building openssl (master/f66aad6) within my own project in Mac OS X
Yosemite, and it get compile error about undefined TLS_SIGALGS, which is
defined in ssl/ssl.h, but not in OS version of ssl.h
(/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
Dear Andy,
On Mon, May 25, 2015 at 5:26 PM, Andy Polyakov via RT
wrote:
> >>> ghash-x86_64.s:1383: Error: no such instruction: `vpclmulqdq
> >>> $0,%xmm6,%xmm14,%xmm0'
> >>
> >> What does 'gcc -Wa,-v -c -o /dev/null -x assembler /dev/null' print on
> >> your system?
> >>
> >>
> >> $ gcc -Wa,-v -
Dear Andy,
On Mon, May 25, 2015 at 5:26 PM, Andy Polyakov via RT
wrote:
> >>> ghash-x86_64.s:1383: Error: no such instruction: `vpclmulqdq
> >>> $0,%xmm6,%xmm14,%xmm0'
> >>
> >> What does 'gcc -Wa,-v -c -o /dev/null -x assembler /dev/null' print on
> >> your system?
> >>
> >>
> >> $ gcc -Wa,-v -
>>> ghash-x86_64.s:1383: Error: no such instruction: `vpclmulqdq
>>> $0,%xmm6,%xmm14,%xmm0'
>>
>> What does 'gcc -Wa,-v -c -o /dev/null -x assembler /dev/null' print on
>> your system?
>>
>>
>> $ gcc -Wa,-v -c -o /dev/null -x assembler /dev/null
> GNU assembler version 2.17.50.0.6-14.el5 (x86_64-re
Dear Andy,
On Mon, May 25, 2015 at 2:23 PM, Andy Polyakov via RT
wrote:
> Hi,
>
> > I got a problem building openssl 1.0.2a on SUSE.
> >
> > Platform:
> >> uname -a
> >
> > Linux b-sles11-64 2.6.27.19-5-default #1 SMP 2009-02-28 04:4
Dear Andy,
On Mon, May 25, 2015 at 2:23 PM, Andy Polyakov via RT
wrote:
> Hi,
>
> > I got a problem building openssl 1.0.2a on SUSE.
> >
> > Platform:
> >> uname -a
> >
> > Linux b-sles11-64 2.6.27.19-5-default #1 SMP 2009-02-28 04:4
Hi,
> I got a problem building openssl 1.0.2a on SUSE.
>
> Platform:
>> uname -a
>
> Linux b-sles11-64 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100
> x86_64 x86_64 x86_64 GNU/Linux
>
>
> Compiler:
>
>> gcc -v
> Using built-in specs.
Hello openssl-dev,
I got a problem building openssl 1.0.2a on SUSE.
Platform:
>uname -a
Linux b-sles11-64 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100
x86_64 x86_64 x86_64 GNU/Linux
Compiler:
> gcc -v
Using built-in specs.
Target: x86_64-suse-linux
Configured with: ../con
Hello openssl-dev,
I got a problem building openssl 1.0.2a on SUSE.
Platform:
>uname -a
Linux b-sles11-64 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100
x86_64 x86_64 x86_64 GNU/Linux
Compiler:
> gcc -v
Using built-in specs.
Target: x86_64-suse-linux
Configured with: ../con
On 13/03/2015 22:10, Joey Yandle wrote:
...
On side note
the error is indication that your nasm is out-of-date and you are
missing out some optimizations.
I'm using the nasm-2.07 windows installer from sourceforge:
http://sourceforge.net/projects/nasm/
Is there something more recent?
The
tmp32\aesni-sha256-x86_64.asm:113: error: symbol
`__imp_RtlVirtualUnwind' undefined
Can you confirm that attached patch addresses the problem?
Yes, that fixes it. However, the build then fails during linking:
lib /nologo /out:out32\libeay32.lib @C:\Users\dragon\AppData\Local\Temp\
nm60AD.tmp
Hi,
> nasm -f win64 -DNEAR -Ox -g -o tmp32\aesni-sha256-x86_64.obj
> tmp32\aesni-sha256-x86_64.asm
> tmp32\aesni-sha256-x86_64.asm:113: error: symbol
> `__imp_RtlVirtualUnwind' undefined
> NMAKE : fatal error U1077: '"C:\Program Files (x86)\NASM\nasm.EXE"' :
> return code '0x1'
>
> Any id
I'm trying to build openssl-1.0.2 for windows. I successfully built
win32 binaries, but I can't seem to build win64a. I get reasonably far
into the build, but then it fails doing AES nasm calls. Previous nasm
calls succeed.
FWIW, I was able to work around this by disabling asm entirely:
per
Hello,
I'm trying to build openssl-1.0.2 for windows. I successfully built
win32 binaries, but I can't seem to build win64a. I get reasonably far
into the build, but then it fails doing AES nasm calls. Previous nasm
calls succeed.
perl Configure VC-WIN64A --prefix=Output\Win64\Release
ms
Info:
Windows 8.1 64-bit
Visual Studio Premium 2012
Zlib 1.2.8
OpenSSL fips object module 2.0.8
OpenSSL 1.0.1j
Note: zlib and fips object module build fine (FYI: zlib dll built from zlib
distro directory contrib\vstudio\vc11 that makes zlibwapi.dll instead of making
ZLIB1.DLL).
The following bu
Closing this ticket as Andy has provided an answer.
Matt
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
>> When I built OpenSSL 1.0.1j for Win64 I had several hundred loss of data
>> warnings, most like this:
>>
>> warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of
>> data
>>
>> Loss of data warnings can be serious or benign as you know. Is there a
>> list of known warnings that
> When I built OpenSSL 1.0.1j for Win64 I had several hundred loss of data
> warnings, most like this:
>
> warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of
> data
>
> Loss of data warnings can be serious or benign as you know. Is there a
> list of known warnings that are e
Hi,
> Hello, I built OpenSSL 1.0.1j this way, which in the case of x86 I have
> done with some previous versions as well:
>
> x86:
> perl Configure debug-VC-WIN32 enable-static-engine
> ms\do_ms
> nmake -f ms\ntdll.mak
>
> x64:
> perl Configure debug-VC-WIN64A enable-static-engine
> ms\do_win64a
Hello, I built OpenSSL 1.0.1j this way, which in the case of x86 I have
done with some previous versions as well:
x86:
perl Configure debug-VC-WIN32 enable-static-engine
ms\do_ms
nmake -f ms\ntdll.mak
x64:
perl Configure debug-VC-WIN64A enable-static-engine
ms\do_win64a
nmake -f ms\ntdll.mak
I
When I built OpenSSL 1.0.1j for Win64 I had several hundred loss of data
warnings, most like this:
warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of
data
Loss of data warnings can be serious or benign as you know. Is there a
list of known warnings that are expected and
Hello Andy,
On Thu, Oct 23, 2014 at 5:34 PM, Andy Polyakov via RT
wrote:
> > I used the commands
> >
> > ./Configure shared debug
> I don't think this would be working build on
> a 64-bit platform such as one in question. Or rather even if it does
> work (make test pas
Hello Andy,
On Thu, Oct 23, 2014 at 5:34 PM, Andy Polyakov via RT
wrote:
> > I used the commands
> >
> > ./Configure shared debug
> I don't think this would be working build on
> a 64-bit platform such as one in question. Or rather even if it does
> work (make test pas
> I used the commands
>
> ./Configure shared debug
I don't think this would be working build on
a 64-bit platform such as one in question. Or rather even if it does
work (make test passes, etc.) it wouldn't be supported and questions
should be dismissed. "Official" way t
Hello Rich,
Yes, removing the cast solves the problem.
beldmit@manul$ sed -n -e 160,162p crypto/bn/bn_ctx.c
BN_STACK *stack = &ctx->stack;
fprintf(stderr,"(%p): ", ctx);
while(bnidx < ctx->used)
Thank you!
On Sun, Oct 5, 2014 at 4:08 PM, Salz, Rich wrote:
> Did you ta
Did you take the (unsigned int) cast off?
Do sed –n –e 160,162p bn_ctx.
:��I"Ϯ��r�m
(Z+�7�zZ)���1���x ��hW^��^��%�� ��&jם.+-1�ځ��j:+v���h�
Hello Rich,
Unfortunately no :-(
The error became
bn_ctx.c: In function ‘ctxdbg’:
bn_ctx.c:161:27: error: cast from pointer to integer of different size
[-Werror=pointer-to-int-cast]
bn_ctx.c:161:2: error: format ‘%p’ expects argument of type ‘void *’, but
argument 3 has type ‘unsigned int’ [-Wer
In crypto/bn/bn_ctx.c, line 161:
fprintf(stderr,"(%08x): ", (unsigned int)ctx);
change it to this
fprintf(stderr,"(%p): ", ctx);
and see if that fixes it.
--
Principal Security Engineer, Akamai Technologies
IM: rs...@jabber.me Twitter: RichSalz
Hello openssl team,
I've got a problem building openssl
I used the commands
./Configure shared debug
make
and get an error
gcc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include -DBN_DEBUG
-DREF_CHECK -DCONF_DEBUG -DBN_CTX_DEBUG -DCRYPTO_MDEBUG -DOPENSSL_NO_ASM
-ggdb -g2 -Wf
On Wed Jul 10 21:46:50 2013, graeme.per...@gmail.com wrote:
> I am trying to build the FIPS Object Module for Windows on an AMD64
> machine. I started with the instructions in section 4.3 of the User Guide
> 2.0, and was able to build the FIPS module itself, but the instructions for
> building a FI
Fixed.
http://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=955376fde3c60999b27deeebb41d82ad17dca3da
Thanks for the report.
Matt
__
OpenSSL Project http://www.openssl.org
Development Mailing Li
Hello,
when we try to build openssl when TLS_DEBUG is on, we get an error:
t1_enc.c: In function ‘tls1_mac’:
t1_enc.c:1045: error: ‘mac_sec’ undeclared (first use in this function)
t1_enc.c:1045: error: (Each undeclared identifier is reported only once
t1_enc.c:1045: error: for each function it a
On 09/18/2013 09:07 AM, Perrow, Graeme wrote:
> I am trying to build the FIPS module on a 64-bit AIX machine (running
> AIX 5.3). When I run ./config (or ./config no-asm) in the
> openssl-fips-2.0.5 directory, I get this:
>
> Operating system: 0003D0AAD300-ibm-aix
>
> WARNING! If you wish to buil
I am trying to build the FIPS module on a 64-bit AIX machine (running AIX 5.3).
When I run ./config (or ./config no-asm) in the openssl-fips-2.0.5 directory, I
get this:
Operating system: 0003D0AAD300-ibm-aix
WARNING! If you wish to build 64-bit kit, then you have to
invoke './Configure
On 07/10/2013 03:46 PM, Graeme Perrow via RT wrote:
> I am trying to build the FIPS Object Module for Windows on an AMD64
> machine. I started with the instructions in section 4.3 of the User Guide
> 2.0, and was able to build the FIPS module itself, but the instructions for
> building a FIPS-capab
On 07/10/2013 03:46 PM, Graeme Perrow via RT wrote:
> I am trying to build the FIPS Object Module for Windows on an AMD64
> machine. I started with the instructions in section 4.3 of the User Guide
> 2.0, and was able to build the FIPS module itself, but the instructions for
> building a FIPS-capab
I am trying to build the FIPS Object Module for Windows on an AMD64
machine. I started with the instructions in section 4.3 of the User Guide
2.0, and was able to build the FIPS module itself, but the instructions for
building a FIPS-capable OpenSSL are specific to 32-bit Windows. I adjusted
the bu
On 16 January 2013 13:55, Bruce Cran wrote:
> We've been having regular build problems on Windows: sometimes nasm claims
> there are unresolved symbols. For example:
>
> set ASM=nasm -f win64 -DNEAR -Ox -g
> perl crypto\x86_64cpuid.pl tmp32dll.dbg\x86_64cpuid.asm
>
> nasm -f win64 -DNEAR -Ox
We've been having regular build problems on Windows: sometimes nasm
claims there are unresolved symbols. For example:
set ASM=nasm -f win64 -DNEAR -Ox -g
perl crypto\x86_64cpuid.pl tmp32dll.dbg\x86_64cpuid.asm
nasm -f win64 -DNEAR -Ox -g -o tmp32dll.dbg\x86_64cpuid.obj
I'm currently trying to build openssl-1.0.1c on 64bit PA-RISC HPUX but
am getting compile errors. I have successfully built a 32bit version
which compiles and passes make test, but unfortunately need to be able
to link the libraries with a 64bit application. I attach the output from
"make repo
On 10/24/2012 11:03 PM, Munagala Ramanath wrote:
Just downloaded built openssl 1.0.1c on Ubuntu 10.04 x86_64 with the
standard commands:
./config
make
make test
All is well but I noticed that these files from 'engines' are compiled
but the resulting objects are
not put into any library:
e_4
> We are going off topic on my question. Which is just, is android openssl
> builds going to continue to have versions?
First of all it's hardly appropriate to build it as lib[crypto|ssl].so.
So essentially it's .so.1.0.0.so vs. say .1.0.0.so. Complain appears to
be that .so.1.0.0 doesn't play we
: openssl-dev@openssl.org
Subject: Re: Building openssl fips 2.0 shared without version for Android
> I have a common c library on top of openssl to abstract it from our
> applications we use for devices and servers. We can easily plug in
> any version of openssl going forward. On Android
I have a common c library on top of openssl to abstract it from our
applications we use for devices and servers. We can easily plug in any
version of openssl going forward. On Android we had an existing jni wrapper
for our common library that I compile with android ndk.
Wouldn't it be most appr
Sent: Friday, November 09, 2012 12:04 PM
To: openssl-dev@openssl.org
Subject: Re: Building openssl fips 2.0 shared without version for Android
> Very good point, I agree. The advantage of the shared object is I
> don't need to sign the entire application again (fipsld).
My understandin
Very good point, I agree. The advantage of the shared object is I don't
need to sign the entire application again (fipsld).
My understanding is that native methods are always collected in shared
library. Shared library containing FIPS module is the only one that
needs to be fingerprinted. So
why the versioning is only done in the Linux
build.
Thanks for the response
Ken
-Original Message-
From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org]
On Behalf Of Andy Polyakov
Sent: Friday, November 09, 2012 7:06 AM
To: openssl-dev@openssl.org
Subject: Re: Buildin
Ken Montagna wrote:
> I have built android on windows, iOS, and android successfully, but with
> android I had to do a workaround for the versioning using this link:
>
> http://stackoverflow.com/questions/12269563/using-openssl-fips-2-0-shared-libraries-in-android
>
>
>
> Is there an environme
I have built android on windows, iOS, and android successfully, but with
android I had to do a workaround for the versioning using this link:
http://stackoverflow.com/questions/12269563/using-openssl-fips-2-0-shared-li
braries-in-android
Is there an environment variable or switch I can pass to
Just downloaded built openssl 1.0.1c on Ubuntu 10.04 x86_64 with the standard
commands:
./config
make
make test
All is well but I noticed that these files from 'engines' are compiled but the
resulting objects are
not put into any library:
e_4758cca, e_aep, e_atalla, e_cswift, e_gmp, e_chil,
e_
> openssl 1.0.1 and win32: assembler error: x86cpuid.asm
>
> Building OpenSSL
> perl util/copy.pl ".\crypto\buildinf.h" "tmp32dll\buildinf.h"
> Copying: ./crypto/buildinf.h to tmp32dll/buildinf.h
> ml /nologo /Cp /coff /c /Cx /Zi /Fotmp32dll\
openssl 1.0.1 and win32: assembler error: x86cpuid.asm
Building OpenSSL
perl util/copy.pl ".\crypto\buildinf.h" "tmp32dll\buildinf.h"
Copying: ./crypto/buildinf.h to tmp32dll/buildinf.h
ml /nologo /Cp /coff /c /Cx /Zi /Fotmp32dll\x86cpuid.obj
tmp32dll\x86c
On 2012-02-10 23:15, Philip Prindeville wrote:
> I'm not a Windows person so bear with me: I'm trying to ensure that some
> multi-platform code continues to build and run on Windows, so I'm having to
> set up a build environment there too.
If you install Visual Studio 2010, it should by default
On Fri, Feb 10, 2012, Philip Prindeville wrote:
> Hi.
>
> I'm not a Windows person so bear with me: I'm trying to ensure that some
> multi-platform code continues to build and run on Windows, so I'm having to
> set up a build environment there too.
>
> I went looking for MASM and found it on M
Hi.
I'm not a Windows person so bear with me: I'm trying to ensure that some
multi-platform code continues to build and run on Windows, so I'm having to set
up a build environment there too.
I went looking for MASM and found it on MSDN, but when I try to run it, it
complains about the architec
> 3.) nmake -f ms\ntdll.mak
>
> C:\Daten\openssl\openssl-1.0.0e>nmake -f ms\ntdll.mak
>
> Microsoft (R) Program Maintenance Utility Version 9.00.30729.01
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> Building OpenSSL
> perl util/copy.pl &
or VC-WIN64A
2.) ms\do_win64a
seems to work
...
3.) nmake -f ms\ntdll.mak
C:\Daten\openssl\openssl-1.0.0e>nmake -f ms\ntdll.mak
Microsoft (R) Program Maintenance Utility Version 9.00.30729.01
Copyright (C) Microsoft Corporation. All rights reserved.
Building OpenSSL
perl
Hi
I already mentioned this in the opensssl-users maling list. Is it possible to
build openssl without RSA,DA and DH support? Doing so i got erros like
./config --prefix=/home_vie/mhofer/tmp_opensslscratch
--openssldir=/home_vie/mhofer/tmp_opensslscratch/openssl no-threads no-zlib
no-shared
From: "Dr. Stephen Henson"
> [...]
> >What is the justification for having mixed-/upper-case options/values
> > like, say:
> >
> > -CAfile
> > -CApath
> > -EncryptedData_encrypt
> > SMIME|PEM|DER
> > ???
>
> It has never been mentioned as being a problem before. [...
From: "Dr. Stephen Henson"
> > > http://antinode.info/ftp/openssl/1_0_0/test/
> >
> >Now contains some new and updated files to add a helper program for
> > the perl system() function on VMS systems.
>
> Is there any way to redirect standard output and error to different files
> under
On Mon, May 03, 2010, Steven M. Schweda wrote:
> > http://antinode.info/ftp/openssl/1_0_0/test/
>
>Now contains some new and updated files to add a helper program for
> the perl system() function on VMS systems.
>
Is there any way to redirect standard output and error to different fil
On Mon, May 03, 2010, Steven M. Schweda wrote:
> > [...] (One might question the cleverness of that stuff
> > being case-sensitive, of course.)
>
>I believe that I shall. Realizing that leaving "VMS" in the subject
> line will probably cause this inquiry to sink without trace, I continue,
>
> [...] (One might question the cleverness of that stuff
> being case-sensitive, of course.)
I believe that I shall. Realizing that leaving "VMS" in the subject
line will probably cause this inquiry to sink without trace, I continue,
oblivious ...
http://openssl.org/docs/apps/cms.html
> http://antinode.info/ftp/openssl/1_0_0/test/
Now contains some new and updated files to add a helper program for
the perl system() function on VMS systems. Relatively recent, non-VAX
VMS systems with SET PROCESS /PARSE_STYLE = EXTENDED, that is. Without
extra quotation on system() arg
Hello!
1. I believe there are a couple of bugs in cms.h -
diff -ur openssl/crypto/cms/cms.h openssl-1.1.0/crypto/cms/cms.h
--- openssl/crypto/cms/cms.h 2010-04-07 20:22:01.185601800 +0600
+++ openssl-1.1.0/crypto/cms/cms.h 2010-04-24 12:39:05.350609800
+0600
@@ -56,9 +56,9 @@
#define HEADER_CMS_
For the morbidly curious, I may have a working LIB$INITIALIZE module
for OpenSSL, which would cause it to preserve case for its command-line
arguments (on modern, non-VAX systems, with SET PROCESS /PARSE_STYLE =
EXTENDED). That stuff should be in:
http://antinode.info/ftp/openssl/1_0_0/a
From: "Jouk Jansen"
> Parse Style: Extended
>
> Case Lookup: Blind
>
> So I assumed it was because of the extended parse style.
Never assume. ( http://en.wikipedia.org/wiki/Desk_Set Everyone
needs to see this movie.)
My next guess would be that you have some CRTL feature logical
name(
SMS wrote:
>I don't have this problem.
>
> show process /case_lookup /parse_style
>
>Are you having trouble because of "/parse_style = extended" or
>"/case_lookup = sensitive"?
troika-jj) show process /case_lookup /parse_style
26-APR-2010 08:45:08.19 User: JOUKJProcess ID: 23
From: "Jouk Jansen"
> > http://antinode.info/ftp/openssl
> I tested the 1.0.0-s1 set from your web-page, but it has exactly the same
> problem when running the tests:
> [...]
> testing X509 conversions
> p -> d
> p -> n
> p -> p
> d -> d
> n -> d
> p -> d
> d -> n
> n -> n
> p -> n
> d -> p
Steven wrote on 16-APR-2010 17:14:47.36
>From: "Jouk Jansen"
>
>> When building OpenSSL on a OpenVMS machine, while "extended parse style is
>> on (i.e set proc/parse=extend) some of the tests fail. The solution is
>> simple : add a few
openssl-dev@openssl.org wrote on 16-APR-2010 17:14:47.36
>From: "Jouk Jansen"
[snip]
>> [...] I put the
>> "corrected" files on my web-page:
>>http://nchrem.tnw.tudelft.nl/openvms/software2.html#OSSL
>
> "0.9.8l" and "1.0.0-beta2" are hardly current. But don't worry.
>There are still ple
From: "Jouk Jansen"
> When building OpenSSL on a OpenVMS machine, while "extended parse style is
> on (i.e set proc/parse=extend) some of the tests fail. The solution is
> simple : add a few double quotes in the command procedures. [...]
Because practically every
Hi All,
When building OpenSSL on a OpenVMS machine, while "extended parse style is
on (i.e set proc/parse=extend) some of the tests fail. The solution is
simple : add a few double quotes in the command procedures. I put the
"corrected" files on my web-page:
http://nchrem.tnw.tud
1 - 100 of 167 matches
Mail list logo
