Re: building openssl for windows - missing do_win64a from ms directory.

[Richard Levitte]

I'd suggest reading the files called 'README' and 'INSTALL' as a start.

Cheers
Richard


"Lewis, Michael L"  skrev: (11 juni 2019 18:55:48 
CEST)
>Hi,
>
>I'm trying to build OpenSSL for windows (openssl-1.1.1c), I do the
>following steps:
>
>
>1.   cd into open ssl directory.
>
>2.   Run: perl Configure VC-WIN64A, this appears to work fine ...
>
>
>
>C:\develop\ignite\openssl-1.1.1c>perl Configure VC-WIN64A
>
>Configuring OpenSSL version 1.1.1c (0x1010103fL) for VC-WIN64A
>
>Using os-specific seed configuration
>
>Creating configdata.pm
>
>Creating makefile
>
>The issue I have is that I don't see 'do_win64a' within the 'ms'
>directory (I'm following build instructions here:
>http://eran.geek.co.il/wp/archives/3897
>and
>https://wiki.openssl.org/index.php/Compilation_and_Installation#W64)
>
>Anyone have any ideas on what I'm doing wrong? (The output from perl
>configdata.pm -dump is shown below).
>
>Thanks,
>Mike Lewis
>
>
>C:\develop\ignite\openssl-1.1.1c>perl configdata.pm -dump
>
>Command line (with current working directory = .):
>
>C:\Strawberry\perl\bin\perl.exe Configure VC-WIN64A
>
>Perl information:
>
>C:\Strawberry\perl\bin\perl.exe
>5.12.3 for MSWin32-x86-multi-thread
>
>Enabled features:
>
>aria
>asm
>async
>autoalginit
>autoerrinit
>autoload-config
>bf
>blake2
>buildtest-c\+\+
>camellia
>capieng
>cast
>chacha
>cmac
>cms
>comp
>ct
>deprecated
>des
>dgram
>dh
>dsa
>dtls
>dynamic-engine
>ec
>ec2m
>ecdh
>ecdsa
>engine
>err
>filenames
>gost
>hw(-.+)?
>idea
>makedepend
>md4
>mdc2
>multiblock
>nextprotoneg
>pinshared
>ocb
>ocsp
>pic
>poly1305
>posix-io
>psk
>rc2
>rc4
>rdrand
>rfc3779
>rmd160
>scrypt
>seed
>shared
>siphash
>sm2
>sm3
>sm4
>sock
>srp
>srtp
>sse2
>ssl
>static-engine
>stdio
>tests
>threads
>tls
>ts
>ui-console
>whirlpool
>tls1
>tls1-method
>tls1_1
>tls1_1-method
>tls1_2
>tls1_2-method
>tls1_3
>dtls1
>dtls1-method
>dtls1_2
>dtls1_2-method
>
>Disabled features:
>
>afalgeng[not-linux]
>asan[default]   OPENSSL_NO_ASAN
>crypto-mdebug   [default]   OPENSSL_NO_CRYPTO_MDEBUG
> crypto-mdebug-backtrace [default]   OPENSSL_NO_CRYPTO_MDEBUG_BACKTRACE
>devcryptoeng[default]   OPENSSL_NO_DEVCRYPTOENG
>ec_nistp_64_gcc_128 [default]   OPENSSL_NO_EC_NISTP_64_GCC_128
>egd [default]   OPENSSL_NO_EGD
>external-tests  [default]   OPENSSL_NO_EXTERNAL_TESTS
>fuzz-libfuzzer  [default]   OPENSSL_NO_FUZZ_LIBFUZZER
>fuzz-afl[default]   OPENSSL_NO_FUZZ_AFL
>heartbeats  [default]   OPENSSL_NO_HEARTBEATS
>   md2 [default]   OPENSSL_NO_MD2 (skip crypto\md2)
>msan[default]   OPENSSL_NO_MSAN
>   rc5 [default]   OPENSSL_NO_RC5 (skip crypto\rc5)
>sctp[default]   OPENSSL_NO_SCTP
>ssl-trace   [default]   OPENSSL_NO_SSL_TRACE
>ubsan   [default]   OPENSSL_NO_UBSAN
>unit-test   [default]   OPENSSL_NO_UNIT_TEST
>weak-ssl-ciphers[default]   OPENSSL_NO_WEAK_SSL_CIPHERS
>zlib[default]
>zlib-dynamic[default]
>ssl3[default]   OPENSSL_NO_SSL3
>ssl3-method [default]   OPENSSL_NO_SSL3_METHOD
>
>Config target attributes:
>
>AR => "lib",
>ARFLAGS => "/nologo",
>AS => "nasm",
>ASFLAGS => "-g",
>CC => "cl",
>CFLAGS => "/W3 /wd4090 /nologo /O2",
>CPP => "\$(CC) /EP /C",
>HASHBANGPERL => "/usr/bin/env perl",
>LD => "link",
>LDFLAGS => "/nologo /debug",
>MT => "mt",
>MTFLAGS => "-nologo",
>RANLIB => "CODE(0x253c2ac)",
>RC => "rc",
>aes_asm_src => "aes-x86_64.s vpaes-x86_64.s bsaes-x86_64.s
>aesni-x86_64.s aesni-sha1-x86_64.s aesni-sha256-x86_64.s
>aesni-mb-x86_64.s",
&

Re: building openssl for windows - missing do_win64a from ms directory.

[Salz, Rich via openssl-users]

  *   The issue I have is that I don’t see ‘do_win64a’ within the ‘ms’ 
directory (I’m following build instructions here: 
http://eran.geek.co.il/wp/archives/3897
 and https://wiki.openssl.org/index.php/Compilation_and_Installation#W64 )

Those files are outdated; look at the NOTES.WIN file.

(PS that email disclaimer is obnoxious, it’d be great if you could get it 
disabled.)

building openssl for windows - missing do_win64a from ms directory.

[Lewis, Michael L]

Hi,

I'm trying to build OpenSSL for windows (openssl-1.1.1c), I do the following 
steps:


1.   cd into open ssl directory.

2.   Run: perl Configure VC-WIN64A, this appears to work fine ...



C:\develop\ignite\openssl-1.1.1c>perl Configure VC-WIN64A

Configuring OpenSSL version 1.1.1c (0x1010103fL) for VC-WIN64A

Using os-specific seed configuration

Creating configdata.pm

Creating makefile

The issue I have is that I don't see 'do_win64a' within the 'ms' directory (I'm 
following build instructions here: http://eran.geek.co.il/wp/archives/3897
and https://wiki.openssl.org/index.php/Compilation_and_Installation#W64)

Anyone have any ideas on what I'm doing wrong? (The output from perl 
configdata.pm -dump is shown below).

Thanks,
Mike Lewis


C:\develop\ignite\openssl-1.1.1c>perl configdata.pm -dump

Command line (with current working directory = .):

C:\Strawberry\perl\bin\perl.exe Configure VC-WIN64A

Perl information:

C:\Strawberry\perl\bin\perl.exe
5.12.3 for MSWin32-x86-multi-thread

Enabled features:

aria
asm
async
autoalginit
autoerrinit
autoload-config
bf
blake2
buildtest-c\+\+
camellia
capieng
cast
chacha
cmac
cms
comp
ct
deprecated
des
dgram
dh
dsa
dtls
dynamic-engine
ec
ec2m
ecdh
ecdsa
engine
err
filenames
gost
hw(-.+)?
idea
makedepend
md4
mdc2
multiblock
nextprotoneg
pinshared
ocb
ocsp
pic
poly1305
posix-io
psk
rc2
rc4
rdrand
rfc3779
rmd160
scrypt
seed
shared
siphash
sm2
sm3
sm4
sock
srp
srtp
sse2
ssl
static-engine
stdio
tests
threads
tls
ts
ui-console
whirlpool
tls1
tls1-method
tls1_1
tls1_1-method
tls1_2
tls1_2-method
tls1_3
dtls1
dtls1-method
dtls1_2
dtls1_2-method

Disabled features:

afalgeng[not-linux]
asan[default]   OPENSSL_NO_ASAN
crypto-mdebug   [default]   OPENSSL_NO_CRYPTO_MDEBUG
crypto-mdebug-backtrace [default]   OPENSSL_NO_CRYPTO_MDEBUG_BACKTRACE
devcryptoeng[default]   OPENSSL_NO_DEVCRYPTOENG
ec_nistp_64_gcc_128 [default]   OPENSSL_NO_EC_NISTP_64_GCC_128
egd [default]   OPENSSL_NO_EGD
external-tests  [default]   OPENSSL_NO_EXTERNAL_TESTS
fuzz-libfuzzer  [default]   OPENSSL_NO_FUZZ_LIBFUZZER
fuzz-afl[default]   OPENSSL_NO_FUZZ_AFL
heartbeats  [default]   OPENSSL_NO_HEARTBEATS
md2 [default]   OPENSSL_NO_MD2 (skip crypto\md2)
msan[default]   OPENSSL_NO_MSAN
rc5 [default]   OPENSSL_NO_RC5 (skip crypto\rc5)
sctp[default]   OPENSSL_NO_SCTP
ssl-trace   [default]   OPENSSL_NO_SSL_TRACE
ubsan   [default]   OPENSSL_NO_UBSAN
unit-test   [default]   OPENSSL_NO_UNIT_TEST
weak-ssl-ciphers[default]   OPENSSL_NO_WEAK_SSL_CIPHERS
zlib[default]
zlib-dynamic[default]
ssl3[default]   OPENSSL_NO_SSL3
ssl3-method [default]   OPENSSL_NO_SSL3_METHOD

Config target attributes:

AR => "lib",
ARFLAGS => "/nologo",
AS => "nasm",
ASFLAGS => "-g",
CC => "cl",
CFLAGS => "/W3 /wd4090 /nologo /O2",
CPP => "\$(CC) /EP /C",
HASHBANGPERL => "/usr/bin/env perl",
LD => "link",
LDFLAGS => "/nologo /debug",
MT => "mt",
MTFLAGS => "-nologo",
RANLIB => "CODE(0x253c2ac)",
RC => "rc",
aes_asm_src => "aes-x86_64.s vpaes-x86_64.s bsaes-x86_64.s aesni-x86_64.s 
aesni-sha1-x86_64.s aesni-sha256-x86_64.s aesni-mb-x86_64.s",
aes_obj => "aes-x86_64.o vpaes-x86_64.o bsaes-x86_64.o aesni-x86_64.o 
aesni-sha1-x86_64.o aesni-sha256-x86_64.o aesni-mb-x86_64.o",
apps_aux_src => "win32_init.c",
apps_init_src => "../ms/applink.c",
apps_obj => "win32_init.o",
aroutflag => "/out:",
asflags => "-Ox -f win64 -DNEAR",
asoutflag => "-o ",
bf_asm_src => "bf_enc.c",
bf_obj => "bf_enc.o",
bin_cflags => "/Zi /Fdapp.pdb",
bin_lflags => "/subsystem:console /opt:ref",
bn_asm_src => "bn_asm.c x86_64-mont.s x86_64-mont5.s x86_64-gf2m.s 
rsaz_exp.c rsaz-x86_64.s rsaz-avx2.s",
bn_obj => "bn_asm.o x86_64-mont.o x86_64-mont5.o x86_64-gf2m.o rsaz_exp.o 
rsaz-x86_64.o rsaz-avx2.o",
bn_ops =

Re: Signing .JAR files using OpenSSL for Windows

[Jakob Bohm]

On 01/09/2014 16:17, AUser ZUser wrote:




Hello
Can someone please help me with the following question.
I have a code signing certicate in my X509 store "LocalMachine\My" which I can 
use for signing PowerShell scripts for example
Set-AuthenticodeSignature ./MyScript.ps1 -certificate ( gci 
cert:\LocalMachine\My -CodeSigning)
No worries there
>From the information I have re "AthentiCode" as above, the only file formats 
it currently supports are

 *
.cab files

 *
.cat files

 *
.ctl files

 *
.dll files

 *
.exe files

 *
.ocx and

Now the UNIX guys also need their .JAR files signing (they do not have the code 
signing cert)
So I want thinking along the following lines but need some help please
I downloaded OpenSSL for Windows and Install
What I want to do use OpenSSL from the Windows command line to sign a .jar file
I do not want to expose the code signing certificate by having is as a flat 
file (e.g. CodeSigningCert.pfx) on the file system, rather I would prefer  to 
keep it in the X509 store (whereby the private key is not exportable) and refer 
to the cert on the OpenSSL command line when signing the .jar file.
Is this possible? can any one please show me a few command line examples? if 
this is not possible is there another utility I can use to achive the above
Thanks All
AAnotherUser__






Note: I have successfully signed jar files (actually apk files,
which are jar files with different contents) using the openssl
command line, plus some scripting.

Basically, jar files are zip files containing extra files
describing the signature.  There is a specification on Oracle's
site, but fundamentally:

META-INF/MANIFEST.MF   contains hashes of all non-signature files
   in the zip file, this is generated when you
   sign the jar with any certificate (even an
   unimportant dummy key). This is a text file.

META-INF/$signaturename.SF  contains hashes of various parts of
MANIFEST.MF.  This too is generated
when you sign the jar with any
certificate, even though there is one
copy of this file for each signature.
This is a text file.

META-INF/$signaturename.RSA is the output from running the following
command (this is a binary file):

openssl cms -sign -outform DER -noattr -md $hashname \
   -signer $whatever.pem $engineorprivkeyoptions \
   < $signaturename.SF > $signaturename.RSA

META-INF/$signaturename.DSA is the same as the .RSA file if your
certificate happens to use a DSA public key.

So one way (there are more advanced ways) is to sign with a dummy
(unimportant, no security) key using jarsigner, then extract
META-INF/$signaturename.SF, pass it to openssl with appropriate
engine options, then use a generic ZIP program to replace the
dummy $signaturename.RSA with the real one.

Enjoy

Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S.  http://www.wisemo.com
Transformervej 29, 2730 Herlev, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded


__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org

Re: Signing .JAR files using OpenSSL for Windows

[Benny Baumann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Am 01.09.2014 16:17, schrieb AUser ZUser:
> Hello Can someone please help me with the following question. I
> have a code signing certicate in my X509 store "LocalMachine\My"
> which I can use for signing PowerShell scripts for example 
> Set-AuthenticodeSignature ./MyScript.ps1 -certificate ( gci 
> cert:\LocalMachine\My -CodeSigning) No worries there
>> From the information I have re "AthentiCode" as above, the only
>> file
> formats it currently supports are
> 
> * .cab files * .cat files * .ctl files * .dll files * .exe files *
> .ocx and
> 
> Now the UNIX guys also need their .JAR files signing (they do not
> have the code signing cert) So I want thinking along the following
> lines but need some help please I downloaded OpenSSL for Windows
> and Install What I want to do use OpenSSL from the Windows command
> line to sign a .jar file I do not want to expose the code signing
> certificate by having is as a flat file (e.g. CodeSigningCert.pfx)
> on the file system, rather I would prefer  to keep it in the X509
> store (whereby the private key is not exportable) and refer to the
> cert on the OpenSSL command line when signing the .jar file.
For JAR signing you might want to refer to [1] - the things written
there are not specific to CAcert, but give a general outline.
> Is this possible?
Not without exposing it on the filesystem as far as I know. JarSigner
(the Tool from Java) wants to have it in its own keystore, which is a
file on disk.
> can any one please show me a few command line examples?
Sure. Have a look at the link I gave.
> if this is not possible is there another utility I can use to 
> achive the above
See above.
> Thanks All AAnotherUser__

Regards,
BenBE.

[1]
http://wiki.cacert.org/CodesigningCert#How_can_I_use_my_code_signing_certificate.3F_.28java_example.29
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCgAGBQJUBWV0AAoJEPHTXLno4S6tNWoP/2kGhOZ+Lmi3dpzp88tayG5Q
nx4Tfyk8GyjoWwxOQ0Vgfrq6yf157AqWjmXEQ9fk/1vT7cW5mdlAfOI5mAcDRIzW
ED+gB9x7Ch/GP6f7T8i985h9pDpmFX/8QZDucRr4phEYJxNERvC+jjNIscN+lY8U
M230hfUgGZdlQ7OtPX0Jvy+frNG0c/hqrFSfR3xQNkEyh1OAcmRUwDjoW7kk4STJ
da+cLj1mIRXEIkTMed0VpDEM0L58ZEbx5OsXNwXvFiItGDsO28YH4uvQ+RvQA8Km
hUKfEnxnVHPGJJ77PTbYHtvYQnmZ0iz5kuA3ORM8RyknKtL8/Gtr6cJWva60xwyg
isnd45OlHhj74wH8PI3HT3snvv1rKIZG60SYV4v48Qk790Zuy6FH3h8VbHn255Mw
n0NDyhFwl3vzOnoE92MFpSXfiS6z0oz+YLKd7o4ZWGJe/pog9vy0BweNMBfls9tI
y+xcARivHcsqxB1BdTZ+NIcxFzHwxXeGQyeVyMDeyZz8/hF7Sioqrwu+3agEEioC
tTk3da1ImQx6mo1zmxC52afqyIGaX7qTVfXnXeUVyoeDvl1tlJgeh93s4gQJKi52
nZG2jAqkx0oR5YHwHP+RlTXBD47PKGEl94ncCEF/6wneRKIx+jklmXvXFS7DPVR4
ZH2JtDxR77LKW+0Fx1z8
=W8pg
-END PGP SIGNATURE-
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org

RE: Signing .JAR files using OpenSSL for Windows

[Porter, Andrew]

For jars you need to use the jarsigner utility in the Java Development Kit 
(JDK). This can access certs in the Windows personal and root certificate 
stores, see



http://www.oracle.com/technetwork/articles/javase/security-137537.html



using "Windows-MY" or "Windows-ROOT" for the KeyStore parameter instead of the 
name of a keystore file.



Andrew

Signing .JAR files using OpenSSL for Windows

[AUser ZUser]

Hello

Can someone please help me with the following question.

I have a code signing certicate in my X509 store "LocalMachine\My" which I can 
use for signing PowerShell scripts for example

Set-AuthenticodeSignature ./MyScript.ps1 -certificate ( gci 
cert:\LocalMachine\My -CodeSigning)

No worries there

>From the information I have re "AthentiCode" as above, the only file formats 
>it currently supports are


.cab files
.cat files
.ctl files
.dll files
.exe files
.ocx and
Now the UNIX guys also need their .JAR files signing (they do not have the code 
signing cert)

So I want thinking along the following lines but need some help please

I downloaded OpenSSL for Windows and Install

What I want to do use OpenSSL from the Windows command line to sign a .jar file

I do not want to expose the code signing certificate by having is as a flat 
file (e.g. CodeSigningCert.pfx) on the file system, rather I would prefer  to 
keep it in the X509 store (whereby the private key is not exportable) and refer 
to the cert on the OpenSSL command line when signing the .jar file.

Is this possible? can any one please show me a few command line examples? if 
this is not possible is there another utility I can use to achive the above

Thanks All

AAnotherUser__

  

Compiling OpenSSL for Windows Mobile 6.1 with VS 2008

[Thomas Harning Jr.]

Has anyone tackled getting OpenSSL to compile for Windows Mobile 6.1
with Visual Studio 2008?

There appears to be some instructions for setting it up to compile
with EVC++ 4 and VS 2005, which provide the necessary runtime
environments... however VS 2008 does not provide them.

Are there any recommended ways to get OpenSSL to build for WM6.1?

-- 
Thomas Harning Jr.
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   majord...@openssl.org

OpenSSL for Windows

[Ariel Sanchez]

Good afternoon, sir.

 

Using v.0.9.8g, on Windows XP SP3 (FTP Server), logged in as Local 

Administrator account.

 

I was hoping to get some insight as to why I am getting the following 

errors (I hope you can see these screen shots)

 

I tried the "g" version since v.0.9.8h was giving me other issues 

 (i.e., command line error: "openssl" or "openssl.exe" is not a 

recognized internal or external command). I'm trying to generate a 

key, then csr file to send to VeriSign in order to download a
certificate.

 

Any insight would be much appreciated.

 

Thanks in advance.

 

 

Ariel Sanchez

[EMAIL PROTECTED]  

 

Re: OpenSSL For Windows CE

[Panthers Rock]

I have never compiled OpenSSL for Windows CE.  However, it seems that you
need to change compiler and linker options to say it is for an ARM
processor.   Look for CFLAGS and LFLAGS and make appropriate changes.


On Mon, Jul 21, 2008 at 10:28 AM, Amir <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I saw your message in the openssl-dev mailing list about building openSSL
> for windows CE and i'm trying to do the same thing.
>
> I want to buil the openSSL libraries for Windows CE following those steps :
>
> Building
> 
>
> Setup the eMbedded Visual C++ environment.  There are batch files for doing
> this installed with eVC++.  For an ARM processor, for example, execute:
>
> > "C:\Program Files\Microsoft eMbedded Tools\EVC\WCE300\BIN\WCEARM.BAT"
>
> Next indicate where wcecompat is located:
>
> > set WCECOMPAT=C:\wcecompat
>
> Next you should run Configure:
>
> > perl Configure VC-CE
>
> Next you need to build the Makefiles:
>
> > ms\do_ms
>
> If you get errors about things not having numbers assigned then check the
> troubleshooting section in INSTALL.W32: you probably won't be able to
> compile
> it as it stands.
>
> Then from the VC++ environment at a prompt do:
>
> - to build static libraries:
>
> > nmake -f ms\ce.mak
>
> When i try to excute the last step : nmake -f ms\ce.mak, i got the
> following problem :
>
> tmp32_\md2test.obj: fatal error LINK1112: module machine type 'X86'
> conflicts with target machine type 'ARM'.
>
> Please, did you have any idea about solving this problem?
>
> or did you know where can i get the openSSL library already builded for
> Windows CE?
>
> Thanks,
> Amir,
>

OpenSSL For Windows CE

[Amir]

Hi,

I saw your message in the openssl-dev mailing list about building 
openSSL for windows CE and i'm trying to do the same thing.


I want to buil the openSSL libraries for Windows CE following those steps :

Building


Setup the eMbedded Visual C++ environment.  There are batch files for doing
this installed with eVC++.  For an ARM processor, for example, execute:

> "C:\Program Files\Microsoft eMbedded Tools\EVC\WCE300\BIN\WCEARM.BAT"

Next indicate where wcecompat is located:

> set WCECOMPAT=C:\wcecompat

Next you should run Configure:

> perl Configure VC-CE

Next you need to build the Makefiles:

> ms\do_ms

If you get errors about things not having numbers assigned then check the
troubleshooting section in INSTALL.W32: you probably won't be able to 
compile

it as it stands.

Then from the VC++ environment at a prompt do:

- to build static libraries:

> nmake -f ms\ce.mak

When i try to excute the last step : nmake -f ms\ce.mak, i got the 
following problem :


tmp32_\md2test.obj: fatal error LINK1112: module machine type 'X86' 
conflicts with target machine type 'ARM'.


Please, did you have any idea about solving this problem?

or did you know where can i get the openSSL library already builded for 
Windows CE?


Thanks,
Amir,
begin:vcard
fn:Amir Krifa
n:Krifa;Amir
email;internet:[EMAIL PROTECTED]
tel;quoted-printable;work:Ing=C3=A9nieur Expert, INRIA Sophia-Antipolis
tel;home:Antibes, France
tel;cell:0033637297010
url:www-sop.inria.fr/planete/personnel/Amir.Krifa/
version:2.1
end:vcard

Re: openssl for windows file separator

[larry.dalton]

Tried that, only with single quotes. Forward slashes, 
back, and double back. Doesn't seem anything works for the pc, at least what I 
use. UNIX works, PC only works if all files are in the same 
directory.

  - Original Message - 
  From: 
  Kyle Hamilton 
  
  To: openssl-users@openssl.org 
  Sent: Friday, June 23, 2006 10:04 
PM
  Subject: Re: openssl for windows file 
  separator
  How do you mean?  Windows will support the forward slash 
  convention,as will openssl.  If you use backslashes, you may need to 
  double them. If you are using a space in any of the directory or 
  filenames, thefull path must be surrounded by doublequotes or else OpenSSL 
  willinterpret it as two different arguments.I don't recall the 
  specifics at this moment, unfortunately --allergies plus chlortrimeton 
  make for bad memory.  However, try thesuggestions that I mention 
  above, and report back with your findings.:)-Kyle HOn 
  6/23/06, larry.dalton <[EMAIL PROTECTED]> 
  wrote:>>> What arguments do you use when using openssl 
  for windows to make full path> to the file in the openssl arguments 
  work?>> [EMAIL PROTECTED]>>__OpenSSL 
  Project 
  http://www.openssl.orgUser Support 
  Mailing 
  List    
  openssl-users@openssl.orgAutomated 
  List 
  Manager   
  [EMAIL PROTECTED]-- 
  No virus found in this incoming message.Checked by AVG Free 
  Edition.Version: 7.1.394 / Virus Database: 268.9.3/374 - Release Date: 
  6/23/2006

Re: openssl for windows file separator

[Kyle Hamilton]

How do you mean?  Windows will support the forward slash convention,
as will openssl.  If you use backslashes, you may need to double them.
If you are using a space in any of the directory or filenames, the
full path must be surrounded by doublequotes or else OpenSSL will
interpret it as two different arguments.

I don't recall the specifics at this moment, unfortunately --
allergies plus chlortrimeton make for bad memory.  However, try the
suggestions that I mention above, and report back with your findings.
:)

-Kyle H

On 6/23/06, larry.dalton <[EMAIL PROTECTED]> wrote:



What arguments do you use when using openssl for windows to make full path
to the file in the openssl arguments work?

[EMAIL PROTECTED]



__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   [EMAIL PROTECTED]

openssl for windows file separator

[larry.dalton]

What arguments do you use when using openssl for 
windows to make full path to the file in the openssl arguments 
work?
 
[EMAIL PROTECTED]
 
 

trouble building openssl for windows

[Charles Summey]

Trying, unsuccessfully, to build OpenSSL 0.9.7e, downloaded from
www.openssl.org, for Win32 following the procedure detailed in the
'Install.w32' document.

Successfully ran Configure, built the Makefiles and assembly language files,
but failed to make ntdll. Error messages a little too cryptic (no pun
intended).  nmake I have is for Open Watcom C/C++.

Output from my attempt:

C:\DOWNLO~1\OpenSSL>perl Configure VC-WIN32 Configuring for VC-WIN32
IsWindows=1
CC=cl
CFLAG =-DOPENSSL_SYSNAME_WIN32 -DOPENSSL_THREADS  -DDSO_WIN32
-DOPENSSL_NO_KRB5
EX_LIBS   =
BN_ASM=bn_asm.o
DES_ENC   =des_enc.o fcrypt_b.o
BF_ENC=bf_enc.o
CAST_ENC  =c_enc.o
RC4_ENC   =rc4_enc.o
RC5_ENC   =rc5_enc.o
MD5_OBJ_ASM   =
SHA1_OBJ_ASM  =
RMD160_OBJ_ASM=
PROCESSOR =
RANLIB=true
ARFLAGS   =
PERL  =perl
THIRTY_TWO_BIT mode
BN_LLONG mode
RC4_INDEX mode
RC4_CHUNK is undefined

Configured for VC-WIN32.

C:\DOWNLO~1\OpenSSL>ms\do_masm

C:\DOWNLO~1\OpenSSL>rem use "fips" as the first argument to make a proper
FIPS build.
Generating x86 for MASM assember
Bignum
DES
"crypt(3)"
Blowfish
CAST5
RC4
MD5
SHA1
RIPEMD160
RC5\32

C:\DOWNLO~1\OpenSSL>perl util\mkfiles.pl  1>MINFO

C:\DOWNLO~1\OpenSSL>rem perl util\mk1mf.pl no-sock  VC-MSDOS >ms\msdos.mak

C:\DOWNLO~1\OpenSSL>rem perl util\mk1mf.pl  VC-W31-32 >ms\w31.mak

C:\DOWNLO~1\OpenSSL>perl util\mk1mf.pl dll  VC-W31-32  1>ms\w31dll.mak

C:\DOWNLO~1\OpenSSL>perl util\mk1mf.pl  VC-WIN32  1>ms\nt.mak

C:\DOWNLO~1\OpenSSL>perl util\mk1mf.pl dll  VC-WIN32  1>ms\ntdll.mak

C:\DOWNLO~1\OpenSSL>perl util\mkdef.pl 16 libeay   1>ms\libeay16.def

C:\DOWNLO~1\OpenSSL>perl util\mkdef.pl 32 libeay   1>ms\libeay32.def

C:\DOWNLO~1\OpenSSL>perl util\mkdef.pl 16 ssleay   1>ms\ssleay16.def

C:\DOWNLO~1\OpenSSL>perl util\mkdef.pl 32 ssleay   1>ms\ssleay32.def

C:\DOWNLO~1\OpenSSL>nmake -f ms\ntdll.mak Open Watcom C/C++ NMAKE Clone for
386  Version 1.2 Portions Copyright (c) 1995-2002 Sybase, Inc. All Rights
Reserved.
Source code is available under the Sybase Open Watcom Public License.
See http://www.openwatcom.org/ for details.
Building OpenSSL
copy nul+ .\crypto\buildinf.h tmp32dll\buildinf.h nul .\crypto\buildinf.h
1 file(s) copied.
copy nul+ .\crypto\opensslconf.h inc32\openssl\opensslconf.h nul
.\crypto\opensslconf.h
1 file(s) copied.
Error(E14): Cannot execute (): No such file or directory
Error(E42): Last command making (headers) returned a bad status
Error(E02): Make execution terminated

C:\DOWNLO~1\OpenSSL>



Charles Summey
Software/Systems Engineer
Video Gaming Technologies (VGT) Inc.
4353 Seminole Trail
US 29 North
Charlottesville, VA 22911
[EMAIL PROTECTED]
(434)817-7070 x-109

<>

RE: openssl for windows ce "tchar" problem

[Steven Reddie]

In anticipation of your response...  char is the type that has been used to
represent a character in C for a very long time now, in fact I've read that
it dates back to the same time as C's "if" keyword.  TCHAR is a newish type
defined by Microsoft that is equivalent to a char when doing a non-Unicode
build and equivalent to a wide char (WCHAR) when doing a Unicode build.
OpenSSL is platform-independant and therefore does not use such
Microsoft-specific types in it's interface.  If you wish to use OpenSSL on a
Unicode system such as Windows CE you may at times need to convert between
ASCII char's and Unicode WCHAR's.  This is not a problem specific to
OpenSSL, nor To Windows CE; it is a requirement of mixing ASCII and Unicode
in a single program.  The Win32 functions WideCharToMultiByte and
MultiByteToWideChar will help you with the conversions.

Regards,

Steven

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Steven Reddie
Sent: Friday, 20 June 2003 12:22 AM
To: [EMAIL PROTECTED]
Subject: RE: openssl for windows ce "tchar" problem


Can you give me an example of an OpenSSL function that uses a char type
where you expect to be able to use a TCHAR type?

Regards,

Steven

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Antonio d'Errico
Sent: Thursday, 19 June 2003 7:48 PM
To: [EMAIL PROTECTED]
Subject: openssl for windows ce "tchar" problem


Hi,

i'm building a windows ce project for pocket pc 2002 with the openssl 0.9.7b
e wcecompat support.
I have some problems using TCHAR type in functions defined in openssl
include files (.h) and libraries, but i must use TCHAR type for the correct
visualization about the device!
Why openssl libraries for windows ce using char type and not TCHAR type?
it's normal? How I do?
Thanks for any suggestions

_
MSN Foto: condividi, ritocca e stampa le tue foto online
http://photos.msn.it

__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

RE: openssl for windows ce "tchar" problem

[Steven Reddie]

Can you give me an example of an OpenSSL function that uses a char type
where you expect to be able to use a TCHAR type?

Regards,

Steven

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Antonio d'Errico
Sent: Thursday, 19 June 2003 7:48 PM
To: [EMAIL PROTECTED]
Subject: openssl for windows ce "tchar" problem


Hi,

i'm building a windows ce project for pocket pc 2002 with the openssl 0.9.7b
e wcecompat support.
I have some problems using TCHAR type in functions defined in openssl
include files (.h) and libraries, but i must use TCHAR type for the correct
visualization about the device!
Why openssl libraries for windows ce using char type and not TCHAR type?
it's normal? How I do?
Thanks for any suggestions

_
MSN Foto: condividi, ritocca e stampa le tue foto online
http://photos.msn.it

__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

RE: openssl for windows?

[Imran Badr]

http://www.iconsinc.com/~agray/ossldev/
 
 

  -Original Message-From: 
  [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On 
  Behalf Of park hkSent: Wednesday, October 31, 2001 5:51 
  PMTo: [EMAIL PROTECTED]Subject: openssl for 
  windows?
  I'm poor at English.
  I'd like to know there is the openssl for 
  windows.
   
  Thank you!!

openssl for windows?

[park hk]

I'm poor at English.
I'd like to know there is the openssl for 
windows.
 
Thank you!!

Re: openssl for windows

[Mike_Bryeans]

In Article <001501bff8b1$04439120$4c3e36d5@pac>
"ukoeppe" <[EMAIL PROTECTED]> writes:

> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, July 28, 2000 6:50 PM
> Subject: openssl for windows
> 
> 
> > Anybody know where I can get openssl already compiled for WIndows? I
> don't
> > have perl installed, have no interest in having it installed, so I can't
> > compile the source for Windows.
> 
> Wow, a kindred spirit .
> There is some version (I think from May 1999) at
> http://mail-archive.cashcow.dk/msg00114.html   , look for openssl.zip. Tell
> you what, if you know where to put the openssl.cnf let me know, OK?

If I figure it out, I'll let you know.

---
WebBBS Pro v1.19 : Genesis ( http://www.webbbs.org/ )

__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: openssl for windows

[ukoeppe]

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 28, 2000 6:50 PM
Subject: openssl for windows


> Anybody know where I can get openssl already compiled for WIndows? I don't
> have perl installed, have no interest in having it installed, so I can't
> compile the source for Windows.

Wow, a kindred spirit .
There is some version (I think from May 1999) at
http://mail-archive.cashcow.dk/msg00114.html   , look for openssl.zip. Tell
you what, if you know where to put the openssl.cnf let me know, OK?

Uli Koeppe mailto [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

openssl for windows

[Mike_Bryeans]

Anybody know where I can get openssl already compiled for WIndows? I don't
have perl installed, have no interest in having it installed, so I can't
compile the source for Windows.

---
WebBBS Pro v1.19 : Genesis ( http://www.webbbs.org/ )

__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]