On Tue, Sep 30, 2008 at 7:33 AM, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > Russ Dill <russ.dill@xxxxxxxxx> wrote: >> >> I worked with this a bit, and since the IV has to be modified, it was >> just easier to check for nbytes less than or equal to block size in my >> own code and then back up src/dest pointers by iv_size and increase >> the size by iv_size. (My IV is prepended to my data). On decryption I >> do something similar by adding a buffer for the output of the IV. > > I suggest that we fix the CTS algorithm (i.e., give it a block size > of 1 instead of whatever it is now, plus make it work properly for > input equal or less than a block), and then implement RFC3962 on > top of it. > I'm just not sure how to best fit that into an API. In the case of number of bytes being greater than the underlying block size, everything works "normally". But in the case of the number of bytes being less than or equal to the block size, the IV sent to the remote end needs to be modified. -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
