From c60c5234c548ff960d3e62df1eefedfeef59e057 Mon Sep 17 00:00:00 2001 From: LinuxServer-CI Date: Thu, 13 Oct 2022 15:53:18 +0200 Subject: [PATCH] Bot Updating Unraid Template --- unraid/nntp2nntp.xml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/unraid/nntp2nntp.xml b/unraid/nntp2nntp.xml index fe0e306..7353857 100755 --- a/unraid/nntp2nntp.xml +++ b/unraid/nntp2nntp.xml @@ -21,8 +21,11 @@ Whilst we know of no nntp2nntp security issues the upstream code(https://github.com/linuxserver/nntp2nntp) for this project has received no changes since 06.08.15 and is likely abandoned permanently. For this reason we strongly recommend you do not make this application public facing and if you must do so other layers of security and SSL should be considered an absolute bare minimum requirement. We see this proxy being used primarily on a LAN so that all the users NNTP applications can share a common set of internal credentials allowing for central managment of the upstream account e.g change provider, server, thread limits for all applications with one global config change. https://raw.githubusercontent.com/linuxserver/templates/main/unraid/nntp2nntp.xml https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/nntp2nntp-logo.png - 2019-12-19 + 2022-10-10 +### 2022-10-10 +- Rebase to Alpine 3.15. + ### 2019-12-19 - Rebasing to alpine 3.11.