On 24/02/2020 13:04, Phani 2004 wrote:
> Hi Team,
>
> "aes_cbc_hmac_sha1" implementation is currently supported on x86
> platforms only.
> With which RFC is this compliant with?
> This cipher is only used when the "encrypt then mac" option is disabled.
> Is this understanding correct. I am
On Mon, Feb 24, 2020 at 12:09 PM Michael Wojcik <
michael.woj...@microfocus.com> wrote:
> > From: openssl-users [mailto:openssl-users-boun...@openssl.org] On
> Behalf Of Michael Leone
> > Sent: Monday, February 24, 2020 09:37
>
> > SO I was an idiot, and signed a certificate, but specified an
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Michael Leone
> Sent: Monday, February 24, 2020 09:37
> SO I was an idiot, and signed a certificate, but specified an invalid
> location. i.e.,
> I used a "/" instead of a "/" in the location.
I assume that was
SO I was an idiot, and signed a certificate, but specified an invalid
location. i.e., I used a "/" instead of a "/" in the location.
$ sudo openssl ca -in requests/.req -out
certs\-2020-02-24.
And so I can't find that cert file anywhere (obviously). So I'd like to
revoke it, so that I can
Hi Team,
"aes_cbc_hmac_sha1" implementation is currently supported on x86 platforms
only.
With which RFC is this compliant with?
This cipher is only used when the "encrypt then mac" option is disabled. Is
this understanding correct. I am using openssl s_server and s_client is i
use the below
