Thanks for the explanation Mr. Henson.
I do not wish to take up too much of your time, but as I am still trying
to understand OpenSSL, I would be grateful if you can add a few words on
how you cope with this in TLS, and point me to the corresponding source
code.
Thanks again,
Michel.
Le 12
On Fri, Oct 12, 2012, Michel wrote:
> I am guessing that 'special handling' is linked to the 'no
> additional authentication data' issue discussed in :
> http://incog-izick.blogspot.fr/2011_08_01_archive.html
>
It's to do with the fact that additional parameters are required with GCM and
how the
I am guessing that 'special handling' is linked to the 'no additional
authentication data' issue discussed in :
http://incog-izick.blogspot.fr/2011_08_01_archive.html
Le 11/10/2012 22:33, Erik Tkal a écrit :
I think Steve posted a while back that those ciphers require special handling
and do n
I think Steve posted a while back that those ciphers require special handling
and do not work with the enc command yet.
Erik Tkal
Juniper OAC/UAC/Pulse Development
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of e
See:
http://marc.info/?l=openssl-users&m=134867395821086&w=2
On 11 October 2012 17:19, e...@mit.edu wrote:
> Hello,
> I am trying to encrypt and decrypt a string using command-line openssl
> (1.0.1c) with the id-aes256-GCM algorithm, but every time it fails
>
> echo -n "bla" | openssl enc -e -i
