Better documentation for CFB

[MarekKnapek]

Prerequisites

• Checked the developer manual
• Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=repo%3Alibtom%2Flibtomcrypt
• Checked that your issue isn't related to TomsFastMath's limitation that PK operations can by default only be done with max. 2048bit keys

Description

If you look at the definition of CFB mode (for example in NIST SP 800-38A document), you will see that CFB mode can accept integer parameter (called s) telling the CFB (roughly) how many bits shall process at a time. The parameter is often incorporated into the mode's name (such as 1-bit CFB mode, the 8-bit CFB mode, the 64-bit CFB mode, or the 128-bit CFB mode).

The problem is, that libtomcrypt doesn't document which CFB variant it uses.

Therefore in this issue I suggest to improve libtomcrypt's documentation to tell its users that it always uses the "full width" version of CFB ("full-width" meaning 128-bit CFB for AES cipher (I didn't test with other ciphers, yet)). This might apply to other modes as well (I didn't test other modes, yet).

Steps to Reproduce

Write AES + CFB implementation from scratch (yes, I'm masochist reinventing wheel) and test its correctness against other crypto library (such as libtomcrypt) and discover that both libraries behave differently.

Version

Latest git head, develop branch, 1.17.
Windows 10, x86 + x64, Visual Studio 2022.

Additional Information

It would be nice if libtomcrypt would implement the CFB s parameter, but this is not subject of this issue.

Best regards, Marek.

[sjaeckel]

Well, the documentation already states the following:

libtomcrypt/doc/crypt.tex

Line 828 in 06a81ae

Note that in this library the output feedback width is equal to the size of the block cipher. That is this mode is used

Looks like that isn't sufficient, maybe could require a bit more clarification.

Implementing the full spec would also be an option.

I'll leave this issue open until the doc is updated or the full spec is implemented, whichever comes first ;)

[levitte]

Note: this goes for OFB too.

[sjaeckel]

I added the different CFB modes in #587 , so current develop should be fine. @MarekKnapek can you maybe verify?

Note: this goes for OFB too.

Oh I wasn't aware of that! Reading that scanned document "FIPS PUB81" felt like a travel back in time :D

That shouldn't be too hard to implement, but also it's discouraged for more than 40 years IIUC... I doubt it even has been used in the wild since ltc exists ;)

[MarekKnapek]

I added the different CFB modes in #587 , so current develop should be fine. @MarekKnapek can you maybe verify?

Reading commits cf79fac and 2613264 in web browser seems fine. I can do some programming, but not sooner than this weekend.