dm-crypt.saout.de archive mirror
 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: Mon, 2 Mar 2020 05:30:16 +0000	[thread overview]
Message-ID: <BYAPR05MB5749AA56827852996E215E90E3E70@BYAPR05MB5749.namprd05.prod.outlook.com> (raw)
In-Reply-To: <7b4d93db-ed67-666f-176c-c545b95c13c0@gmail.com>

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

Hello Milan,

Yes, I have the module installed and enabled.


# lsmod | grep -i gcm

gcm                    24576  0


# modprobe gcm


# modinfo gcm

filename:       /lib/modules/4.1.12-61.1.19.el7uek.x86_64/kernel/crypto/gcm.ko

alias:          crypto-gcm

alias:          gcm

alias:          crypto-rfc4543

alias:          rfc4543

alias:          crypto-rfc4106

alias:          rfc4106

alias:          crypto-gcm_base

alias:          gcm_base

author:         Mikko Herranen <mh1@iki.fi>

description:    Galois/Counter Mode

license:        GPL

srcversion:     0805471CE9244CDA1D08732

depends:

intree:         Y

vermagic:       4.1.12-61.1.19.el7uek.x86_64 SMP mod_unload modversions

signer:         Oracle CA Server

sig_key:        99:0C:6B:AD:6E:20:40:AB:2F:AC:19:2B:13:86:80:73:E1:2A:95:FB

sig_hashalgo:   sha512


#cryptsetup luksFormat --type luks2 /dev/sdb2 --cipher aes-gcm-random --integrity aead


WARNING!

========

This will overwrite data on /dev/sdb2 irrevocably.


Are you sure? (Type 'yes' in capital letters): YES

Enter passphrase for /dev/sdb2:

Verify passphrase:

Cipher aes-gcm-random (key size 256 bits) is not available.

#

Vinay
On 28 Feb 2020, 4:51 PM +0530, Milan Broz <gmazyland@gmail.com>, wrote:
On 27/02/2020 06:37, vinay paduru wrote:
I am trying to encrypt a volume with *LUKS2* *AES-GCM-Random* cipher
and I am seeing an error saying “key size 256 bits” not available. I
tried changing the key size but same error repeats for whatever the
key size we give.

Do you have kernel with gcm crypto module enabled?

Milan

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

  reply	other threads:[~2020-03-02  5:30 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 [this message]
2020-03-02  7:23       ` Milan Broz
2020-03-12  7:34         ` vinay paduru

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=BYAPR05MB5749AA56827852996E215E90E3E70@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).