Article View: comp.arch.fpga
Article #17Re: AES(Rijindal) CTR with CBC MAC
From: Nicholas C. Weaver
Date: Fri, 24 Jan 2003 11:48
Date: Fri, 24 Jan 2003 11:48
34 lines
3245 bytes
3245 bytes
In article <b0qjos$s2dd0$2@ID-159027.news.dfncis.de>, geeko <jibin@ushustech.com> wrote: >Hi all > > Anbody familier with the implementation of AES(Rijindal) --- CTR with CBC >MAC in FPGA ( a C implementation can be found at >http://fp.gladman.plus.com/cryptography_technology/ccm/index.htm ) >I have certain quries about the implementation of a block cipher >How the implemetation can be tested ? (a sample test setup) Best way is to create a monte-carlo test rig (take the output, encrypt again, use output to rekey/reencrypt), compare with the software version. If you have any little problem, it will show up. >How the perfomance ie throughput,latency etc can be measured? CBC-MAC will be inherantly sequential, so for a single stream of execution, you will be limited by the latency required to encrypt each block before starting the next one. However, you probably should use XCBC MAC instead of CBC-MAC, its a slight tweak but an improvement http://csrc.nist.gov/CryptoToolkit/modes/proposedmodes/xcbc-mac/xcbc-mac-spec.pdf Also, if you are going to use a MAC which is sequential, why use CTR mode? CTR mode is nice for parallelism, but is easy to screw up, and screw up BADLY, in practice. Latency can be measred by taking your clock rate (from static timing) * number of cycles to encrypt a single block. Due to your MAC choice, your throughput will be limited by single block latency. -- Nicholas C. Weaver nweaver@cs.berkeley.edu
Technical Details
Message-ID:
<b0r960$21uu$1@agate.berkeley.edu>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-08!supernews.com!newsswitch.lcs.mit.edu!newsfeed.berkeley.edu!ucberkeley!agate.berkeley.edu!agate!not-for-mailReferences:
<b0qjos$s2dd0$2@ID-159027.news.dfncis.de>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1151b2,54699e004b474446 X-Google-Attributes: gid1151b2,public X-Google-Thread: f57fe,54699e004b474446 X-Google-Attributes: gidf57fe,public X-Google-Thread: f736a,54699e004b474446 X-Google-Attributes: gidf736a,public X-Google-Thread: 109e85,54699e004b474446 X-Google-Attributes: gid109e85,public X-Google-Thread: 104c88,54699e004b474446 X-Google-Attributes: gid104c88,public X-Google-Thread: 1089ad,54699e004b474446 X-Google-Attributes: gid1089ad,public X-Google-Thread: 112e4c,54699e004b474446 X-Google-Attributes: gid112e4c,public X-Google-Thread: fec08,54699e004b474446 X-Google-Attributes: gidfec08,public X-Google-ArrivalTime: 2003-01-24 03:48:16 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-xit-08!supernews.com!newsswitch.lcs.mit.edu!newsfeed.berkeley.edu!ucberkeley!agate.berkeley.edu!agate!not-for-mail From: nweaver@ribbit.CS.Berkeley.EDU (Nicholas C. Weaver) Newsgroups: comp.arch.fpga,comp.lang.verilog,comp.lang.vhdl,comp.lsi,comp.lsi.cad,fa.info-vlsi,fj.comp.lang.verilog,fj.comp.lang.vhdl Subject: Re: AES(Rijindal) CTR with CBC MAC Date: Fri, 24 Jan 2003 11:48:16 +0000 (UTC) Organization: University of California, Berkeley, EECS Department Lines: 34 Message-ID: <b0r960$21uu$1@agate.berkeley.edu> References: <b0qjos$s2dd0$2@ID-159027.news.dfncis.de> NNTP-Posting-Host: ribbit.cs.berkeley.edu X-Trace: agate.berkeley.edu 1043408896 67550 128.32.112.203 (24 Jan 2003 11:48:16 GMT) X-Complaints-To: usenet@agate.berkeley.edu NNTP-Posting-Date: Fri, 24 Jan 2003 11:48:16 +0000 (UTC) X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Originator: nweaver@ribbit.CS.Berkeley.EDU (Nicholas C. Weaver)