linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zain <zain.wang@rock-chips.com>
To: Sandy Harris <sandyinchina@gmail.com>,
	linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH v2 1/4] Crypto: Crypto driver support aes/des/des3 for rk3288
Date: Mon, 9 Nov 2015 08:53:46 +0800	[thread overview]
Message-ID: <563FEE9A.2020505@rock-chips.com> (raw)
In-Reply-To: <CACXcFmmFeK6kO7Q9sWf0SE5gmw0ZzX126=TUaA6YPGApVsopCg@mail.gmail.com>



On 2015年11月07日 12:40, Sandy Harris wrote:
> On Thu, Nov 5, 2015 at 8:17 PM, Zain Wang <zain.wang@rock-chips.com> wrote:
>> The names registered are:
>>     ecb(aes) cbc(aes) ecb(des) cbc(des) ecb(des3_ede) cbc(des3_ede)
>> You can alloc tags above in your case.
> Why on Earth are you allowing DES? Here's a reference from around the
> turn of the century on why the FreeS/WAN project refused to implement
> it then:
> http://www.freeswan.org/freeswan_trees/freeswan-1.97/doc/politics.html#desnotsecure
>
> In 1998 a $200,000-odd purpose-built machine using FPGAs could break
> DES in a few days. Morre's Law applies; my guess would be that today
> you could break it in hours for well under $10,000 using either GPUs
> or Intel's Xeon Phi.
>
> Even if you have to implement DES because you need it as a component
> for 3DES and some standards still require 3DES, single DES should not
> be exposed in the user interface.
>
>
>
Thanks for your comment.
I built it because DES has been built in many other patch about crypto
like atmel, marvell, samsung... though I don't known how it can be used.
Do I remove DES?

  reply	other threads:[~2015-11-09  0:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  1:17 [PATCH v2 0/4] Crypto: add crypto accelerator support for rk3288 Zain Wang
2015-11-06  1:17 ` [PATCH v2 1/4] Crypto: Crypto driver support aes/des/des3 " Zain Wang
2015-11-06  1:54   ` Caesar Wang
2015-11-06  9:51     ` Zain
2015-11-07  4:40   ` Sandy Harris
2015-11-09  0:53     ` Zain [this message]
     [not found]   ` <1446772644-2352-2-git-send-email-zain.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-11-07 23:19     ` Heiko Stuebner
2015-11-09  3:46       ` Zain
     [not found] ` <1446772644-2352-1-git-send-email-zain.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-11-06  1:17   ` [PATCH v2 2/4] clk: rockchip: set an id for crypto clk Zain Wang
2015-11-06  1:17   ` [PATCH v2 3/4] ARM: dts: rockchip: Add Crypto drivers for rk3288 Zain Wang
2015-11-06  2:00     ` Caesar Wang
2015-11-06  9:50       ` Zain
     [not found]     ` <1446772644-2352-4-git-send-email-zain.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-11-06 10:12       ` Heiko Stuebner
2015-11-06 10:27         ` Zain
2015-11-06  1:17 ` [PATCH v2 4/4] crypto: rockchip/crypto - add DT bindings documentation Zain Wang
2015-11-06  2:27   ` Rob Herring
2015-11-06  9:00   ` Heiko Stuebner
2015-11-06  9:36     ` Zain
2015-11-06  1:36 ` [PATCH v2 0/4] Crypto: add crypto accelerator support for rk3288 Caesar Wang
     [not found]   ` <563C0430.9000607-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-11-06  9:53     ` Zain

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=563FEE9A.2020505@rock-chips.com \
    --to=zain.wang@rock-chips.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=sandyinchina@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).