Make Onet independent from Kyber

[Gilthoniel]

Those are the different points to change for Onet to be independent:

• ServerToml is now tightly bound to kyber because of the public identity of a server that is a kyber point. One the same topic, suites are used to unmarshal the points.

• TLS hack might need a rewrite or an adaptation as the server identity is used in the process.

• ServerIdentity holds the key pair of the server and the services' key pairs which are defined by Kyber.

Overall it doesn't seem to be an impossible task.

[Gilthoniel]

https://tools.ietf.org/html/rfc7250

[ineiti]

I only followed this from afar, so I might be completely off...

If I understand correctly, the goal is to allow for transport of lattigo structures in onet. So I don't understand why the question is make onet independent from kyber rather than add lattigo support to onet?

If instead of the kyber.Suite in the onet.serviceEntry there is a possibility of adding lattigo.Suite (which doesn't exist, but something like it) to the serviceEntry, you could use lattigo with onet, no?

Even though, if I remember correctly, there is a setup-phase in lattigo when creating the private keys. Or do I remember that wrongly?

[Gilthoniel]

That is just an issue for me to keep track of what I did but I'm meeting next week with Christian to understand better what would the best for everyone.