ripemd
RIPE Message Digest
TOC »
Documentation
An implementation of the RIPE cryptographic hash function.
See message-digest-primitive for more information.
RIPE 128 API
Component export
Usage
(import ripemd128-api)
Constants
- name
- algorithm name ; symbol
- version
- algorithm version ; string
- context-size
- context byte length ; fixnum
- digest-length
- final byte length ; fixnum
- block-length
- buffer byte length ; fixnum
Note that block-length is informational only.
init
- init CTXprocedure
Initializes a RIPEMD128 CTX, with at least context-size byte size.
update
- update CTX OBJ LENprocedure
Accumulate LEN bytes from the Scheme OBJ into CTX.
raw-update
- raw-update CTX PTR LENprocedure
Accumulate LEN bytes from the byte PTR into CTX.
final
- final CTX OBJprocedure
Finalize the CTX into a Scheme OBJ with at least digest-length byte size. The target is usually a blob, u8vector, or string.
RIPE 128 Primitive
Packaged export
Usage
(import ripemd128-primitive)
ripemd128-primitive
- ripemd128-primitiveprocedure
Returns the 128-bit RIPE message-digest-primitive object.
RIPE 160 API
Component export
Usage
(import ripemd160-api)
Constants
- name
- algorithm name ; symbol
- version
- algorithm version ; string
- context-size
- context byte length ; fixnum
- digest-length
- final byte length ; fixnum
- block-length
- buffer byte length ; fixnum
Note that block-length is informational only.
init
- init CTXprocedure
Initializes a RIPEMD-160 CTX, with at least context-size byte size.
update
- update CTX OBJ LENprocedure
Accumulate LEN bytes from the Scheme OBJ into CTX.
raw-update
- raw-update CTX PTR LENprocedure
Accumulate LEN bytes from the byte PTR into CTX.
final
- final CTX OBJprocedure
Finalize the CTX into a Scheme OBJ with at least digest-length byte size. The target is usually a blob, u8vector, or string.
RIPE 160 Primitive
Packaged export
Usage
(import ripemd160-primitive)
ripemd160-primitive
- ripemd160-primitiveprocedure
Returns the 160-bit RIPE message-digest-primitive object.
Usage
(import ripemd)
Examples
- Note the message-digest-utils egg is a dependency for the example.
(import ripemd160-primitive message-digest-byte-vector) (message-digest-string (ripemd160-primitive) "abc") ;=> "8eb208f7e05d987a9b044a8e98c6b087f15a0bfc"
Notes
- The ...-primitive API is for use with the message-digest extensions. And the ...-api API implements the ...-primitive API. One packages the algorithm as a record, the other a module.
- RIPEMD-160 software written by Antoon Bosselaers, available at AB-9601.
Requirements
Author
Repository
This egg is hosted on the CHICKEN Subversion repository:
https://anonymous@code.call-cc.org/svn/chicken-eggs/release/5/ripemd
If you want to check out the source code repository of this egg and you are not familiar with Subversion, see this page.
Version history
- 2.1.0
- Split into api & primitive modules.
- 2.0.0
- CHICKEN 5 release.
- 1.3.0
- Add types.
- 1.2.0
- Add raw-update.
- 1.1.0
- Add block-length.
- 1.0.3
- Use release 3 of message-digest.
- 1.0.2
- Added identifier for message-digest-primitive.
- 1.0.1
- 1.0.0
- From the Chicken 3 version. Removed digest & binary-digest procedures.
License
Copyright (C) 2010-2021 Kon Lovett. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the Software), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED ASIS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.