Take the shared prekey and phi from the client about libotr-ng

[olabini]

Maybe make an API in libotr-ng that specifies the different things that can go in to phi - for example alice_identity, bob_identity, prearranged_password

[juniorz]

It should be enough to do only the part that is in libotr-ng: provide a way to input phi and the shared prekey when a messages needs them.

I propose merging the phi part with #58 and leaving this as generating the shared prekey.

[juniorz]

In order to generate phi', the protocol expects to receive 3 string parameters:

• 2 identifiers (one per participants).
• a password (optionally).

The phi' string is created by joining the 2 identifiers (in lexicographical order). If a password is provided, it is appended to the end of this session state string.

The shared session state string is then generated by joining the 2 participants' instance tags (in numerical order), the query message, and the phi' string.

[juniorz]

• Update the spec.

[deniscostadsc]

Cases like this should also have a segfault if not implemented? If yes I going to remove this checks from these if's.

[claucece]

Cases like this should also have a segfault if not implemented? If yes I going to remove this checks from these if's.

We already discussed over IRC around this the other day. Right now we are not dealing with these errors as they are part of the plugin/client work. We will deal with them once we start there. So, I'll suggest leaving it there.

[juniorz]

These are not callbacks that receive value from outside, bur rather inform the outside that something happened.

If the outside does not want to be informed, the protocol can still move on.

[claucece]

Yeah, still for things that inform the outside, I'll prefer to leave them as that for the moment and deal with them in the plugin work.

I'll say that we should inform, but we will see on the plugin work..

[deniscostadsc]

Ok! Thanx!