[bind10-dev] crypto API

[Francis Dupont]

> > The main question is inheritance vs embedding, i.e., if class X uses
> > class Y do we want:
> >  class X : Y
> > or
> >  class X {
> >   Y y;
> >  }
> 
> This is usually answered in this way:
> 
>   If X "is a" Y, then you write:
> 
>      class X : Y
> 
>   If X "has a " Y, then you write:
> 
>      class X {
>         Y y;
>      }

=> this is another form of the question, not an answer...

> > Now we need:
> >  - raw hash (at the top of most things)
> >  - keyed hash
> >  - HMAC (a case of keyed hash)
> >  - iterated hash (a more complex case of keyed hash)
> >  - signature public key (derives from raw hash)
> >  - signature private key (which includes the previous one)
> >  - DH?
> 
> Let's look into crypto++ and not write our own.

=> I disagree: the API should be designed from our needs, not in the
other way. But this doesn't mean crypto++ or botan or ... can't be
good source of ideas, I just prefer to look at applications first.

Francis Dupont <fdupont at isc.org>