RE: OpenSSL 1.1.1b tests fail on Solaris

[Karl Vogel]

>> In a previous message, I saw:

> Does the Bind Type WEAK indicate anything?

Grasping at straws here, but I had to patch one of the assembler
files in the past on Solaris.  The patch is below.

  me% cd /path/to/openssl/src/crypto/bn/asm

  me% patch < /tmp/sparcv9a-mont.pl.patch 
Looks like a unified context diff.
  done

--
Karl Vogel / I don't speak for the USAF or my company

"Auntie Em:  hate you, hate Kansas, taking the dog."  -Dorothy
--bumper sticker
--- sparcv9a-mont.pl.orig   2017-05-25 08:54:34.0 -0400
+++ sparcv9a-mont.pl2017-10-13 22:34:19.073600500 -0400
@@ -124,6 +124,7 @@
 .section   ".text",#alloc,#execinstr
 
 .global $fname
+.weak $fname
 .align  32
 $fname:
save%sp,-$frame-$locals,%sp

Re: Building OpenSSL with Emscripten

[Sunghyun Park]

Hi, all. Thanks for your help, I could finish compilation to the end.
However, athough I successfully compiled with _no-asm_ options, I found a
problem when loading the compiled library in the 3rd party code base.
When looking into the source code, the definition of some function seems to
require a specific preprocessor to be compiled.
(For example, PEM_write_bio_DSAPrivateKey needs '#define OPENSSL_FIPS'.)
I installed *openssl-1.0.2r.tar.gz *and only provided *no-asm* for
configuration.
Am I missing some dependencies or necessary options?
The error I'm facing is as follows:


error: undefined symbol: AES_ctr128_encrypt
warning: To disable errors for undefined symbols use `-s
ERROR_ON_UNDEFINED_SYMBOLS=0`
error: undefined symbol: AES_set_encrypt_key
error: undefined symbol: BIO_ctrl
error: undefined symbol: BIO_free
error: undefined symbol: BIO_new
error: undefined symbol: BIO_s_mem
error: undefined symbol: BN_bn2bin
error: undefined symbol: BN_free
error: undefined symbol: BN_is_bit_set
error: undefined symbol: BN_new
error: undefined symbol: BN_num_bits
error: undefined symbol: BN_set_word
error: undefined symbol: CRYPTO_free
error: undefined symbol: CRYPTO_malloc
error: undefined symbol: DSA_free
error: undefined symbol: DSA_generate_key
error: undefined symbol: DSA_generate_parameters_ex
error: undefined symbol: DSA_new
error: undefined symbol: EC_KEY_free
error: undefined symbol: EC_KEY_generate_key
error: undefined symbol: EC_KEY_get0_group
error: undefined symbol: EC_KEY_get0_public_key
error: undefined symbol: EC_KEY_new_by_curve_name
error: undefined symbol: EC_KEY_set_asn1_flag
error: undefined symbol: EC_POINT_point2oct



Any advice would be a great help!
Thank you.


On Thu, May 9, 2019 at 10:43 PM Dr Paul Dale  wrote:

> Configure with the _no-asm_ option.
>
> It will be a **lot** slower.
>
>
> Pauli
> --
> Dr Paul Dale | Cryptographer | Network Security & Encryption
> Phone +61 7 3031 7217
> Oracle Australia
>
>
>
> On 10 May 2019, at 3:33 pm, Sunghyun Park  wrote:
>
> Nice to meet you all :)
>
> I faced a problem while building assembly code in OpenSSL (e.g.,
> crypto/x86_64cpuid.s) with Emscripten.
> Since Emscripten does not support compilation for assembly code (As far as
> I know), I'm wondering if there is any version of OpenSSL that does not
> require compiling assembly code.
> Or, if there is anyone who experienced the similar problem, please share
> your experience.
>
> Thank you!
>
> --
> Best, Sung
>
>
>

-- 
Best, Sung

RE: OpenSSL 1.1.1b tests fail on Solaris - solution

[John Unsworth]

This seems to be caused by the ongoing saga documented in issues 6912 and 8102. 
These functions were declared as weak in 1.1.1b.

safestack.h
#  pragma weak OPENSSL_sk_num
#  pragma weak OPENSSL_sk_value
#  pragma weak OPENSSL_sk_new
#  pragma weak OPENSSL_sk_new_null
...

lhash.h
#  pragma weak OPENSSL_LH_new
#  pragma weak OPENSSL_LH_free
#  pragma weak OPENSSL_LH_insert
#  pragma weak OPENSSL_LH_delete
...

Removing these lines allows all the tests to work. I am building static 
libraries (no-shared) which is presumably why it works for some people out of 
the box if they are using shared libraries.

Please advise as to the way forward. I note that one other user (see 8102) has 
reported this too:

>>>
rammishr commented on Mar 26
Hi,
Sorry if this should have been posted separately.

When i build openssl1.1.1b on solaris , it is successful. But while verifying 
the version " openssl version" it fails with below error.
ld.so.1: openssl: fatal: relocation error: file 
/vobs_tools/prgs/src/openssl/solaris64/bin/openssl: symbol OPENSSL_sk_new_null: 
referenced symbol not found
Killed

The same machine works fine for openssl1.1.1.
So, in 1.1.1b I can observe that OPENSSL_sk_new_null has been defined as below 
in safestack.h.
pragma weak OPENSSL_sk_new_null
Can this be related ? Am I missing anything while Configure ?
<<<

Regards,
John.

-Original Message-
From: openssl-users  On Behalf Of John 
Unsworth
Sent: 09 May 2019 10:13
To: openssl-users@openssl.org
Subject: RE: OpenSSL 1.1.1b tests fail on Solaris

CAUTION: This email originated from outside of Synchronoss.


This looks like the problem:

ld.so.1: sanitytest: fatal: relocation error: file ../../test/sanitytest: 
symbol OPENSSL_sk_new_null: referenced symbol not found 
../../util/shlib_wrap.sh ../../test/sanitytest => 137 not ok 1 - running 
sanitytest

#   Failed test 'running sanitytest'
#   at 
/home/metabld/OpenSSL/openssl-1.1.1b/test/../util/perl/OpenSSL/Test/Simple.pm 
line 77.
# Looks like you failed 1 test of 1.
Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests

This results in the same error:
sol-mds-build-01 $ cd apps
sol-mds-build-01 $ ./openssl version
ld.so.1: openssl: fatal: relocation error: file openssl: symbol 
OPENSSL_sk_new_null: referenced symbol not found

I have built static libraries.

John

-Original Message-
From: openssl-users  On Behalf Of Matt 
Caswell
Sent: 09 May 2019 09:38
To: openssl-users@openssl.org
Subject: Re: OpenSSL 1.1.1b tests fail on Solaris

CAUTION: This email originated from outside of Synchronoss.


What is the output from:

$ make V=1 TESTS=test_sanity test

Matt

On 08/05/2019 19:22, John Unsworth wrote:
> I have build OpenSSL 1.1.1b 64 bit on Solaris SunOS 5.10 
> Generic_Virtual sun4v sparc SUNW,T5140.
>
>
>
> ./Configure -lrt solaris64-sparcv9-cc no-shared -m64 -xcode=pic32 
> -xldscope=hidden
>
>
>
> It builds fine but all the tests fail, with or without no-asm. Can 
> anyone help please? Here is the start of the test run:
>
>
>
> $ make test
>
> make depend && make _tests
>
> ( cd test; \
>
>   mkdir -p test-runs; \
>
>   SRCTOP=../. \
>
>   BLDTOP=../. \
>
>   RESULT_D=test-runs \
>
>  PERL="/opt/perl-5.26.1/bin/perl" \
>
>   EXE_EXT= \
>
>   OPENSSL_ENGINES=`cd .././engines 2>/dev/null && pwd` \
>
>   OPENSSL_DEBUG_MEMORY=on \
>
> /opt/perl-5.26.1/bin/perl .././test/run_tests.pl  )
>
> ../test/recipes/01-test_abort.t  ok
>
> ../test/recipes/01-test_sanity.t ... Dubious, test 
> returned 1 (wstat 256, 0x100)
>
> Failed 1/1 subtests
>
> Regards,
>
> John.
>

Build the FIPS Object Module issue on Ubuntu 18.04

[Sreekanth Reddy]

Hi,
I am trying to build the FIPS object module using the fips library
openssl-fips-2.0.16 on Ubuntu 18.04 for x86 arch.
I am following the steps in
https://wiki.openssl.org/index.php/FIPS_Library_and_Android

below steps are followed to Build the FIPS Object Module:

$ . ./setenv-android.sh
$ cd openssl-fips-2.0.5/
$ ./config
$ make

First 3 steps are successful, able to set the environment paths, run the
config but make fails with error "cryptlib.h:62:20: fatal error: stdlib.h:
No such file or directory" - "#inlcude 

I do have the libraries under /usr/inlcude but the make is not looking at
the right path.

below is the error message received:
In file included from cryptlib.c:117:0:
cryptlib.h:62:20: fatal error: stdlib.h: No such file or directory
 #include 
^
compilation terminated.
: recipe for target 'cryptlib.o' failed
make[1]: *** [cryptlib.o] Error 1

Also, attaching the complete error log. Could you please suggest what is
the issue and where to change the path reference (in config).

Thanks,
Sreekanth


Build FIPS Object Module_x86_Ubuntu_18.04
Description: Binary data

Re: Reg slowness seen in openssl 1.1.1

[Jan Just Keijser]

Hi,

On 10/05/19 02:29, ramakrushna mishra wrote:

Hi,

Could anyone please help me wth it.

Following are sslc speed results for SHA1.

[...]
OpenSSL 1.1.0e  16 Feb 2017
type             16 bytes     64 bytes    256 bytes   1024 bytes  
 8192 bytes  16384 bytes
sha1             90515.06k   301813.93k   551106.78k  701554.35k  
 729893.50k   832176.13k


[...]


OpenSSL 1.1.1  11 Sep 2018type             16 bytes  64 bytes    256 
bytes   1024 bytes   8192 bytes  16384 bytes
sha1             90645.60k   245118.29k   455184.27k  684999.34k  
 752292.25k   822811.06k




I have a lot of experience running 'openssl speed' tests and these 
numbers would not worry me too much - if you were to run each of these 
tests 10 times **on an empty system** , then average the results , then 
most likely you will find that the results are within 5% of each other.


IOW, OpenSSL 1.1.1 is just as fast/slow on this purely artificial speed 
test as 1.1.0


HTH,

JJK

Re: Reg slowness seen in openssl 1.1.1

[Jan Just Keijser]

On 10/05/19 03:16, ramakrushna mishra wrote:

Hi ,

The results on a AIX machine looks more bad If I am interpreting them 
correctly.


openssl 1.1.0e :
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes  1024 bytes   8192 
bytes  16384 bytes
sha1             65019.16k   151552.49k   266107.41k  337113.93k  
 360792.93k   364102.89k



openssl 1.1.1 :
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes  1024 bytes   8192 
bytes  16384 bytes
sha1             10641.28k    21433.09k    38464.85k 48496.92k    
49381.38k    51755.48k



the numbers for openssl 1.1.1 seem wrong - I've ran a similar test on a 
POWER8 and POWER9 box and the results for a "out of the box compiled" 
openssl 1.1.0 vs openssl 1.1.1 are much closer.
The only difference I did see was the (obsolete) sha1 test on Power8:  
openssl 1.1.1 seems to be a bit slower than 1.1.0, but not by a factor 
of 7 as shown above.


Also, on both POWER8 and POWER9, there does not appear to be a major 
difference in blowfish or aes-256 speed.


As for your code: I would check that you are not using a no-asm build 
for openssl 1.1.1.


HTH,

JJK

openssl failed to connect to MS Exchange Server (Office365) on RHEL 7.x

[Chandu Gangireddy]

Dear OpenSSL Users,

At my corporate environment, I'm experience a challenge to use openssl
s_client utility. I really appreciate if someone can help me narrow down
the issue.

Here the details -

Platform: RHEL 7.x
*Openssl version:*
OpenSSL 1.0.2k-fips  26 Jan 2017
built on: reproducible build, date unspecified
platform: linux-x86_64
options:  bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int)
blowfish(idx)
compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DZLIB
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64
-DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches
 -m64 -mtune=generic -Wa,--noexecstack -DPURIFY -DOPENSSL_IA32_SSE2
-DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m
-DRC4_ASM -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
OPENSSLDIR: "/etc/pki/tls"
engines:  rdrand dynamic

Command tried to tes the connectivity between my Linux client server to
remote office 365 exchange server using POP3 port -

$ openssl s_client -crlf -connect outlook.office365.com:995
...
...
subject=/C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=outlook.com
issuer=/C=US/O=DigiCert Inc/CN=DigiCert Cloud Services CA-1
---
No client certificate CA names sent
Peer signing digest: SHA256
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3952 bytes and written 415 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol  : TLSv1.2
Cipher: ECDHE-RSA-AES256-GCM-SHA384
Session-ID:
072FFFDC6177DE9CAB2B59EA06E486A25AD8A2882A9B82F16678BAD74E79
Session-ID-ctx:
Master-Key:
DD7B59F38867FEAB9656B519FBCD743158E528C63FF9A96CE758120424159F26967F9F6FE57A9B5E7CAD806798322278
Key-Arg   : None
Krb5 Principal: None
PSK identity: None
PSK identity hint: None
Start Time: 1557500061
Timeout   : 300 (sec)
Verify return code: 0 (ok)
---
+OK The Microsoft Exchange POP3 service is ready.
[QgBOADYAUABSADEANABDAEEAMAAwADQAMgAuAG4AYQBtAHAAcgBkADEANAAuAHAAcgBvAGQALgBvAHUAdABsAG8AbwBrAC4AYwBvAG0A]
*USER netco...@cox.com *
*+OK*
*PASS *
*-ERR Logon failure: unknown user name or bad password.*
*quit*
*+OK Microsoft Exchange Server POP3 server signing off.*
*read:errno=0*

Operating System:
Red Hat Enterprise Linux Server release 7.2 (Maipo)

When I did the same from a different server, it worked as expected.
Following are the two difference which I noticed between a working server
and non-working server.

*Working server details:*
1. Red Hat Enterprise Linux Server release 6.9 (Santiago)
2. openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
built on: Mon Jan 30 07:47:24 EST 2017
platform: linux-x86_64
options:  bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int)
blowfish(idx)
compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -DTERMIO -Wall -O2 -g
-pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -Wa,--noexecstack -DPURIFY
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM
-DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
OPENSSLDIR: "/etc/pki/tls"
engines:  dynamic

Please let me know if you need any further details from my end.

Thanks, in advance.
Chandu

Re: Issue in linking Openssl1.1.1b to application

[Kenneth Goldman]

> From: vin 
> To: openssl-users@openssl.org
> Date: 05/10/2019 12:44 AM
> Subject: Re: Issue in linking Openssl1.1.1b to application
> Sent by: "openssl-users" 
>
> Hi Ken
>
> I am almost struck in registering the built dll to windows 7 32 bit
machine.
>
> Can you provide me the details on which all openssl1.1.1b output lib
files
> and output dll files that needs to be linked to any application while
> building in visual studio??

With mingw, I specify this to the linker

c:/program files/openssl/lib/mingw/libcrypto-1_1.a

In Visual Studio,

Linker - Input - Additional Dependencies: libcrypto32mdd.lib
Linker - General - Additional Library Directory: c:\program files\openssl
\lib\vc

However, it sounded like you were linking correctly, but Windows could
not find the dll at runtime.  That points to a PATH issue.

>
> Or any steps needs to be added while building openssl1.1.1b,I am
following
> the steps below
> Windows 32-bit
>1. perl Configure VC-WIN32
>2. nmake
>3. nmake test
>4. nmake install

I don't build myself.  I use Shining Light:

http://slproweb.com/products/Win32OpenSSL.html

Re: Reg slowness seen in openssl 1.1.1

[ramakrushna mishra]

Hi ,

I have installed openssl from scratch and there I am not observing any
degradation.  But I built it with in my project, there I observe the
degradation.  The Configure file remains same , but still in my project I
can see a difference that "dynamic-engine" is present in enabled feature
list.

But In Configure file its present in disabled list. So, Could anyone
suggest how this can be disabled ?
And I want to build the openssl outside my project) with dynamic-engine
enabled. What Configure argument shall i pass or make changes in Configure
file to achive that ?

Thanks and Regards,
Ram Krushna

On Fri, May 10, 2019 at 6:46 AM ramakrushna mishra 
wrote:

> Hi ,
>
> The results on a AIX machine looks more bad If I am interpreting them
> correctly.
>
> openssl 1.1.0e :
> The 'numbers' are in 1000s of bytes per second processed.
> type 16 bytes 64 bytes256 bytes   1024 bytes   8192
> bytes  16384 bytes
> sha1 65019.16k   151552.49k   266107.41k   337113.93k
>  360792.93k   364102.89k
>
>
> openssl 1.1.1 :
> The 'numbers' are in 1000s of bytes per second processed.
> type 16 bytes 64 bytes256 bytes   1024 bytes   8192
> bytes  16384 bytes
> sha1 10641.28k21433.09k38464.85k48496.92k
> 49381.38k51755.48k
>
> could any one please confirm if my interpretation is correct ?
> I doubt any issue with openssl 1.1.1 version with such wider user base.
> How to debug this further ?
>
> Thanks and Regards,
> Ram Krushna
>
>
> On Fri, May 10, 2019 at 5:59 AM ramakrushna mishra <
> rama.krush...@gmail.com> wrote:
>
>> Hi,
>>
>> Could anyone please help me wth it.
>>
>> Following are sslc speed results for SHA1.
>>
>> sslc speed sha1
>> Doing sha1 for 3s on 16 size blocks: 16858430 sha1's in 2.98s
>> Doing sha1 for 3s on 64 size blocks: 14147528 sha1's in 3.00s
>> Doing sha1 for 3s on 256 size blocks: 6436755 sha1's in 2.99s
>> Doing sha1 for 3s on 1024 size blocks: 2055335 sha1's in 3.00s
>> Doing sha1 for 3s on 8192 size blocks: 266404 sha1's in 2.99s
>> Doing sha1 for 3s on 16384 size blocks: 152376 sha1's in 3.00s
>> OpenSSL 1.1.0e  16 Feb 2017
>> built on: reproducible build, date unspecified
>> options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int)
>> blowfish(ptr)
>> compiler: gcc -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_THREADS
>> -DOPENSSL_NO_STATIC_ENGINE -DOPENSSL_PIC -DOPENSSL_IA32_SSE2
>> -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m
>> -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM
>> -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DPADLOCK_ASM
>> -DOPENSSLDIR="\"/vobs_prgs/tools/linuxx86_64/openssl/install\""
>> -DENGINESDIR="\"/vobs_prgs/tools/linuxx86_64/openssl/install/lib/engines-1.1\""
>> The 'numbers' are in 1000s of bytes per second processed.
>> type 16 bytes 64 bytes256 bytes   1024 bytes   8192
>> bytes  16384 bytes
>> sha1 90515.06k   301813.93k   551106.78k   701554.35k
>>  729893.50k   832176.13k
>>
>>
>>
>> sslc speed sha1
>> Doing sha1 for 3s on 16 size blocks: 16939397 sha1's in 2.99s
>> Doing sha1 for 3s on 64 size blocks: 11489920 sha1's in 3.00s
>> Doing sha1 for 3s on 256 size blocks: 5316410 sha1's in 2.99s
>> Doing sha1 for 3s on 1024 size blocks: 2006834 sha1's in 3.00s
>> Doing sha1 for 3s on 8192 size blocks: 273661 sha1's in 2.98s
>> Doing sha1 for 3s on 16384 size blocks: 150159 sha1's in 2.99s
>> OpenSSL 1.1.1  11 Sep 2018
>> built on: Tue Feb 12 18:18:22 2019 UTC
>> options:bn(64,64) rc4(16x,int) des(int) aes(partial) idea(int)
>> blowfish(ptr)
>> compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -fPIC
>> -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ
>> -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5
>> -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM
>> -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM
>> -DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DNDEBUG -fPIC
>> The 'numbers' are in 1000s of bytes per second processed.
>> type 16 bytes 64 bytes256 bytes   1024 bytes   8192
>> bytes  16384 bytes
>> sha1 90645.60k   245118.29k   455184.27k   684999.34k
>>  752292.25k   822811.06k
>>
>> Does not this  means 1.1.1 process lesser number of bytes per second
>> compared to 1.1.0e ?
>>
>> Thanks and Regards,
>> Ram Krushna
>>
>> On Thu, May 9, 2019 at 11:46 PM Salz, Rich  wrote:
>>
>>> *>  *Could you please look into the program and let me know if
>>> anything  I am doing wrong ?
>>>
>>> > Or else What could be the issue ?
>>>
>>>
>>>
>>> Sorry, no not me.  Maybe someone else on the list has ideas.
>>>
>>

Re: Building OpenSSL with Emscripten

[Sunghyun Park]

I realized I made a mistake when I tried that option before.
Now it works great. Thank you! :)

On Thu, May 9, 2019 at 10:43 PM Dr Paul Dale  wrote:

> Configure with the _no-asm_ option.
>
> It will be a **lot** slower.
>
>
> Pauli
> --
> Dr Paul Dale | Cryptographer | Network Security & Encryption
> Phone +61 7 3031 7217
> Oracle Australia
>
>
>
> On 10 May 2019, at 3:33 pm, Sunghyun Park  wrote:
>
> Nice to meet you all :)
>
> I faced a problem while building assembly code in OpenSSL (e.g.,
> crypto/x86_64cpuid.s) with Emscripten.
> Since Emscripten does not support compilation for assembly code (As far as
> I know), I'm wondering if there is any version of OpenSSL that does not
> require compiling assembly code.
> Or, if there is anyone who experienced the similar problem, please share
> your experience.
>
> Thank you!
>
> --
> Best, Sung
>
>
>

-- 
Best, Sung

Re: Building OpenSSL with Emscripten

[Jakob Bohm via openssl-users]

By the way, has anyone worked on a feature or patch to use browser
provided crypto functions (WebCrypto etc.) when compiled to
pseudo-javascript via EmScripten or WebAssembly?

On 10/05/2019 07:43, Dr Paul Dale wrote:

Configure with the _no-asm_ option.

It will be a **lot** slower.


On 10 May 2019, at 3:33 pm, Sunghyun Park > wrote:


Nice to meet you all :)

I faced a problem while building assembly code in OpenSSL (e.g., 
crypto/x86_64cpuid.s) with Emscripten.
Since Emscripten does not support compilation for assembly code (As 
far as I know), I'm wondering if there is any version of OpenSSL that 
does not require compiling assembly code.
Or, if there is anyone who experienced the similar problem, please 
share your experience.





Enjoy

Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, 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