Storing 4 char prefix for 32bit hex token after storing HMAC digest

Joseph Carpenter

9/25/23, 8:46 AM

Currently I am working on a public api that uses token authentication. The token is a 32 bit random hex that is shared with the user and then stored in our database as an HMAC digest using a secret key. The token is not stored except for the first 4 characters.

My question is, is it safe to store the prefix like this?

My intuition tells me that it is not safe as it gives any attacker the beginning of the correct answer which therefore shortens the process of trying to brute force our secret key. I am wondering what someone with more expertise than I have thinks about this.

Thank you in advance.

0 + 0

hmac

Maarten Bodewes

9/25/23, 10:00 AM

32 bit random *hex*? Hexadecimals are a base 16 numbering scheme, often used to represent bytes. Bits are *binary digits*, i.e. base 2.

Score:0

Crypto

Maarten Bodewes

9/25/23, 9:58 AM

In cryptography we do always do all the calculations in bits. A HMAC has the same size as the hash used. Assuming a secure hash function such as SHA-256 you'd have an output of 256 bits, as reflected by the name.

Of this 32 bits are stored in your scheme. Now for a hash and a HMAC, the bits are all dependent on the input, but in principle you cannot tell anything about the unknown bits from the output bits. That means that 224 bits are remaining. An attacker would on average take $2^{223}$ guesses to get to the full HMAC value.

So you don't really have to worry about brute forcing assuming that you are using a secure hash function.

0 + 0

Maarten Bodewes

9/25/23, 9:58 AM

Beware that this answer doesn't give any indication of the security of your solution though; it's not an in depth analysis and such analysis is considered off topic for this Q/A site.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Storing 4 char prefix for 32bit hex token after storing HMAC digest

TH: จัดเก็บคำนำหน้าอักขระ 4 ตัวสำหรับโทเค็นฐานสิบหก 32 บิตหลังจากจัดเก็บไดเจสต์ HMAC

RO: Stocarea prefixului de 4 caractere pentru jetonul hexadecimal de 32 de biți după stocarea rezumatului HMAC

RU: Сохранение 4-символьного префикса для 32-битного шестнадцатеричного токена после сохранения дайджеста HMAC

VI: Lưu trữ tiền tố 4 ký tự cho mã thông báo hex 32 bit sau khi lưu trữ thông báo HMAC

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.