-
|
Hi, I am currently considering using zerobyte for my homelab to simplify the backup of my Docker containers. I read the disclaimer on the repository's homepage regarding the availability of the server on which zerobyte runs with the internet and do not quite understand why this disclaimer is given. Many of the services on my home lab are accessible from the internet, but not all of them. Does this just mean that zerobyte should not be accessible from the internet, but it is okay if other containers/services are? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
By exposing services to the internet you are basically inviting anyone to visit your homelab. You might have login screens in front of your apps but any bug or vulnerability in even one of your containers could let someone take over your server and all your data. While there are legitimate use cases for exposing stuff, there is practically always a safer solution to access your services remotely |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clarification, now I can better understand the disclaimer. I am aware that an application exposed to the internet always carries a certain security risk, but the disclaimer gave the impression that there was something else to consider with ZeroByte. Since I don't plan to expose ZeroByte and take the security of my home lab seriously, I am looking forward to working with Z |
Beta Was this translation helpful? Give feedback.
By exposing services to the internet you are basically inviting anyone to visit your homelab. You might have login screens in front of your apps but any bug or vulnerability in even one of your containers could let someone take over your server and all your data. While there are legitimate use cases for exposing stuff, there is practically always a safer solution to access your services remotely