sysnopsis says it all.
The coverage of SHA-2 was originally intended as part of the resynch with
PKCS#11 v2.20, tracked by CR#4920408.
See justification for the reason this is spun in a separate higher priority RFE.
xxxxx@xxxxx.com 10/20/04 16:33 GMT