Many times you will have two parties with a shared symmetric key that
they will use to communicate authenticated and private messages to
each other. If you have multiple keys, then you somehow have to match
the key to the received message based on the context, the sender, or
some key identifier tha
Hi Frank,
> On Jul 1, 2016, at 11:11 AM, Frank Siebenlist
> wrote:
>
> snip snip key identifiers
This is why some key derivation functions and PRFs have “purpose” or “info"
fields, yes; including BLAKE2 and HKDF. Deriving a lesser key (which might just
be a keyid) is a perfectly valid strate
Hi lvh,
Guess you're the "lvh" who is responsible for "lvh/caesium" ;-). Good
to see that you've reanimated that project! Believe you were kind of
distracted for awhile, which "forced" me to play around with
"franks42/naclj"... which has been on live-support for about a year
now, because my new j
> On Jul 1, 2016, at 12:54 PM, Frank Siebenlist
> wrote:
>
> Hi lvh,
>
> Guess you're the "lvh" who is responsible for "lvh/caesium" ;-).
Yup. I’m also a founding member of PyCA and the resident cryptographer, which
is why I’m on this list :-)
> Good to see that you've reanimated that proje
… esprit de l’escalier: there’s also the difference between public-parameter
hashes and a PRF, and BLAKE2 will do both for you. So, are you trying to
identify a key in such a way that Eve can not detect the key being reused (but
Bob shares a key with you), or is that OK?
lvh
signature.asc
Des
