[openssl-users] Problems on authentication during TLS handshake

2019-01-07 Thread Jin Xie
Hello everyone, I’m new at OpenSSL programming and encountered a problem while build TLS connection. I’m working on a crypto chip ATECC508A. So the client private key is stored in the chip and no way to get it out. However during standard TLS handshake, I need to provide client private key by “

Re: [openssl-users] Openssl asynchronous operation in real network

2019-01-07 Thread Ananthu Unnikrishnan
Can anyone please help on this? If u need any additional information please let me know. On Mon, Jan 7, 2019 at 6:25 PM Ananthu Unnikrishnan wrote: > Hi all, > > Adding more details to the previous mail. We have edited the OpenSSL code > for implementing the polling for changed fd's as in OpenSS

Re: [openssl-users] possible C bugs in ecp_nistp521

2019-01-07 Thread Patrick Steuer
Dear Bo-Yin Yang, I looked into your felem_square counterexample: There is an overflow in the result's least significant 128-bit limb such that the computed result is 2^128 smaller than the actual result. The general problem is the following.. The function's comment says: /*- * felem_square

Re: [openssl-users] RNG behavior by default

2019-01-07 Thread Steffen Nurpmeso
Steffen Nurpmeso wrote in <20190107183136.-ew61%stef...@sdaoden.eu>: ... | ... ||RAND_bytes() has always documented that it can fail. Most function ... |So, to me.., i do not see any possible error condition, since the |initial seeding has been testified with RAND_status(). | |This is dif

Re: [openssl-users] RNG behavior by default

2019-01-07 Thread Steffen Nurpmeso
Jakob Bohm via openssl-users wrote in <07f4dea3-1a62-0c8c-76a4-cbe56abc8\ 7...@wisemo.com>: |On 07/01/2019 22:31, Steffen Nurpmeso wrote: |> Good evening. |> |> Jakob Bohm via openssl-users wrote in <95bceb59-b299-015a-f9c2-e2487a699\ |> 8...@wisemo.com>: |>|Small corrections below: |>| ...

Re: [openssl-users] Session params output fails via cron

2019-01-07 Thread Jakob Bohm via openssl-users
On 07/01/2019 22:26, Jordan Brown wrote: [ Off topic for OpenSSL... ] On 1/7/2019 8:06 AM, Jakob Bohm via openssl-users wrote: A chroot with no other reason to open /dev/null should not contain that file name, even on unix-like platforms (least privilege chroot design). There's always a firs

Re: [openssl-users] RNG behavior by default

2019-01-07 Thread Jakob Bohm via openssl-users
On 07/01/2019 22:31, Steffen Nurpmeso wrote: > Good evening. > > Jakob Bohm via openssl-users wrote in <95bceb59-b299-015a-f9c2-e2487a699\ > 8...@wisemo.com>: > |Small corrections below: > | ... Note that I do not represent the project at all, I am just another user trying to help you. As s

Re: [openssl-users] Session params output fails via cron

2019-01-07 Thread Jordan Brown
[ Off topic for OpenSSL... ] On 1/7/2019 8:06 AM, Jakob Bohm via openssl-users wrote: > A chroot with no other reason to open /dev/null should not contain that > file name, even on unix-like platforms (least privilege chroot design). There's always a first reason :-) But also:  /dev/null is par

Re: [openssl-users] RNG behavior by default

2019-01-07 Thread Steffen Nurpmeso
Good evening. Jakob Bohm via openssl-users wrote in <95bceb59-b299-015a-f9c2-e2487a699\ 8...@wisemo.com>: |Small corrections below: | |On 07/01/2019 19:31, Steffen Nurpmeso wrote: | ||... |||RAND_load_file() and all this stuff. Just make sure the os entropy \ |||sources |||are available an

Re: [openssl-users] RNG behavior by default

2019-01-07 Thread Jakob Bohm via openssl-users
Small corrections below: On 07/01/2019 19:31, Steffen Nurpmeso wrote: ... |> That is really bad. Of course you had to do it like this, and you |> surely have looked around to see what servers and other software |> which use OpenSSL do with the PRNG afte

Re: [openssl-users] RNG behavior by default

2019-01-07 Thread Steffen Nurpmeso
A wonderful Monday in the beautiful Winter time i wish. I am sorry for the late reply again, i got a bug report for the mailer i maintain, and from a long time user. I hope it is ok that i compress the answers in one message, i am talking much too much... Kurt Roeckx wrote in <20190105221506.ga18

Re: [openssl-users] Compiling FIPS-cable OpenSSL on Windows Server 2012R2

2019-01-07 Thread Chris Fernando via openssl-users
> > On Jan 7, 2019, at 09:20, Chris Fernando via openssl-users > wrote: > > I perused the list archives for all of 2018 and did not see anything current > relating to this problem, so if this is a question that has been asked & > answered, please feel free to point me at the relevant location

Re: [openssl-users] Session params output fails via cron

2019-01-07 Thread Jakob Bohm via openssl-users
On 04/01/2019 22:04, Michael Wojcik wrote: From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Jordan Brown Sent: Friday, January 04, 2019 13:16 If you want to, what you want is something like: int fd; do { fd = open("/dev/null", O_RDWR);

[openssl-users] Compiling FIPS-cable OpenSSL on Windows Server 2012R2

2019-01-07 Thread Chris Fernando via openssl-users
I perused the list archives for all of 2018 and did not see anything current relating to this problem, so if this is a question that has been asked & answered, please feel free to point me at the relevant location to read about what I'm doing incorrectly. =) I'm not at all familiar with Windows

[openssl-users] possible C bugs in ecp_nistp521

2019-01-07 Thread Bo-Yin Yang
Dear all, we found some counter-examples (examples where wrong answers were returned) for field element computations in the C routines for P-521 (that is, modulo 2^521-1). The counterexamples, a C test file, a Makefile, and a short README are attached. The routines in question are: felem_s

Re: [openssl-users] Openssl asynchronous operation in real network

2019-01-07 Thread Ananthu Unnikrishnan
Hi all, Adding more details to the previous mail. We have edited the OpenSSL code for implementing the polling for changed fd's as in OpenSSL speed command. Attached the code snippet of the same along with this mail. Mentioned below some observations which found doubtful: 1) We have got prints in