From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Cryptographic issues with SSD-technology and wide-block encryption modes
Date: Tue, 12 Feb 2013 13:41:20 +0100 [thread overview]
Message-ID: <20130212124119.GA5690@tansi.org> (raw)
In-Reply-To: <trinity-d29f0e50-1a40-49df-963b-2c308931d2a2-1360658821864@3capp-webde-bs34>
Hmm. Was the original publication on EME2 by them?
There is also a possible problem if the EME patent holder
thinks it covers EME2.
Arno
On Tue, Feb 12, 2013 at 09:47:01AM +0100, Stavros Kousidis wrote:
> This is really interesting! The webpage
>
> http://standards.ieee.org/about/sasb/patcom/pat1390.html
>
> links to a non-awareness statement of UC Davis concerning IEEE Standard No. 1619.2 (that standardizes EME2). By the way there is also a mail discussion of the corresponding IEEE working group: http://grouper.ieee.org/groups/1619/email-2/msg00005.html, that also links to this „Letter of Asssurance“.
>
> This document states the submitter's (UC Davis) position as:
>
> „After a Reasonable and Good Faith Inquiry, the Submitter is not aware of any Patent Claims that the Submitter may own, control, or have the ability to license that might be or become Essential Patent Claims.“
>
> As far as I understand, this „only“ certifies that UC Davis is not aware of any patent claims or pending patent applications after asking people/employees involved in this matter. This does not sound as a patent disclosure to me, which might rather be checking boxes 1. and c. in section D. of that Letter of Assurance. But on the other hand D.1.c. would be a really hard statement.
>
> I do not know the real-life meaning of this non-awareness statement. But my first feeling is that (IEEE-1619.2 standardized) EME2 is good to go from an intellectual property point of view. That's just my feeling though.
>
> Stavros
>
> > >> BTW anyone know what had happened with EME2 wide mode?
> > >> [snip long link]
> > >
> > > As far as I know there are intellectual-property issues:
> > >
> > > P. Rogaway, Block cipher mode of operation for constructing a
> > > wide-blocksize block cipher from a conventional block cipher, US Patent
> > > Application 20040131182 A1 _______________________________________________
> >
> > Hey, this caught my attention so I contacted Dr. Rogaway. Included below is
> > the email conversation (my apologies for the format, he replied at the top
> > so I followed suit):
> >
> > =======
> >
> > > Cool, thank you. It seems there was some misinformation in that thread
> > then,
> > > so would you mind if I quoted your response?
> >
> > Go right ahead.
> >
> > Best wishes,
> > Phil Rogaway
> >
> > > On Friday, February 08, 2013 09:34:14 AM you wrote:
> > >> Hi Alex,
> > >>
> > >> There is no Rogaway or UC patent related to EME2.
> > >> The University of California did do a patent application,
> > >> but abandoned it (that is, decided not to pursue a utility patent).
> > >> I had to look up some old correspondence to remind myself of this,
> > >> but it seems that we informed Matt Ball and Jim Hughes back in Nov 2007
> > >> that there'd be no patent, filling out some IEEE patent-disclosure
> > >> form saying this, too.
> > >>
> > >> Best wishes,
> > >> phil rogaway
> > >>
> > >> On Fri, 8 Feb 2013, Alex Elsayed wrote:
> > >>> Hi, I was wondering if you had any plans to (explicitly) offer similar
> > >>> terms regarding open-source software for EME2 as you recently have for
> > >>> OCB. There was a recent discussion on the dm-crypt mailing list with the
> > >>> title "Cryptographic issues with SSD-technology and wide-block
> > encryption
> > >>> modes." In the course of the discussion Milan Broz, the maintainer of
> > >>> dm-crypt, stated the following:
> > >>>
> > >>> "[It] would be nice to have some not patent encumbered wide mode (no
> > code
> > >>> changes needed, just someone have to invent it and add to crypto API)"
> > >>>
> > >>> I'm just someone who reads the list, but I thought I'd write to point
> > out
> > >>> that there's interest.
> > >>>
> > >>> (Frankly, I'm also very interested in OCB, but the other AE patents have
> > >>> an
> > >>> exceedingly unfortunate chilling effect independent of your license.)
> _______________________________________________
> 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
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2013-02-12 12:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1360494001.22742.dm-crypt@saout.de>
2013-02-12 8:47 ` [dm-crypt] Cryptographic issues with SSD-technology and wide-block encryption modes Stavros Kousidis
2013-02-12 12:41 ` Arno Wagner [this message]
[not found] <mailman.1.1360148402.2056.dm-crypt@saout.de>
2013-02-06 13:22 ` Stavros Kousidis
[not found] <mailman.6.1360140726.2399.dm-crypt@saout.de>
2013-02-06 10:06 ` Stavros Kousidis
2013-02-06 10:32 ` Arno Wagner
2013-02-06 12:52 ` Milan Broz
2013-02-06 13:06 ` Arno Wagner
2013-02-06 11:07 ` Matthias Schniedermeyer
2013-02-06 12:45 ` Arno Wagner
2013-02-06 13:18 ` Stavros Kousidis
2013-02-06 12:38 ` Milan Broz
2013-02-06 13:34 ` Stavros Kousidis
2013-02-06 14:08 ` Milan Broz
2013-02-06 13:59 ` Stavros Kousidis
2013-02-09 14:20 ` Alex Elsayed
2013-02-06 8:52 Stavros Kousidis
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=20130212124119.GA5690@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 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.