date:20180802

Re: [openssl-users] Need help with creating a server certificate

2018-08-02 Thread murugesh pitchaiah

Hi,

The command you used is the correct one to generate a cert from CSR.
Still certificate not generated means there may be some config issue.

You did not see any errors after the following line ?
using configuration from
> path/to/config/folder/openssl.cnf".

Also check if the file/path permissions are ok.

Thanks,
Murugesh P.


On 8/2/18, Neo meister  wrote:
> I started the process of creating a chain of certificates from the root CA
> down to a leaf certificate using openssl running on a debian vm. I
> successfully created and verified the root cert, intermediate cert and
> chain file. The issue I am having now is that when I go to create a leaf
> cert to be used by the server it will not work for me. After generating the
> key and and the CSR i use this command " *openssl* ca -config
> path/to/config/folder/openssl.cnf -extensions server_cert -days 375 -notext
> -md sha256 -in path/to/CSR/folder/www.testcert.com.csr.pem -out
> path/to/output/cert/folder/www.testcert.com.cert.pem".
>
> After running this command I get the output "using configuration from
> path/to/config/folder/openssl.cnf".
>
> When I check the folder i told openssl to place the newly created cert in
> it is not there. I have tried changing to a different output folder for the
> new cert but I get the same result. Any idea what is going on?
>
>
> The guide I have been using up until this point is at:
> https://jamielinux.com/docs/openssl-certificate-authority/create-the-root-pair.html
>
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] openssl cms -decrypt failing due to malloc(3) failure

2018-08-02 Thread Viktor Dukhovni

On Thu, Aug 02, 2018 at 01:53:42PM +0200, Christian Böhme wrote:

> > In any case, the OpenSSL apps are a convenience and a set of samples.
> 
> My original impression was that those tools represented some kind of reference
> implementation of the libraries.  Clearly, I was wrong ;-)

Well, OpenSSL's cms(1) is not a reference implementation of the CMS
standard.

It is an implementation of CMS via the OpenSSL APIs, and its source
code is a useful resource in understanding how to use those APIs.

IIRC the requirement to extract the complete CMS message into memory
is not just an artefact of the CLI design.  Rather, I seem to recall
that presently the CMS library needs the whole message in memory
in order to process it.  If so, a streaming implementation would
need to extend the CMS implementation in libcrypto to support that
mode of operation.

-- 
Viktor.
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] openssl-1.1.0-stable-SNAP-20180802 issue

2018-08-02 Thread Matt Caswell

The fix is already pending:
https://github.com/openssl/openssl/pull/6843

Just waiting on it being pushed.

Matt


On 02/08/18 13:28, Blumenthal, Uri - 0553 - MITLL wrote:
> Same problem on Linux. 
> 
> Regards,
> Uri
> 
> Sent from my iPhone
> 
>> On Aug 2, 2018, at 07:47, The Doctor  wrote:
>>
>> While compiling today's openssl 1.1.0 snap on FreeBSD 11.2 
>>
>> I got
>>
>> /usr/bin/cc  -I. -Icrypto/include -Iinclude -DZLIB -DZLIB_SHARED -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 -DPOLY1305_ASM 
>> -DOPENSSLDIR="\"/usr/local/ssl\"" 
>> -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -DL_ENDIAN -Wall -O3 -pthread 
>> -D_THREAD_SAFE -D_REENTRANT  -rdynamic -fPIC -MMD -MF 
>> crypto/asn1/tasn_utl.d.tmp -MT crypto/asn1/tasn_utl.o -c -o 
>> crypto/asn1/tasn_utl.o crypto/asn1/tasn_utl.c
>> cc: warning: argument unused during compilation: '-rdynamic' 
>> [-Wunused-command-line-argument]
>> crypto/asn1/tasn_utl.c:60:5: error: use of undeclared identifier
>>  'CRYPTO_REF_COUNT'
>>  CRYPTO_REF_COUNT *lck;
>>  ^
>> crypto/asn1/tasn_utl.c:60:23: error: use of undeclared identifier 'lck'
>>  CRYPTO_REF_COUNT *lck;
>>^
>> crypto/asn1/tasn_utl.c:70:5: error: use of undeclared identifier 'lck'; did 
>> you
>>  mean 'lock'?
>>  lck = offset2ptr(*pval, aux->ref_offset);
>>  ^~~
>>  lock
>> crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
>>CRYPTO_RWLOCK **lock;
>>  ^
>> crypto/asn1/tasn_utl.c:75:10: error: use of undeclared identifier 'lck'; did 
>> you
>>mean 'lock'?
>>*lck = ret = 1;
>> ^~~
>> lock
>> crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
>>   CRYPTO_RWLOCK **lock;
>>  ^
>> crypto/asn1/tasn_utl.c:75:14: warning: incompatible integer to pointer
>>conversion assigning to 'CRYPTO_RWLOCK *' (aka 'void *') from 'int'
>>  [-Wint-conversion]
>>  *lck = ret = 1;
>>   ^ ~~~
>> crypto/asn1/tasn_utl.c:83:14: warning: implicit declaration of function
>>   'CRYPTO_UP_REF' is invalid in C99 [-Wimplicit-function-declaration]
>> if (!CRYPTO_UP_REF(lck, , *lock))
>>  ^
>> crypto/asn1/tasn_utl.c:83:28: error: use of undeclared identifier 'lck'; did 
>> you
>> mean 'lock'?
>>if (!CRYPTO_UP_REF(lck, , *lock))
>>   ^~~
>>   lock
>> crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
>>CRYPTO_RWLOCK **lock;
>>  ^
>> crypto/asn1/tasn_utl.c:87:14: warning: implicit declaration of function
>>  'CRYPTO_DOWN_REF' is invalid in C99 [-Wimplicit-function-declaration]
>>if (!CRYPTO_DOWN_REF(lck, , *lock))
>> ^
>> crypto/asn1/tasn_utl.c:87:30: error: use of undeclared identifier 'lck'; did 
>> you
>>   mean 'lock'?
>>   if (!CRYPTO_DOWN_REF(lck, , *lock))
>>^~~
>>  lock
>> crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
>> CRYPTO_RWLOCK **lock;
>>   ^
>> 3 warnings and 6 errors generated.
>> *** Error code 1
>>
>> Stop.
>> make[1]: stopped in /usr/source/openssl-1.1.0-stable-SNAP-20180802
>> *** Error code 1
>>
>> Stop.
>> make: stopped in /usr/source/openssl-1.1.0-stable-SNAP-20180802
>>
>>
>> Please fix.
>>
>> -- 
>> Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
>> doctor@@nl2k.ab.ca
>> Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
>> rising!
>> https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on 
>> Atheism
>> A problem is a chance for you to do your best.  -Duke Ellington
>> -- 
>> openssl-users mailing list
>> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
>>
>>
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] openssl-1.1.0-stable-SNAP-20180802 issue

2018-08-02 Thread Blumenthal, Uri - 0553 - MITLL

Same problem on Linux. 

Regards,
Uri

Sent from my iPhone

> On Aug 2, 2018, at 07:47, The Doctor  wrote:
> 
> While compiling today's openssl 1.1.0 snap on FreeBSD 11.2 
> 
> I got
> 
> /usr/bin/cc  -I. -Icrypto/include -Iinclude -DZLIB -DZLIB_SHARED -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 -DPOLY1305_ASM 
> -DOPENSSLDIR="\"/usr/local/ssl\"" 
> -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -DL_ENDIAN -Wall -O3 -pthread 
> -D_THREAD_SAFE -D_REENTRANT  -rdynamic -fPIC -MMD -MF 
> crypto/asn1/tasn_utl.d.tmp -MT crypto/asn1/tasn_utl.o -c -o 
> crypto/asn1/tasn_utl.o crypto/asn1/tasn_utl.c
> cc: warning: argument unused during compilation: '-rdynamic' 
> [-Wunused-command-line-argument]
> crypto/asn1/tasn_utl.c:60:5: error: use of undeclared identifier
>  'CRYPTO_REF_COUNT'
>  CRYPTO_REF_COUNT *lck;
>  ^
> crypto/asn1/tasn_utl.c:60:23: error: use of undeclared identifier 'lck'
>  CRYPTO_REF_COUNT *lck;
>^
> crypto/asn1/tasn_utl.c:70:5: error: use of undeclared identifier 'lck'; did 
> you
>  mean 'lock'?
>  lck = offset2ptr(*pval, aux->ref_offset);
>  ^~~
>  lock
> crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
>CRYPTO_RWLOCK **lock;
>  ^
> crypto/asn1/tasn_utl.c:75:10: error: use of undeclared identifier 'lck'; did 
> you
>mean 'lock'?
>*lck = ret = 1;
> ^~~
> lock
> crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
>   CRYPTO_RWLOCK **lock;
>  ^
> crypto/asn1/tasn_utl.c:75:14: warning: incompatible integer to pointer
>conversion assigning to 'CRYPTO_RWLOCK *' (aka 'void *') from 'int'
>  [-Wint-conversion]
>  *lck = ret = 1;
>   ^ ~~~
> crypto/asn1/tasn_utl.c:83:14: warning: implicit declaration of function
>   'CRYPTO_UP_REF' is invalid in C99 [-Wimplicit-function-declaration]
> if (!CRYPTO_UP_REF(lck, , *lock))
>  ^
> crypto/asn1/tasn_utl.c:83:28: error: use of undeclared identifier 'lck'; did 
> you
> mean 'lock'?
>if (!CRYPTO_UP_REF(lck, , *lock))
>   ^~~
>   lock
> crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
>CRYPTO_RWLOCK **lock;
>  ^
> crypto/asn1/tasn_utl.c:87:14: warning: implicit declaration of function
>  'CRYPTO_DOWN_REF' is invalid in C99 [-Wimplicit-function-declaration]
>if (!CRYPTO_DOWN_REF(lck, , *lock))
> ^
> crypto/asn1/tasn_utl.c:87:30: error: use of undeclared identifier 'lck'; did 
> you
>   mean 'lock'?
>   if (!CRYPTO_DOWN_REF(lck, , *lock))
>^~~
>  lock
> crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
> CRYPTO_RWLOCK **lock;
>   ^
> 3 warnings and 6 errors generated.
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/source/openssl-1.1.0-stable-SNAP-20180802
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/source/openssl-1.1.0-stable-SNAP-20180802
> 
> 
> Please fix.
> 
> -- 
> Member - Liberal International This is doctor@@nl2k.ab.ca Ici 
> doctor@@nl2k.ab.ca
> Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist 
> rising!
> https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
> A problem is a chance for you to do your best.  -Duke Ellington
> -- 
> openssl-users mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


smime.p7s
Description: S/MIME cryptographic signature
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] openssl cms -decrypt failing due to malloc(3) failure

2018-08-02 Thread Christian Böhme

Hello,

On 01.08.2018 14:49, Michael Wojcik wrote:
>> On 30.07.2018 20:12, Michael Wojcik wrote:
>>
>>> FWIW, SUS Issue 5 defines RLIMIT_AS as applying to both malloc and mmap, 
>>> but RLIMIT_DATA as
>>> applying only to malloc. (That is, mmap'd pages do not count against the 
>>> data limit.)
>>
>> mmap() , by defninition, populates the process' virtual address space, and 
>> if  that
>> is limited in size, artificially or not, then the call is going to fail, 
>> eventually.
> 
> That's irrelevant to the statement you quoted, which was about the SUS 
> process-limit mechanism
> (setrusage et al.), not the process address space.

I may have skipped a few steps and made too broad a statement, so here are the 
details
and corrections.

malloc(3)  is a pure C library call, whereas  mmap(2)  is a proper system call 
on those,
POSIX-conforming systems I have seen, anyway.

To a userland process, there is nothing more fundamental than the system call 
interface.
If it requires resources to do its work, it needs to go through this interface 
and ask
"the system" first.  The kernel as an implementation of "the system", where 
process-level
resource control actually happens, does not care about what userland code such 
as the
C library does unless that actually decides to call the system.

Except for SAS OSes, processes generally live in their own virtual address 
space, and
that is where "the process's data segment" is located that  RLIMIT_DATA  refers 
to.
s/brk(2)  are system calls to manage the end of the process's data segment AKA 
program
break, while  mmap() , as much broader a concept, does not have this limited 
view on the
process's address space and is therefore also more powerful.

Now, with Linux since 4.7 for example,  RLIMIT_DATA  also controls  mmap() .  
What's more,
glibc  malloc()  on Linux is actually implemented in terms of  mmap()  these 
days, although
usage of  s/brk()  isn't phased out completely (apparently, the runtime linker 
still likes
those).  Since  s/brk()  and  mmap()  are the only means available to a Linux 
userland
process to manage those parts of its address space that it is designed to 
manage,
controlling a process's  RLIMIT_DATA  value ultimately controls all of its 
ability
to manage its address space, data segment or otherwise.

>> The pure streaming approach may be appropriate for file descriptors that are 
>> not
>> seekable like sockets, pipes, tty ends etcpp., whereas with egular files, 
>> random
>> access schemes using either  pread(v)(2)  or  lseek(2)  in combination with
>> read(v)(2)  can be employed.
> 
> Or regular files could also be processed sequentially. What's the advantage 
> of making
> seekable sources a special case?

Making sure that the message under investigation is consistent w.r.t. the 
standards
according to which it was supposedly constructed, without having to consume 
resources
that aren't strictly necessary to make such a decision.  In other words, it's 
about
system performance /and/ making sure to get the logic right at the same time.

There is simply no need to slurp in the whole file just to get at its end (if so
required), when mechanisms for random access are readily available.  Please 
remember
our messages can get fairly large.  System performance and tight integration are
equally important to us as the security aspects.

> In any case, the OpenSSL apps are a convenience and a set of samples.

My original impression was that those tools represented some kind of reference
implementation of the libraries.  Clearly, I was wrong ;-)

Thanks,
Christian

-- 
*Christian Böhme*

Developer System Integration

CLOUD

*CLOUD & HEAT Technologies GmbH*
Königsbrücker Str. 96 (Halle 15) | 01099 Dresden
Tel: +49 351 479 3670 - 100
Fax: +49 351 479 3670 - 110
E-Mail: christian.boe...@cloudandheat.com 

Web: https://www.cloudandheat.com 

Handelsregister: Amtsgericht Dresden
Registernummer: HRB 30549
USt.-Ident.-Nr.: DE281093504
Geschäftsführer: Nicolas Röhrs

signature.asc
Description: OpenPGP digital signature
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

[openssl-users] openssl-1.1.0-stable-SNAP-20180802 issue

2018-08-02 Thread The Doctor

While compiling today's openssl 1.1.0 snap on FreeBSD 11.2 

I got

/usr/bin/cc  -I. -Icrypto/include -Iinclude -DZLIB -DZLIB_SHARED -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 
-DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" 
-DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -DL_ENDIAN -Wall -O3 -pthread 
-D_THREAD_SAFE -D_REENTRANT  -rdynamic -fPIC -MMD -MF 
crypto/asn1/tasn_utl.d.tmp -MT crypto/asn1/tasn_utl.o -c -o 
crypto/asn1/tasn_utl.o crypto/asn1/tasn_utl.c
cc: warning: argument unused during compilation: '-rdynamic' 
[-Wunused-command-line-argument]
crypto/asn1/tasn_utl.c:60:5: error: use of undeclared identifier
  'CRYPTO_REF_COUNT'
  CRYPTO_REF_COUNT *lck;
  ^
crypto/asn1/tasn_utl.c:60:23: error: use of undeclared identifier 'lck'
  CRYPTO_REF_COUNT *lck;
^
crypto/asn1/tasn_utl.c:70:5: error: use of undeclared identifier 'lck'; did you
  mean 'lock'?
  lck = offset2ptr(*pval, aux->ref_offset);
  ^~~
  lock
crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
CRYPTO_RWLOCK **lock;
  ^
crypto/asn1/tasn_utl.c:75:10: error: use of undeclared identifier 'lck'; did you
mean 'lock'?
*lck = ret = 1;
 ^~~
 lock
crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
   CRYPTO_RWLOCK **lock;
  ^
crypto/asn1/tasn_utl.c:75:14: warning: incompatible integer to pointer
conversion assigning to 'CRYPTO_RWLOCK *' (aka 'void *') from 'int'
  [-Wint-conversion]
  *lck = ret = 1;
   ^ ~~~
crypto/asn1/tasn_utl.c:83:14: warning: implicit declaration of function
   'CRYPTO_UP_REF' is invalid in C99 [-Wimplicit-function-declaration]
 if (!CRYPTO_UP_REF(lck, , *lock))
  ^
crypto/asn1/tasn_utl.c:83:28: error: use of undeclared identifier 'lck'; did you
mean 'lock'?
if (!CRYPTO_UP_REF(lck, , *lock))
   ^~~
   lock
crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
CRYPTO_RWLOCK **lock;
  ^
crypto/asn1/tasn_utl.c:87:14: warning: implicit declaration of function
  'CRYPTO_DOWN_REF' is invalid in C99 [-Wimplicit-function-declaration]
if (!CRYPTO_DOWN_REF(lck, , *lock))
 ^
crypto/asn1/tasn_utl.c:87:30: error: use of undeclared identifier 'lck'; did you
   mean 'lock'?
   if (!CRYPTO_DOWN_REF(lck, , *lock))
^~~
  lock
crypto/asn1/tasn_utl.c:61:21: note: 'lock' declared here
 CRYPTO_RWLOCK **lock;
 ^
3 warnings and 6 errors generated.
 *** Error code 1

Stop.
make[1]: stopped in /usr/source/openssl-1.1.0-stable-SNAP-20180802
*** Error code 1

 Stop.
 make: stopped in /usr/source/openssl-1.1.0-stable-SNAP-20180802


Please fix.

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
A problem is a chance for you to do your best.  -Duke Ellington
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

[openssl-users] Need help with creating a server certificate

2018-08-02 Thread Neo meister

I started the process of creating a chain of certificates from the root CA
down to a leaf certificate using openssl running on a debian vm. I
successfully created and verified the root cert, intermediate cert and
chain file. The issue I am having now is that when I go to create a leaf
cert to be used by the server it will not work for me. After generating the
key and and the CSR i use this command " *openssl* ca -config
path/to/config/folder/openssl.cnf -extensions server_cert -days 375 -notext
-md sha256 -in path/to/CSR/folder/www.testcert.com.csr.pem -out
path/to/output/cert/folder/www.testcert.com.cert.pem".

After running this command I get the output "using configuration from
path/to/config/folder/openssl.cnf".

When I check the folder i told openssl to place the newly created cert in
it is not there. I have tried changing to a different output folder for the
new cert but I get the same result. Any idea what is going on?


The guide I have been using up until this point is at:
https://jamielinux.com/docs/openssl-certificate-authority/create-the-root-pair.html
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Help : TLS 1.3 Server is not listening on the default port

2018-08-02 Thread Chakrapani Reddy

Below command helped Thanks.

*[root@vm bin]# ./openssl s_server -cert server.crt -key server1.key -4
-accept 44330 -www -tls1_3*


On Wed, Aug 1, 2018 at 3:43 PM, Chakrapani Reddy 
wrote:

> Hello,
>
> Wanted to try to capture the TLS1.3 message flow using openssl-1.1.1-pre7
> and used the below command to run the server.
> [root@vm bin]# pwd
> /opt/build/openssl-1.1.1-pre7/bin
>
> *[root@vm bin]# ./openssl s_server -cert server.crt -key server1.key*
>
> But it is throwing the below error :
>
> Using default temp DH parameters
>
> *47306412798048:error:02004061:system
> library:socket:unknown:crypto/bio/b_sock2.c:49:47306412798048:error:2008C076:BIO
> routines:BIO_socket:unable to create socket:crypto/bio/b_sock2.c:50:*
>0 items in the session cache
>0 client connects (SSL_connect())
>0 client renegotiates (SSL_connect())
>0 client connects that finished
>0 server accepts (SSL_accept())
>0 server renegotiates (SSL_accept())
>0 server accepts that finished
>0 session cache hits
>0 session cache misses
>0 session cache timeouts
>0 callback cache hits
>0 cache full overflows (128 allowed)
>
>
>  ldd ./openssl
> linux-vdso.so.1 =>  (0x7fff6c9fd000)
> libdl.so.2 => /lib64/libdl.so.2 (0x003fc220)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x003fc2a0)
> libc.so.6 => /lib64/libc.so.6 (0x003fc1e0)
> /lib64/ld-linux-x86-64.so.2 (0x003fc160)
>
> Shall we know how to make it working?
>
> Best Regards,
> Chakrapani
>
>
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Need help with creating a server certificate

Re: [openssl-users] openssl cms -decrypt failing due to malloc(3) failure

Re: [openssl-users] openssl-1.1.0-stable-SNAP-20180802 issue

Re: [openssl-users] openssl-1.1.0-stable-SNAP-20180802 issue

Re: [openssl-users] openssl cms -decrypt failing due to malloc(3) failure

[openssl-users] openssl-1.1.0-stable-SNAP-20180802 issue

[openssl-users] Need help with creating a server certificate

Re: [openssl-users] Help : TLS 1.3 Server is not listening on the default port

8 matches

Site Navigation

Mail list logo

Footer information