>; git status
>On branch master
>Your branch is up-to-date with 'origin/master'.
>Untracked files:
> (use "git add ..." to include in what will be committed)
>
>include/openssl/opensslv.h
>
>nothing added to commit but untracked files present (u
On 18/10/2019 11:49, Nagalakshmi V J wrote:
> Now the issue is SSL_session structure is also having accessor APIs
> which I am not aware of. So I need to get the APIs for accessing the
> master_key_length,etc.. given in the above code. Those are not listed
> in the openssl link referred.
On thi
Hi Matt,
Sorry I missed your reply as all the conversations are jumbled in that mail.
Please find the sample code snippet. This is a small part. Like the below
sample, we are using SSL and SSL_SESSION structures in many places.
struct PRF_GENERATOR
{
unsigned char master_secret[48];
un
Thank you very much for the reply!
Yes, I have also the additional information about on which of two
solutions I should take.
I'll check the guides you linked below.
Luca Di Mauro
Nicola Tuveri ha scritto:
Hi,
with traditional EC from the x coordinate alone you can't really do that,
beca
Hi,
with traditional EC from the x coordinate alone you can't really do that,
because there are always 2 possible solutions for y (in R the curve is
symmetrical on the x axis).
The standards define a "compressed point" format in which you can send the
coordinate x and an additional bit to select
Hello all,
I don't know if it is the correct mailing list to ask this, so I'm
sorry if it is the wrong palce.
I'm using openssl v1.1, and I'm trying to compute both the X and Y
coordinates of an elliptic curve point starting from a single
coordinate (X or Y).
How can i perform that in
Thank you for your answer.
I know, my version is old and I need to update (and I will). It's installed on
IBM AIX server.
I was not precise enough in my question, I need to have base64url natively
supported for a certification purpose.
I'm using openssl in some bash scripts, I can easily repla
P.S: My answer to your original question applies to 1.0.1 as well:
https://github.com/openssl/openssl/blob/OpenSSL_1_0_1-stable/doc/crypto/EVP_EncodeInit.pod
Von: openssl-users Im Auftrag von Dr.
Matthias St. Pierre
Gesendet: Freitag, 18. Oktober 2019 09:10
An: Benjamin ENTE ; openssl-users@ope
Just noticed your OpenSSL version: it is _very_ old and not supported anymore.
its successor, OpenSSL 1.0.2, will be EOL by the end of this year.
The current stable LTS version is OpenSSL 1.1.1.
Matthias
Von: openssl-users Im Auftrag von Benjamin
ENTE
Gesendet: Freitag, 18. Oktober 2019 08:51
A
OpenSSL is using regular base64 encoding, see for example
https://www.openssl.org/docs/man1.1.1/man3/EVP_EncodeInit.html
But if you need base64url encoding, no problem: a simple string replace will
help.
https://brockallen.com/2014/10/17/base64url-encoding/
Regards,
Matthias
Von: openssl-users
10 matches
Mail list logo
