[email protected] (Frank Swarbrick) writes: > Does anyone know of a program/subroutine that can read "any kind" of > MVS sequential dataset and calculate an MD5 hash on it? By "any kind" > I am specifically meaning a file that is either FB or VB and can have > any LRECL.
note, MD5 has been depreciated for some time (decade ago, I was getting real-time messages from somebody in the crypto rump session where the compromise was being described) ... and asked to do list of internet RFCs mentioning/referencing MD5. http://en.wikipedia.org/wiki/Collision_attack my rfc index http://www.garlic.com/~lynn/rfcietff.htm see special list of RFCs referring to MD5 more recent reference 6151 I Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms, Chen L., Turner S., 2011/03/06 (7pp) (.txt=14662) (Updates 1321, 2104) (Refs 1321, 1939, 2104, 2202, 4231, 4270, 4493) (Ref'ed By 6150, 6176, 6331, 6421, 6528, 6542, 6668, 6920, 6929, 6931, 6952, 7217, 7292, 7298, 7317, 7321, 7376) from above: 2. Security Considerations MD5 was published in 1992 as an Informational RFC. Since that time, MD5 has been extensively studied and new cryptographic attacks have been discovered. Message digest algorithms are designed to provide collision, pre-image, and second pre-image resistance. In addition, message digest algorithms are used with a shared secret value for message authentication in HMAC, and in this context, some people may find the guidance for key lengths and algorithm strengths in [SP800-57] and [SP800-131] useful. MD5 is no longer acceptable where collision resistance is required such as digital signatures. It is not urgent to stop using MD5 in other ways, such as HMAC-MD5; however, since MD5 must not be used for digital signatures, new protocol designs should not employ HMAC-MD5. Alternatives to HMAC-MD5 include HMAC-SHA256 [HMAC] [HMAC-SHA256] and [AES-CMAC] when AES is more readily available than a hash function. ... snip ... -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
