Hi Team,
I am using openssl with dpdk. I try to run s_server and s_client
application. When we use dpdk how do we mention dpdk that we need to use
tls protocol. Is there any flag which indicates this. Because when we use
this cipher suite for tls 1.1 and 1.2 we need to skip the first 16 bytes
for
Hi Team,
I am trying to implement mac-then-encrypt for aes_cbc_hmac_sha1 combined
cipher. From the code i could understand that the first 16 bytes were being
used as explicit IV while decrypting and the hmac is done for 13 bye AAD
and 16 byte Fin record in finish message.
Which RFC/section
Hi Team,
Can anyone help me with the below queries.
Thanks in Advance.
Regards
Phani
On Fri, Feb 28, 2020 at 2:41 PM Phani 2004 wrote:
> OK. I understood that "AES-128-CBC-HMAC-SHA1"(aesni_cbc_hmac_sha1) always
> does mte.
> I am trying to implement engine implementati
and other for mte
without changing the openssl code.
One more query i have is, how do we pass the etm option to the openssl in
conf file.
Regards
Phani
On Fri, Feb 28, 2020 at 8:53 AM Matt Caswell wrote:
>
>
> On 27/02/2020 18:30, Phani 2004 wrote:
> > Thanks for the reply.
>
do I know if we have etm extension enabled or not.
Regards
Phani
On Wed, 26 Feb, 2020, 6:03 PM Hubert Kario, wrote:
> On Wednesday, 26 February 2020 08:59:01 CET, Phani 2004 wrote:
> > Thanks for the quick response Matt.
> >
> > My command was :
> > openssl s_client -
.
Regards
Phani
On Tue, Feb 25, 2020 at 10:31 AM Matt Caswell wrote:
>
>
> 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
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
may get support for this on ARM any sooner?
Any patches available on 1.1.1a?
Thanks in advance.
Regards
Phani
On Mon, Jan 13, 2020 at 5:53 PM Matt Caswell wrote:
>
>
> On 13/01/2020 06:20, Phani 2004 wrote:
> > Hi Team,
> >
> > I am trying to add support on an hardw
Hi Team,
I am trying to add support on an hardware engine for aes-cbc-hmac-sha1. I
have observed that currently aes-cbc-hmac-sha1 is supported only for x86
architecture.
"EVP_aes_128_cbc_hmac_sha1" api returns NULL for non-x86 platforms. The
openssl speed app calls the "EVP_get_cipherbyname" call
