DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] sha384, sha512
Date: Fri, 2 Dec 2016 10:05:29 +0100	[thread overview]
Message-ID: <20161202090529.GA15218@tansi.org> (raw)
In-Reply-To: <2574248a86c44eb5bd544406b8b2e105@useimail1301.ATL.CW.LOCAL>

Hi Steve,

that is a Kernel limitation, i.e. you recompile the kernel 
with these available, if possible.

Regards,
Arno

On Thu, Dec 01, 2016 at 19:53:01 CET, Houtchen, Steven wrote:
>    dm-crypt,
> 
> 
>    I am using cryptsetup  with CentOS7, and It seems that hash values of
>    sha384 and sha512 are not
> 
>    available. Do I need to recompile the LUKs code, or the CentOS kernel
>    to use those?
> 
> 
> 
>    Steve Houtchen
>    Senior Software Engineer
>    Curtiss-Wright
>    2600 Paramount Place, Suite 200, Fairborn, OH 45324
>    T: 937.610.5420 | F: 937.252.1465
>    [1]shoutchen@curtisswright.com | [2]www.curtisswrightds.com
> 
> 
>    _______________________________________________________________________
>    This e-mail and any files transmitted with it are proprietary and
>    intended solely for the use of the individual or entity to whom they
>    are addressed. If you have reason to believe that you have received
>    this e-mail in error, please notify the sender and destroy this e-mail
>    and any attached files. Please note that any views or opinions
>    presented in this e-mail are solely those of the author and do not
>    necessarily represent those of the Curtiss-Wright Corporation or any of
>    its subsidiaries. Documents attached hereto may contain technology
>    subject to government export regulations. Recipient is solely
>    responsible for ensuring that any re-export, transfer or disclosure of
>    this information is in accordance with applicable government export
>    regulations. The recipient should check this e-mail and any attachments
>    for the presence of viruses. Curtiss-Wright Corporation and its
>    subsidiaries accept no liability for any damage caused by any virus
>    transmitted by this e-mail.
> 
> References
> 
>    1. mailto:shoutchen@curtisswright.com
>    2. http://www.curtisswrightds.com/

> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt


-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

      reply	other threads:[~2016-12-02  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01 18:53 [dm-crypt] sha384, sha512 Houtchen, Steven
2016-12-02  9:05 ` Arno Wagner [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=20161202090529.GA15218@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /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