Valery Smyslov writes:
> Hi Paul and Tero,
>
> thank you for your answers.
>
> > > The PRF (or set of PRFs) is known by the receiving party. If the two
> > > parties always only use one PRF, it is known. The padding is not a
> > > universal solution for the reasons you give, but it works in the
>
Hi Paul and Tero,
thank you for your answers.
> > The PRF (or set of PRFs) is known by the receiving party. If the two
> > parties always only use one PRF, it is known. The padding is not a
> > universal solution for the reasons you give, but it works in the
> > common case of peers who know each
Paul Hoffman writes:
> At 9:58 AM +0300 10/30/09, Valery Smyslov wrote:
> >Hi all,
> >
> >I'd like to reiterate my early message, which I haven't got answer to.
> >My concerns are:
> >
> >1. How padding pre-sahred key with string "Key Pad for IKEv2"
> >could help to avoid storing pre-shared key
At 9:58 AM +0300 10/30/09, Valery Smyslov wrote:
>Hi all,
>
>I'd like to reiterate my early message, which I haven't got answer to.
>My concerns are:
>
>1. How padding pre-sahred key with string "Key Pad for IKEv2"
>could help to avoid storing pre-shared key in IKE implementation
>if prf is
Hi all,
I'd like to reiterate my early message, which I haven't got answer to.
My concerns are:
1. How padding pre-sahred key with string "Key Pad for IKEv2"
could help to avoid storing pre-shared key in IKE implementation
if prf is not known untill IKE_SA_INIT exchange is finished?
2. It
