Hongwei,
> We confirmed that AesCrypt follows the normative reference of [FIPS197]
> (http://www.csrc.nist.gov/publications/fips/fips197/fips-197.pdf). As far
> as the statement about AES128 encryption CFB mode, we also confirmed that we
> do use 0 as Initialize Vector(IV), so in this case
You are very welcome Andrew! I am *overflowing* with satisfaction on being able
to deliver the goods.
Regards,
Bill Wesse
MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
TEL: +1(980) 776-8200
CELL: +1(704) 661-5438
FAX: +1(704) 665-9606
Good morning Andrew - just checking in to see if we have covered everything!
-Original Message-
From: Hongwei Sun
Sent: Wednesday, September 02, 2009 5:10 PM
To: 'Andrew Bartlett'; Bill Wesse
Cc: p...@tridgell.net; cifs-proto...@samba.org; Matthias Dieter Wallnöfer
Subject: RE: [cifs-prot
Metze,
Yes, AesCrypt function referenced in 3.3.4.2.1 is also the same function as
in 3.1.4.4 that is using CFB mode. You just need to concatenate twice the
same SequenceNumber, which is 8 byte number, to make a 16 byte IV.
I submitted a request for more example values in Section 4.2
