by that logic you can also stop providing the openssh server package, as thats also a *security* risk
tinc is a mesh based vpn, it only need one master node and all your clients connect to each other, its also more secure than openvpn aka it uses key based by defaults

I would like this as well. I use tinc to manage my client's desktops and servers remotely. Tinc is in every major distribution, so it's likely that many people use it. Tinc also offers features that other VPN's don't. Why would this be anymore of a security risk than openvpn? The project is not dead either, there was a commit 2017-01-15.

--can you tell I was listening to Ikey on Unplugged ;) ?

Should anyone want to install tinc, here are instructions: How to install tinc on Solus

In T857#43876, @jasonehines wrote:

Should anyone want to install tinc, here are instructions: How to install tinc on Solus

Thank you, fine stranger.

I also want to double your sentiments. Also, heard Ikey on LUP and this falls squarely in the criteria that Ikey was laying out as acceptable.

May we have this bug reopened please?

Ok, this is closed/won't fix.

Can we re-open this?

As long as it ticks the boxes here I've no objections.

https://solus-project.com/articles/packaging/package-inclusion-policy/en/

I checked, and it does tick all those boxes.

I believe the reasoning behind closing this was erroneous, assuming @DataDrake closed this for point 5 ("Server Software"), since this is a client for a mesh VPN and therefore both a server and a client.

There is also a newer version available now:
https://www.tinc-vpn.org/packages/tinc-1.0.31.tar.gz

I'd be willing to maintain it once I learn how to package it.