> Is there is a reason why openssl has restriction of auth before
> encrypt
> order ? I dont believe there is an algo restriction, was
> wondering why
> openssl has this.
>
>
> It *is* inherent in the algorithm. The authentication tag for the
> AAD
This is the way GCM works. Perhaps you need something else, like CBC mode.
Closing this ticket.
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
See inline. Look for Praveen.
On Mon, Apr 25, 2016 at 7:20 PM, Brian Smith wrote:
> Praveen Kariyanahalli via RT wrote:
>
>> Is there is a reason why openssl has restriction of auth before encrypt
>> order ? I dont believe there is an algo restriction, was wondering why
>> openssl has this.
>>
Praveen Kariyanahalli via RT wrote:
> Is there is a reason why openssl has restriction of auth before encrypt
> order ? I dont believe there is an algo restriction, was wondering why
> openssl has this.
>
It *is* inherent in the algorithm. The authentication tag for the AAD is
computed first, th
Why do you want GCM then?
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4521
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Is there is a reason why openssl has restriction of auth before encrypt
order ? I dont believe there is an algo restriction, was wondering why
openssl has this.
*int CRYPTO_gcm128_aad(GCM128_CONTEXT *ctx, const unsigned char *aad,*
* size_t len)*
*{*
*[snip]*
*if (ctx->l
