All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Prestwood <james.prestwood@linux.intel.com>
To: ell@lists.01.org
Subject: Re: [PATCH v2 2/2] ecc: document where ECC groups came from
Date: Wed, 16 Jan 2019 09:05:43 -0800	[thread overview]
Message-ID: <10ce642d0b7bd24194ab61a5b2dd0a2c7389625d.camel@linux.intel.com> (raw)
In-Reply-To: <3e0d3d35-f8ae-b02d-be35-b3ee6f778372@gmail.com>

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

On Wed, 2019-01-16 at 10:38 -0600, Denis Kenzior wrote:
> Hi James,
> 
> On 01/15/2019 04:43 PM, James Prestwood wrote:
> > For future reference a comment was added pointing to RFC 5114
> > ---
> >   ell/ecc.c | 6 ++++++
> >   1 file changed, 6 insertions(+)
> > 
> 
> Applied.
> 
> But the original question was actually about where the group
> identifiers 
> came from?  E.g. group 19, 20 etc.

Ah, ok. Well they are in that RFC, just a different section. Actually
after looking into this I am somewhat confused. I originally based my
ECC groups off hostapd, and e.g. EAP-PWD which says group 19 (256-bit)
must be supported. Sort of after the fact I saw that these group
numbers were defined in RFC 5114. Now after revisiting this I see there
are actually two tables, one for IKE and one for TLS, and the group
numbers do not match. Maybe once ECC is used in TLS we will need a
mapping?

Thanks,
James
> 
> Regards,
> -Denis
> 


  reply	other threads:[~2019-01-16 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 22:43 [PATCH v2 1/2] ecc: add l_ecc_curve_get_supported_groups James Prestwood
2019-01-15 22:43 ` [PATCH v2 2/2] ecc: document where ECC groups came from James Prestwood
2019-01-16 16:38   ` Denis Kenzior
2019-01-16 17:05     ` James Prestwood [this message]
2019-01-16 16:35 ` [PATCH v2 1/2] ecc: add l_ecc_curve_get_supported_groups Denis Kenzior
  -- strict thread matches above, loose matches on Subject: below --
2019-01-15 22:23 James Prestwood
2019-01-15 22:23 ` [PATCH v2 2/2] ecc: document where ECC groups came from James Prestwood

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=10ce642d0b7bd24194ab61a5b2dd0a2c7389625d.camel@linux.intel.com \
    --to=james.prestwood@linux.intel.com \
    --cc=ell@lists.01.org \
    /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.