All of lore.kernel.org
 help / color / mirror / Atom feed
From: vinay paduru <vinay.paduru@live.com>
To: "dm-crypt@saout.de" <dm-crypt@saout.de>,
	"Milan Broz" <gmazyland@gmail.com>
Subject: Re: [dm-crypt] LUKS2 AES-GCM-random erroring with key size issue.
Date: Thu, 12 Mar 2020 13:04:59 +0530	[thread overview]
Message-ID: <BYAPR05MB5749A60CEAE48E2BB472B638E3FD0@BYAPR05MB5749.namprd05.prod.outlook.com> (raw)
In-Reply-To: <7c22d7ea-9728-00b6-b923-ca5c9ecab08d@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

Thank you for the detailed explanation Milan and apologies for late response. We were trying it on OEL-7 distro. Any chance of supporting OEL-7 distro in future as OEL-6 is almost EOL ?

Vinay
On 2 Mar 2020, 12:53 PM +0530, Milan Broz <gmazyland@gmail.com>, wrote:
> On 02/03/2020 06:30, vinay paduru wrote:
> > Yes, I have the module installed and enabled.
> >
> > filename:       /lib/modules/4.1.12-61.1.19.el7uek.x86_64/kernel/crypto/gcm.ko
>
> Hi,
>
> as suggested, also check --debug output and syslog.
>
> I cannot provide you support for commercial kernel with possibly (not) backported patches,
> please contact your vendor if it is not working properly.
> (Couldn't resist, but it is Oracle unbreakable kernel (uek) so it have to work, obviously!)
>
> More seriously, it is quite possible that you are missing more things here (dm-integrity)
> that is required for authenticated encryption etc.
>
> We do not support dm-integrity in RHEL7 at all, do not expect it to work in distro clones
> even with updated kernel.
>
> Milan

[-- Attachment #2: Type: text/html, Size: 1744 bytes --]

      reply	other threads:[~2020-03-12  7:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7d63ae4f-0b97-4b98-ac1b-5f26880950ac@Spark>
2020-02-27  5:37 ` [dm-crypt] LUKS2 AES-GCM-random erroring with key size issue vinay paduru
2020-02-28 10:22   ` Michael Kjörling
2020-02-28 11:21   ` Milan Broz
2020-03-02  5:30     ` vinay paduru
2020-03-02  7:23       ` Milan Broz
2020-03-12  7:34         ` vinay paduru [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BYAPR05MB5749A60CEAE48E2BB472B638E3FD0@BYAPR05MB5749.namprd05.prod.outlook.com \
    --to=vinay.paduru@live.com \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.