VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=1.4.0 2024-02-23T13:02:11+00:00 2024-02-23T13:02:11+00:00 sarthurdev 965089+sarthurdev@users.noreply.github.com 2024-02-23T12:14:54+00:00 urn:sha1:1c7fd8a7635e9a8c87de178fcb0735c6ed83b669 (cherry picked from commit e2adfdef9e79aa7550e82a12d661718a479aba90) 2024-02-13T20:39:59+00:00 Christian Breunig christian@breunig.cc 2024-02-11T20:49:25+00:00 urn:sha1:71397fb4070758e5ce29be08a3572bf3ee62cb06 set pki openssh rpki private key ... set pki openssh rpki public key ... set pki openssh rpki public type 'ssh-rsa' (cherry picked from commit 8c78ef0879f22ffd4a5f7fdb175e9109b46e9d7b) 2024-02-10T11:15:49+00:00 Christian Breunig christian@breunig.cc 2024-02-10T11:07:55+00:00 urn:sha1:ec049d192ddb1d2173d54b429213694ba0e6f15f (cherry picked from commit d4278cde2b153e163fe41e1bc461891397336bc3) 2024-01-10T07:11:39+00:00 Christian Breunig christian@breunig.cc 2024-01-06T09:55:42+00:00 urn:sha1:34eadcf2f74ae57342997bed77ce64bddd34219b We have not seen the adoption of the https virtual-host CLI option. What it did? * Create multiple webservers each listening on a different IP/port (but in the same VRF) * All webservers shared one common document root * All webservers shared the same SSL certificates * All webservers could have had individual allow-client configurations * API could be enabled for a particular virtual-host but was always enabled on the default host This configuration tried to provide a full webserver via the CLI but VyOS is a router and the Webserver is there for an API or to serve files for a local-ui. Changes Remove support for virtual-hosts as it's an incomplete and thus mostly useless "thing". Migrate all allow-client statements to one top-level allow statement. (cherry picked from commit d0d3071e99eb65edb888c26ef2fdc9e038438887) 2023-12-20T01:07:42+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2023-12-08T14:14:07+00:00 urn:sha1:a3e059e7e8d340f6f5e623bbc17acf18cb296626 Add ability to configure multiple SSL certificates for frontend/service set load-balancing reverse-proxy service web mode http set load-balancing reverse-proxy service web port 443 set load-balancing reverse-proxy service web ssl certificate cert1 set load-balancing reverse-proxy service web ssl certificate cert2 (cherry picked from commit fe99c45e05fd5794905145ddca80e6078145c2e8) 2022-06-28T23:37:59+00:00 sarthurdev 965089+sarthurdev@users.noreply.github.com 2022-06-25T21:04:31+00:00 urn:sha1:0d5ac59894ae7c10bd9d69047fa7098de66f835f 2021-09-06T10:02:06+00:00 Christian Poessinger christian@poessinger.com 2021-09-06T10:02:06+00:00 urn:sha1:b060fb70cdca155027f92222ea0d989f8e9bf21f 2021-06-29T19:26:44+00:00 sarthurdev 965089+sarthurdev@users.noreply.github.com 2021-06-29T09:06:44+00:00 urn:sha1:f5a8a9cdfe52c331177c8bc7b8fb84fc08d4f60a 2021-06-29T13:13:34+00:00 sarthurdev 965089+sarthurdev@users.noreply.github.com 2021-06-17T16:08:58+00:00 urn:sha1:6f66e71e4622c54058b8689d4be730905d69fe22