The SRP support will not be removed in 3.x releases. At the earliest it
could be removed in 4.0 release. Whether there will be a replacement
for the deprecated SRP APIs at that time we cannot currently say.
So unless you absolutely require not using deprecated APIs you can
still move to 3.x releas
I'm also interested in the answer to these questions regarding SRP in
OpenSSL v3.
Our project still uses OpenSSL v1.1.1 with plans to move to v3 next year.
However we use SRP extensively and will not be able to move to v3 if SRP
support is soon to be no longer available.
Norm Green
GemTalk S
> From: רונן לוי
> Sent: Monday, 17 October, 2022 12:03
Send messages to the list, not directly to me.
> And, in which header file am I expected to find the Definition for LONG?
That's a question about the Windows SDK, not OpenSSL.
It's in WinNT.h, per Microsoft's documentation (which is read
I am trying to get information on versions and usage of the Secure Remote
Password Protocol (SRP) APIs in OpenSSLv3.
1. Are SRPv3, v6, and/or v6a supported?
1. I found the following information in the OpenSSL documents on the
following C API for SRP: SRP_create_verifier(), SRP_user_pwd
> From: רונן לוי
> Sent: Monday, 17 October, 2022 11:12
> see attached file for cygwin details.
I'm afraid I have no comment on that. I merely mentioned that for some OpenSSL
releases, using a POSIXy perl implementation such as Cygwin's to configure
OpenSSL for a Windows build did not work.
> From: רונן לוי
> Sent: Monday, 17 October, 2022 11:16
Please send messages to the list, not to me directly.
> And for the question with regard to the Windows style, are you referring to
> CRLF as
> opposed to LF from linux?
No, to Windows-style file paths, with drive letters and backslashes
Hi Michael,
see attached file for cygwin details.
The openssl is cloned from:
git clone https://github.com/openssl/openssl.git
perl Configure
*Configuring OpenSSL version 3.2.0-dev for target Cygwin-x86_64*
Using os-specific seed configuration
Created configdata.pm
Running configdata.pm
Created
On 17/10/2022 13:10, Ashok Kumar Sarode via openssl-users wrote:
NOTE: I have re-named file openssl\*configuration.h.in* to
openssl\*configuration.h*
Likewise i re-named err.h, ssl.h, opensslv.h, crypto.h
Don't do that. That is almost certainly the cause of these errors. The
".h.in" file
Sehr geehrte Damen und Herren
vom 8. Oktober bis und mit dem 18. Oktober bin ich im Urlaub.
eMails werden nur sehr spärlich gelesen und nur in dringenden Fällen beantwortet
freundliche Grüsse
Silvan Scherrer
Hello OpenSSL users,
I need help on following errors which I am getting from myWindows machine
building on Visual Studio 2019,
Version 16.11.17.
Build started...1>-- Build started: Project: executeHelloWorld,
Configuration: Debug Win32
--1>VerifyJWTSignUsingRSA.cpp1>C:\Users\myDir\Window
On 17/10/2022 09:34, Fernando Elena Benavente wrote:
Hi guys, we are having problems with the implementation of the signature
and verification of messages with ECDSA, because the demo of ECDSA in
github us does not allow us to determine the type of ECDSA curve,
I assume you are looking at
On Mon, Oct 17, 2022 at 10:28:45AM +0200, Tim Meusel wrote:
> Hi!
> I maintain a Ruby script that does PKCS#7 signing and afterwards some
> enryption with AES-128-CFB. A trimmed down version:
>
> certpath = '/tmp/cert.pem'
> keypath = '/tmp/key/pem'
> data = 'teststring'
> key = OpenSSL::PKey::RS
Hi guys, we are having problems with the implementation of the signature and
verification of messages with ECDSA, because the demo of ECDSA in github us
does not allow us to determine the type of ECDSA curve, In addition, we have
seen that we have problems when it comes to having strings and EV
Hi!
I maintain a Ruby script that does PKCS#7 signing and afterwards some
enryption with AES-128-CFB. A trimmed down version:
certpath = '/tmp/cert.pem'
keypath = '/tmp/key/pem'
data = 'teststring'
key = OpenSSL::PKey::RSA.new(File.read(keypath), '1234')
cert = OpenSSL::X509::Certificate.new(F
14 matches
Mail list logo