Wei Shao wrote:
Wan-Teh Chang wrote:
[EMAIL PROTECTED] wrote:
Hi,
HASH_* APIs provide a good wrapper for the hashing algorithms.
But secsign.c does not use any of these. It instead calls
create/update/end directly on the hash context.
Would it be better to use HASH_* APIs in secsign.c?
We co
Wan-Teh Chang wrote:
> [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > HASH_* APIs provide a good wrapper for the hashing algorithms.
> > But secsign.c does not use any of these. It instead calls
> > create/update/end directly on the hash context.
> >
> > Would it be better to use HASH_* APIs in secsign.
[EMAIL PROTECTED] wrote:
Hi,
HASH_* APIs provide a good wrapper for the hashing algorithms.
But secsign.c does not use any of these. It instead calls
create/update/end directly on the hash context.
Would it be better to use HASH_* APIs in secsign.c?
We could use HASH_* APIs in secsign.c. Per
Hi,
HASH_* APIs provide a good wrapper for the hashing algorithms.
But secsign.c does not use any of these. It instead calls
create/update/end directly on the hash context.
Would it be better to use HASH_* APIs in secsign.c?
Wei
___
dev-tech-crypto
4 matches
Mail list logo