search for: rfc2104

$ dovecotpw -p testpass {HMAC-MD5}fe8522268d91e485ccac8f36800e4fa6b10363e2a371cfa61731109b450906cd I wonder if the prefix 'HMAC-MD5' is the correct notation here. According to RFC2104 an HMAC is calculated as follows: H(K XOR opad, H(K XOR ipad, text)) where H is the cryptographic hash function (MD5 in this case). Therefore the result has to be a 128 bit string, which is obviously not the case in the above shown example. In addition, the input value 'text' is missing...

I was looking at the the way that ssh calculates an hmac, and I noticed that the ordering is a little strange - it does hash(key+message). Shouldn't this rather be hash(message+key)? In the former situation, it could be possible for an attacker to append something to the end of the data being sent. The attacker would be able to calculate a valid hmac without knowing the key. For instance,

I'm trying to create an R script that will execute the HMAC algorithm for key-hashing messages. My hope is to use this script for some web authentication via R. The algorithm is found at http://www.ietf.org/rfc/rfc2104.txt Here is some example code that I have done that does not work for HMAC-MD5. I'm a big confused by the algorithm since I don't have a very good working knowledge of digests or hex strings. I would really appreciate some assistance if anyone can take a look at this code and offer advic...

...include: Fix out of place comment for DLGC_* codes. Jonathan Ernst (4): taskmgr: Fix an error in French translation. Use SUBLANG_NEUTRAL in French resources. wineconsole: Updated French translation. oledlg: Updated French translation. Kai Blin (4): secur32: Implement RFC2104 (HMAC) with MD5 for NTLMv2. secur32: Get rid of NEGO_* helper modes, they will never be used. Negotiate should not be done via ntlm_auth. secur32: Stop leaking the session key memory. secur32: Add include guard to hmac_md5.h. Karsten Elfenbein (3): wined3d: BltOverride: Mak...