Protocol specs

[TPS]

AfaIct, AGVPN's protocols aren't well-known/open but proprietary. Given most AG software is closed-source, but VPNs are inherently security/privacy software, it would be sensible to fully open those protocols to allow public vetting (not just this high-level overview), including its actual source code, e.g., schema doc(s) here in the KB, linking to the implementation GitHub repo that's actually compiled into the various products' binaries. That'd certainly give opportunity to increase oversight & transparency, as well as allowing potential weaknesses to be caught & fixed out in the open, & working against the "security through obscurity" worldview, which seems to work until it blows up publicly & spectacularly.

[denis9229]

We are already in the process of preparing the documentation. It will definitely be released publicly in the near future. We’ve done extensive testing, compared it with other protocols, and made improvements.

[TPS]

including its actual source code … linking to the implementation GitHub repo that's actually compiled into the various products' binaries

@denis9229 Will you be publishing the actual implementation source code as requested? That's the crucial part, since that's often where dangerous errors are found.

N.B.: I'm not asking for this to be released under a FOSS license (unless y'all want to & TIA if so! 🙇🏾‍♂️), just 1 permissive enough that security research may happen w/o fear of reprisal.

[TPS]

@denis9229 I see this is now marked Status: Done. Would you share the URL, please?

[denis9229]

@TPS Hi
Right now, we’re in the process of doing exactly that. At this point, our target deadline is before the New Year. We’re already very close

[TPS]

Happy New Year!

In light of https://gpg.fail/, what's the progress toward & current state of this request?