Protocol specification/allow reimplementations

[rugk]

I guess to have some formal protocol specification would be great.

Especially so one could rewrite this in secure languages like Rust to rewrite the server component.

Also, I would generally call for rewrite this in memory-safe language like Rust. (in the future, maybe, of course)

---

Aka my idea would be to split this up and have:

• a tang-protocol that defines the endpoints/APIs (maybe also CLI tools) and how it can be used
• different implementations of that protocol like tang-c (this one here) and tang-rust etc.

To have a specification is e.g. also useful for #46 for instance.

[rugk]

By accident (i.e. seeing it in #27) I actually found a tang-nodejs implementation: https://github.com/cloggo/tangd

Given that this already seems to derivate a little (keys/rotate endpoint e.g.) I guess this shows:

1. that we really need a specification
2. that maybe the efforts should be combined? I.e. e.g. I should have been able to find all implementations somewhere. (a list of all) That I only found it accidentially shows that this is not good…
3. Thus, maybe there should be a (GitHub) organisation ("tang-project" or so), where you could collaborate?

/cc @cloggo

[rugk]

Any comment, @atchset?

[rugk]

Any comment, @latchset?
See also #46.
It would be nice to get any reaction at least, whether you support this idea or not etc.

[sergio-correia]

@rugk: sorry for the delay. I will get back to this in the next days.

[rugk]

@sergio-correia I do not want to push, but some time has passed…

[berlin4apk]

Any update?

[anatol]

Here are the implementation for Golang:

• Clevis part is here https://github.com/anatol/clevis.go
• Tang part is here https://github.com/anatol/tang.go