Tag Info

New answers tagged

16

FIPS 140-2 does not cover the topic of password hashing. Thus, there is no password hashing function which would be "FIPS-approved" in that sense. Using SHA-512 "as is", with or without some salt and regardless of how you inject the said salt in the engine, would not grant you the NIST approval. NIST simply does not approve (or disapprove of) password ...


5

FIPS 140-2 does not list password hashing algorithms. If you actually need to use FIPS 140-2 validated algorithm, you need to find solutions that were validated by NIST for your required compliance level. You probably need to verify this with a FIPS auditor, but PBKDF2 has implementations like PBKDF2-HMAC-SHA256 or 512 for instance. That could be regarded ...


1

The question now is, what is the meaning if 0xffff? Does it mean that the server does not understand the set of curves suggested by the client? I don't think it officially means this. But I have a feeling that the implementation is still doing it with that intention. Unassigned at IANA The identifier 0xFFFF (65535 decimal) is marked as Unassigned in ...


2

Look at RFC4492 Section 5.1.1 that you mention in your post, we see the following structure: enum { sect163k1 (1), sect163r1 (2), sect163r2 (3), sect193r1 (4), sect193r2 (5), sect233k1 (6), sect233r1 (7), sect239k1 (8), sect283k1 (9), sect283r1 (10), sect409k1 (11), sect409r1 (12), sect571k1 (13), sect571r1 (14), ...



Top 50 recent answers are included