v3 consent to attribute release : attribute hash function ?

[Cantor, Scott]

On 9/8/14, 12:09 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>When calculating the hash of attribute values used to determine if any
>values have changed since consent was last granted, should v3 use the
>DataSealer ? Maybe that's overkill for client-side storage since the
>DataSealer will be used again on the cookie.

No, that class is for when you have to encrypt data, it doesn't hash it.

> Currently, uApprove hex
>encodes the SHA-256 message digest of the concatenated values of an
>attribute. If the DataSealer should not be used in v3, it seems
>GZIP'ing and Base64 encoding, like the DataSealer does, would reduce
>storage size.

As Ian said, you won't gain much from compressing the result of a hash.

-- Scott