mirror of
https://github.com/tuxbox-fork-migrations/recycled-ni-neutrino.git
synced 2025-08-26 15:02:50 +02:00
Thilo Graf
aafe499a69
- GUI management of API keys is now disabled by default for OpenWeather,
TMDb, OMDb, Shoutcast, and YouTube to enhance security.
In particular, the risk of accidental activation of GUI-based management
of API keys should be reduced.
- Introduced warning log messages to inform users about the risks of
enabling GUI management, which could potentially expose sensitive API
keys.
- Updated help strings to emphasize safe use of API keys.
- Added notices for users about the possible use of outdated API key
options.
- Implemented missing backward compatibility for some API option names
that have changed. This is necessary because build environments
generated with 'buildenv' do not necessarily adjust automatically to
the new options. This should prevent the risk of build failures and
ensure that older configurations remain compatible.
These changes aim to secure configurations better and mitigate the risk
of unintentional exposure of API keys to end users and should avoid build errors.
Origin commit data
------------------
Branch: ni/coolstream
Commit: f46c4177d2
Author: Thilo Graf <dbt@novatux.de>
Date: 2024-05-13 (Mon, 13 May 2024)
Origin message was:
------------------
configure.ac: More API key management security and improve backward compatibility
- GUI management of API keys is now disabled by default for OpenWeather,
TMDb, OMDb, Shoutcast, and YouTube to enhance security.
In particular, the risk of accidental activation of GUI-based management
of API keys should be reduced.
- Introduced warning log messages to inform users about the risks of
enabling GUI management, which could potentially expose sensitive API
keys.
- Updated help strings to emphasize safe use of API keys.
- Added notices for users about the possible use of outdated API key
options.
- Implemented missing backward compatibility for some API option names
that have changed. This is necessary because build environments
generated with 'buildenv' do not necessarily adjust automatically to
the new options. This should prevent the risk of build failures and
ensure that older configurations remain compatible.
These changes aim to secure configurations better and mitigate the risk
of unintentional exposure of API keys to end users and should avoid build errors.
------------------
This commit was generated by Migit