From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Encrypting with larger packet size
Date: Sat, 26 Jan 2013 00:25:17 +0100 [thread overview]
Message-ID: <20130125232517.GA24516@tansi.org> (raw)
In-Reply-To: <CAO6to9VFg0We+QnnpzcchdUn9YZ4Vcymz=1czi4dAnNm+n3M1A@mail.gmail.com>
On Thu, Jan 24, 2013 at 11:44:34AM -0800, Dinesh Garg wrote:
> >>Please can you be more specific?
> I was offering my help in term of code change and testing and upstreaming
> the patch.
You need to establish a clear and valuable use-case first. I still
do not see it.
> > Which HW accelerator you are using, where is the source of it and
> > when it will be part of upstream kernel? (if not already).
> I would not like to disclose the HW accelerator details. However, IMO,
> anyone who changes GPL license based code, has to opensource the changes.
Well, maybe you have noticed that FOSS projects tend to
be not very friendly to closed hardware and even less so to
secret hardware. I guess you have to fight through this on
your own. If you actually have links to the developers of
said hardware, you may tell them that by having long key
change times, they messed up.
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
----
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-01-25 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 4:18 [dm-crypt] Encrypting with larger packet size Dinesh Garg
2013-01-22 5:42 ` Arno Wagner
2013-01-22 6:04 ` Dinesh Garg
2013-01-22 7:24 ` Milan Broz
2013-01-22 8:00 ` Dinesh Garg
2013-01-22 15:54 ` Milan Broz
2013-01-24 19:44 ` Dinesh Garg
2013-01-25 23:25 ` Arno Wagner [this message]
2013-01-28 12:00 ` [dm-crypt] Encrypting with larger packet size (+some experimental patch) Milan Broz
2013-03-05 11:53 ` Michael Stapelberg
2013-03-10 15:05 ` Milan Broz
2013-03-25 19:22 ` Michael Stapelberg
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=20130125232517.GA24516@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