I'd actually tried the authors, but no reply yet (only a few days). I also tried the RFC Editor thinking they might have e.g. XML from which extraction might have been easier, but also no response yet. And I had found several libraries, but not the RFC code. I can't see any suggestion that the library you indicate includes that code, it also bills itself as a C++ library, which the RFC code is not (and also not what I want, but that's not a subject for this list).
But the broader point is that if it's worth the IETF publishing the code as an RFC, it's worth making the code available straightforwardly. For me, a thanks to Tony Hansen, who did the extraction for me. (That makes me feel a little guilty, why should he do my work I could have done?) But the point of posting on this list was to say that the code should be available so that each person wanting that code doesn't have to do that again. Christopher -- Christopher Dearlove Senior Principal Engineer, Communications Group Communications, Networks and Image Analysis Capability BAE Systems Advanced Technology Centre West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK Tel: +44 1245 242194 | Fax: +44 1245 242124 chris.dearl...@baesystems.com | http://www.baesystems.com BAE Systems (Operations) Limited Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK Registered in England & Wales No: 1996687 -----Original Message----- From: Hector Santos [mailto:hsan...@isdg.net] Sent: 27 June 2013 20:38 To: Dearlove, Christopher (UK) Cc: ietf@ietf.org Subject: Re: RFC 6234 code ----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet. Keep this in mind if you answer this message. Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages. -------------------------------------------------------- Ok, other than time, it should be easy to extract, clean up and cross your fingers that it compiles with your favorite C compiler. But I would write to the authors to get the original source. Or google: C source crypto libraries API hashing functions among the first hit: http://www.cryptopp.com/ On 6/27/2013 12:33 PM, Dearlove, Christopher (UK) wrote: > I want the specific code that is in the RFC (which happens to be in C) rather > than some other implementation. > ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ********************************************************************
