In the current configuration implementation of rsyslogd system_syslog.py the problem is that the render method
would need the tree of system syslog as well as the tree of system logs logrotate messages.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Wed, Nov 12
Jul 15 2025
Jul 9 2025
Jun 24 2025
Jun 23 2025
Jun 17 2025
Jun 10 2025
Jun 2 2025
May 28 2025
May 22 2025
The problem also appears when you only define
When viewing the template for the 1.5 versions it looks like the same problem is there
https://github.com/vyos/vyos-1x/blob/current/data/templates/rsyslog/rsyslog.conf.j2#L66
May 8 2025
May 6 2025
Note that this did make it into the 1.4.2 release; update project tags.
Note this is already backported for sagitta and present in 1.4.2; adjust project tag.
Apr 26 2025
Apr 25 2025
Apr 2 2025
@dmbaturin Are you sure that should be 100 instead of a two digit number? I think those will be done in lexicographic order, I suspect there may be confusion generated if someone tries to make a 110, and 11 runs first.
Thank you for the quick response to this, and the work to mitigate it 🙌
@mjones-vsat I think the wording is good.
Apr 1 2025
I was looking into backporting it myself lately, at a glance your approach seems correct. I'll look deeper into it.
Mar 31 2025
The above linked PR is ready for review by a maintainer. I've tried to cherry-pick only the most relevant commits from the upstream. The build was tested in the vyos-build container (as modified in https://vyos.dev/T7300) after each commit and the overall authentication flow was tested once as described in the PR.
Mar 30 2025
I looked through some Debian and Ubuntu ISOs and didn't notice dropbear installed in the live image. It's likely we are mostly susceptible to this because the live image is used as a loopback mount during normal installation. Many other Debian-based systems would be debootstrapped onto the host.