public inbox for dm-crypt@saout.de
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] bits vs bytes
Date: Tue, 31 Mar 2020 08:43:39 +0200	[thread overview]
Message-ID: <20200331064338.GA4895@tansi.org> (raw)
In-Reply-To: <672718044.1618732.1585632916735@mail.yahoo.com>

On Tue, Mar 31, 2020 at 07:35:16 CEST, JT Morée wrote:
> 
> On Monday, March 30, 2020, 6:43:11 PM MST, Arno Wagner <arno@wagner.name> wrote: 
> > Not in a cryptographic context. You could also want to etch them
> 
> is that because the 512 bits is not the size of the key but instead a
> measurement of one component that goes into generating the key?

Well, block-ciphers have gotten to respect CPU operations recently, 
so they are starting to use bytes internally ti increase efficiency. 
But look at classic DES, and every but pretty much gets treated by 
itself or bits get grpuped in ways that have nothing to do with byte
boundaries. Or look at RSA and whether you have a 4096 bit, 4095 bit 
or 4097 bit modulus makes no difference. Of course you usually
go for multiples of 8, but that is just to accomodate a specific
implementation (computers with 8 bit bytes), not anything that is
part of the algebra of the cipher.

Just accept it, it makes sense form a mathematical viewpoint.
Otherwise you would need to multiply by 8 in a lot of places.
And you could also use nibbles (4 bit) words (16 bits), 
long words (32 bits) or quadwords (64 bits) as "units". The 
byte is not really specuial.

Regards,
Arno

-- 
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:[~2020-03-31  6:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <566872408.1293730.1585598590645.ref@mail.yahoo.com>
2020-03-30 20:03 ` [dm-crypt] bits vs bytes JT Morée
2020-03-30 20:25   ` Michael Kjörling
2020-03-30 21:00     ` Arno Wagner
2020-03-30 21:18       ` JT Morée
     [not found]         ` <20200331014306.GA2009@tansi.org>
2020-03-31  5:35           ` JT Morée
2020-03-31  6:43             ` Arno Wagner [this message]
2020-03-31  6:55               ` Michael Kjörling
2020-03-31  9:32                 ` Arno Wagner
2020-03-31  7:06         ` Michael Kjörling

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=20200331064338.GA4895@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