On Wed, Jan 14, 2015 at 02:17:31PM +0000, Martin wrote: > Fantastic, having it in the CLI would great. It is for the reason of users > losing the pub key that I ask, writing some docs for an internal network. > Ah interesting, I finally found openssl does not have the 25519 curve in > there(and no plans to do so looks like) but I was not aware there was non > standard priv key format either. > > Would it make sense for the > > tinc -n <netname> get Ed25519PublicKey > > To have some logic to derive the pub key it if it's not already in the > hosts file? Just to avoid adding another command to the tinc CLI.
Adding another command is easy. Actually, I'm thinking of adding a
"fsck" or "check" command that checks whether everything is in order,
like configuration file permissions (executable bit on tinc-up for
example), misspelled variable names in the config files, and possibly
repairs what it can. And of course then also recreate the public keys if
necessary.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
