vyos-1x.git/src, branch 1.3.5 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.3.5 2023-12-04T17:38:23+00:00 https: T5772: return from verify if None 2023-12-04T17:38:23+00:00 John Estabrook jestabro@vyos.io 2023-12-04T17:16:25+00:00 urn:sha1:7c6de792279350c980160096887524836b44be47 ​ Signed-off-by: Daniil Baturin <daniil@baturin.org> https: T5772: require that at least one valid API key is present 2023-12-04T15:38:11+00:00 Daniil Baturin daniil@baturin.org 2023-12-04T15:38:11+00:00 urn:sha1:976c800c4ba5bd1f4856ea2fa112e89af979bacf Revert "https api: T5772: check if keys are configured" 2023-12-04T15:36:57+00:00 Daniil Baturin daniil@baturin.org 2023-12-04T15:36:57+00:00 urn:sha1:a148b81659afb02947594cc9255b3162069f86f5 This reverts commit 57ba2fa91573ad2ecd03f0c2eb89507dfc397f1e. https: T5772: remove the default API key 2023-11-30T13:58:39+00:00 Daniil Baturin daniil@baturin.org 2023-11-30T13:58:39+00:00 urn:sha1:ad72670a1f7410a3c4a7e2021f0b7511156f5850 The new verification code prevents it from being used, but it's not a reason to keep it Merge pull request #2536 from c-po/backport-pr-2527 2023-11-28T14:27:07+00:00 Christian Breunig christian@breunig.cc 2023-11-28T14:27:07+00:00 urn:sha1:50a78a29e3bbe6ccc2e070706133c06f6053a612 pppoe: T5630: make MRU default to MTU if unspecified (backport #2527) T5763: fix imprecise check for remote file name 2023-11-27T13:44:48+00:00 John Estabrook jestabro@vyos.io 2023-11-20T15:40:58+00:00 urn:sha1:9e97aa8764b369c90d42497c0897efd7b76634ea (cherry picked from commit fe9b08665367b8e7d9b906a0760d44efc9b5cafb) pppoe: T5630: make MRU default to MTU if unspecified 2023-11-23T11:06:31+00:00 Christian Breunig christian@breunig.cc 2023-11-22T10:40:29+00:00 urn:sha1:220750b9e747c7f539849e96889cfef695300313 This fixes the implementation in e062a8c11 ("pppoe: T5630: allow to specify MRU in addition to already configurable MTU") and restores the bahavior that MRU defaults to MTU if MRU is not explicitly set. This was the behavior in VyOS 1.3.3 and below before we added ability to define the MRU value. (cherry picked from commit ffd7339e2ea3eafdd97ac0763ca4a3913fe71bf3) https api: T5772: check if keys are configured 2023-11-23T10:24:58+00:00 Daniil Baturin daniil@baturin.org 2023-11-22T00:53:35+00:00 urn:sha1:57ba2fa91573ad2ecd03f0c2eb89507dfc397f1e unless PAM auth is enabled for GraphQL (cherry picked from commit 8c450ea7f538beb0b2cd21d35c05d18db49a1802) PAM: T5577: Optimized RADIUS PAM config 2023-11-20T17:07:11+00:00 zsdc taras@vyos.io 2023-09-26T08:27:07+00:00 urn:sha1:d7457268fcaa5626e512eb00a9aab36f4a617f28 - Added system `radius` group - Added `mandatory` and `optional` modes for RADIUS - Improved PAM config for RADIUS New modes: - `mandatory` - if RADIUS answered with `Access-Reject`, authentication must be stopped and access denied immediately. - `optional` (default) - if RADIUS answers with `Access-Reject`, authentication continues using the next module. In `mandatory` mode authentication will be stopped only if RADIUS clearly answered that access should be denied (no user in RADIUS database, wrong password, etc.). If RADIUS is not available or other errors happen, it will be skipped and authentication will continue with the next module, like in `optional` mode. T4940: new interfaces debugging command equuleus 2023-11-16T05:02:29+00:00 mkorobeinikov 92354771+mkorobeinikov@users.noreply.github.com 2023-11-16T04:43:00+00:00 urn:sha1:bb5baa44ef82d2e888ece14bad13df60b13cf62e