Hi,
With my openssl based FTPS client (non-blocking bio) targeting TLS1.3, I
see that immediately after a successful data channel handshake (with
session reuse), a dummy change_cipher_spec record and a non-application
data record are sent as part of the directory listing data. Same holds true
for
On Thu, Nov 24, 2022 at 09:48:42AM +0530, Satyam Mehrotra wrote:
> I have encrypted pkcs#8 key file . Is there any openssl command buy which I
> can view the algorithm used to encrypt it ( i mean aes or des3 )
Removing blank lines and passing to "asn1parse" you get:
$ openssl asn1parse -in /
Hi ,
I have encrypted pkcs#8 key file . Is there any openssl command buy which I
can view the algorithm used to encrypt it ( i mean aes or des3 )
Appreciate for anyone's quick help :)
-BEGIN ENCRYPTED PRIVATE KEY-
MIIFFjBIBgkqhkiG9w0BBQ0wOzAjBgkqhkiG9w0BBQwwFgQQVL5oYwC9daKlhnjT
qnRoAwI
Am 11.11.2022 um 17:44 schrieb Matt Caswell:
On 11/11/2022 12:41, f...@plutonium24.de wrote:
My apologies. I tested the code you supplied and of course it also fails with 1.1.1. The
code was changed without my knowledge when updating to 3.0 and the version that was
working used the depre
On 2022-11-15 21:36, Phillip Susi wrote:
Jakob Bohm via openssl-users writes:
Performance wise, using a newer compiler that implements int64_t etc. via
frequent library calls, while technically correct, is going to run
unnecessarily slow compared to having algorithms that actually use the
opt
