Turris OS packages issueshttps://gitlab.nic.cz/turris/os/packages/-/issues2024-03-12T14:20:58+01:00https://gitlab.nic.cz/turris/os/packages/-/issues/866turris-auth+lighttpd: make sure that turris webapps are not accessible in cas...2024-03-12T14:20:58+01:00Martin Matějekturris-auth+lighttpd: make sure that turris webapps are not accessible in case turris-auth is not runningIn case that turris-auth check & redirection (`https://<router-ip>/login?/`)
```
https://<router-ip>/login?/<target_url> --> https://<router-ip>/<target_url>
```
is not available to lighttpd for some reason - for example [turris-auth c...In case that turris-auth check & redirection (`https://<router-ip>/login?/`)
```
https://<router-ip>/login?/<target_url> --> https://<router-ip>/<target_url>
```
is not available to lighttpd for some reason - for example [turris-auth config for lighttpd](https://gitlab.nic.cz/turris/os/packages/-/blob/master/web/turris-auth/files/lighttpd.conf) cannot be loaded - then turris webapps are directly accessible without authentication.
It would be useful to have failsave config for lighttpd (or some other measure), which would block access to reforis in case that turris-auth is not running, but reforis is running.
---
Please note that in case turris-auth is running, but runtime error occurs, reforis and pakon (and probably other turris webapps that lacks internal authentication) won't be accessible - which is fine, because they are still, although in weird way, protected by turris-auth.
cc: @mhrusecky, @jschlehofer, @shenekRichard MuzikRichard Muzikhttps://gitlab.nic.cz/turris/os/packages/-/issues/829Omnia rescue does not boot correct mode2024-03-12T15:03:49+01:00Karel KociOmnia rescue does not boot correct modeThe current rescue behaves differently compared to the original one. The boot mode selection from the command line is shifted down by one (actually one is added).
The issue is that u-boot reads from i2c value where `0` is regular boot a...The current rescue behaves differently compared to the original one. The boot mode selection from the command line is shifted down by one (actually one is added).
The issue is that u-boot reads from i2c value where `0` is regular boot and anything else is rescue. This value is passed to as boot argument thus `1` is reboot and so on. The rescue for some reason (probably because of Mox) adds one to that and uses that as the mode. Thus reboot is not accessible and for example boot mode seven is on led 6.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/packages/-/issues/822Omnia: update rescue image2022-04-06T14:20:56+02:00Josef SchlehoferOmnia: update rescue imageTurris OS 6.1.0Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/packages/-/issues/589Mox: update u-boot to latest version2024-03-04T10:12:52+01:00Karel KociMox: update u-boot to latest versionUpdating U-boot in Moxes is highly needed to fix issues with BTRFS sparse blocks reading.Updating U-boot in Moxes is highly needed to fix issues with BTRFS sparse blocks reading.Turris OS 7.1.0Michal HruseckyMichal Hrusecky