| Allegro CL version 10.0 Unrevised from 9.0 to 10.0. 9.0 version |
Arguments: context &key return
Finalize and return the RMD160 hash from context in a format determined by the return keyword argument.
return can be one of the following values:
:integer
(the default): the return value is an
integer of up to 128 bits representing the digest. Warning: note that
an integer representation of the digest potentially loses information
if the generated signature has leading octets containing only
zeroes. Care should be taking when using this return type if you
intend to further encode the digest (such as to a base64-encoded
string). See the example below.
cl-user(4): (setq c (rmd160-init)) #S(excl::md-context :ctx 9183168 :size 20) cl-user(5): (rmd160-update c "foo") cl-user(6): (rmd160-final c :return :usb8) #(66 207 162 17 1 142 164 146 253 238 ...) ;; Potential problem with :return :integer (or :return unspecified ;; as the default is :integer). The call is to RMD160-FILE which calls ;; RMD160-FINAL and returns the value RMD160-FINAL returns. ;; ;; Here we get the rmd160 value in a shell: % openssl dgst -rmd160 -hex qall.jpg RIPEMD160(qall.jpg)= 05e527b6387540cc9162049b5f60e960f00f8299 ;; Now we get it with RMD160-FILE: cl-user(17): (rmd160-file "~/qall.jpg") 33655283890170409359154440781670075183125201561 cl-user(18): (format t "~x" *) 5e527b6387540cc9162049b5f60e960f00f8299 nil cl-user(19): ;; Note the hex values are the same but the leading 0 is not printed ;; by Lisp, which is dealing with the value as an integer. The leading ;; 0 is preserved when the :return is :hex: cl-user(19): (rmd160-file "~/qall.jpg" :return :hex) "05e527b6387540cc9162049b5f60e960f00f8299" cl-user(20):
See MD*, SHA*, HMAC, and other message digest support in miscellaneous.htm. See also digest-final.
Copyright (c) 1998-2019, Franz Inc. Oakland, CA., USA. All rights reserved.
This page was not revised from the 9.0 page.
Created 2015.5.21.
| Allegro CL version 10.0 Unrevised from 9.0 to 10.0. 9.0 version |