Implement APIs for LCP support about go-toolkit HOT 5 CLOSED

cc @llemeurfr @danielweck

We're experimenting this first and based on our results we'll start a documentation and an epic to further discuss and specify on main repo.

from go-toolkit.

Question: it seems unsafe (from a personal info perspective) to post the passphrase in clear, even if we have allowed this in the open-source LCP server. Passing its hash (second example) seems better.
-> Why providing the two solutions in r2?
I copy @snemegeer and @danielweck because I forgot the rationale.

Note: after you experiment, it would be great to have a sequence diagram describing how it works in the two cases a) the client gets the license and will decode the streams b) the client posts the passphrase and expects the server to decode the streams.

from go-toolkit.

This is entirely meant for the use case where both the streamer and navigator are on the same client, not for server side LCP (which is still out of scope).

We've included both to make life easier for the launcher/navigator but it's definitely a point that should be up to discussions.

from go-toolkit.

TODO: Remove the option based on User Passphrase.

from go-toolkit.

Update: The first comment has been updated to remove the passphrase option.

from go-toolkit.