Hi Ameir,

> [..] Is there a way to join the network without copying all certificates to
> the known node?

Tinc (as far as I know) does not support any kind of in-band key distribution.
Thus you need to take care for this on your own. I consider this as a good
approach.

Personally I use the following approaches in different situations:
* store the public keys ("hosts" directory) in a shared version control
  repository (subversion/git)
* use rsync/scp for distributing the public keys from one central location
* configuration management (puppet, ansible, ...)

If you are using ansible for other administration tasks then maybe the attached
ansible task file helps you getting started. Just ignore it, if you are not
used to ansible.

I would suggest that you do not complicate things too much. Just extend the
tools that you are already using for your server or network administration.

Cheers,
Lars

Attachment: tinc.yml
Description: application/yaml

_______________________________________________
tinc mailing list
[email protected]
http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc

Reply via email to