Open fieldmapper opened 2 years ago
@tkuester was this done? Looks implemented to me.
Not quite yet!
This can be implemented by hand, but it's a bear to do. Let me see if I can hack something in really quickly...
@Matthew-Beckett and @fieldmapper -- Just pushed a test feature branch today. I added some changes to the setup
command. A quick tutorial on how to run it:
$ sudo python3 -m pip install git+https://github.com/tkuester/taky@feature-byo-ssl
$ takyctl setup --public-ip 192.168.1.100 --cafile /path/to/ca.crt --cakey /path/to/ca.key new-taky-path
# And if you have a password on your CA, execute this, and rerun (assuming you trust taky to momentarily have your CA pass
$ export CA_PASS="blahblahblah"
Feature/Function Request:
Situation: I'm running a VPS server with two
taky
instances... instance 1 (main) calls/etc/taky/taky.conf
(at port 8089) and instance 2 (gp) is calls/etc/taky/taky-gp.conf
(at port 8090) both run the same set of certificates only the port number has changed.Current
build_client
command just runs it off the main taky.conf and whatever port is called onto it. Would there be a way to do something liketakyctl build_client secondary_cert -c /etc/taky/taky-gp.conf
so the appropriate configurations are applied on the newly generated client cert package?Thanks.