DormantDex has quit [Ping timeout: 201 seconds]
NBones has quit [Ping timeout: 201 seconds]
NathanKell is now known as NathanKell|AFK
DuoDex has joined #spacedock
NBones has joined #spacedock
NathanKell|AFK is now known as NathanKell
NathanKell is now known as NathanKell|Twitch
NathanKell|Twitch is now known as NathanKell
NathanKell is now known as NathanKell|NOMZ
NathanKell|NOMZ is now known as NathanKell
NathanKell is now known as NathanKell|Twitch
NathanKell|Twitch is now known as NathanKell|AWAY
egg|zzz|egg is now known as egg
NathanKell|AWAY is now known as NathanKell
NathanKell is now known as NathanKell|AFK
Alanonzander has quit [Ping timeout: 200 seconds]
Alanonzander has joined #spacedock
NathanKell|AFK is now known as NathanKell
<RockyTV> VITAS, Thomas should I use a reverse proxy for my local znc server (if I want to enable access to it from the internet)?
<VITAS> arent reveres proxys mainly for http?
<VITAS> what you would need is port forwarding
<RockyTV> o
<RockyTV> nvm then
<VITAS> if that isnt possible you need to havesome sort of vpn to some public host and do the forwarding there
<RockyTV> what about the webpanel?
<RockyTV> I've found this https://wiki.znc.in/Reverse_Proxy
<VITAS> it still relys on the original ip and port to be reachable by the reverse proxy
<VITAS> If you want to use a subdomain for the ZNC-Webinterface, you have to create a Reverse Proxy with your webserver.
<RockyTV> so the reverse proxy here is only allowing a subdomain to be used to access the webpanel
<RockyTV> ?
<VITAS> so it isnt about making it reachable
<VITAS> see my text above
<RockyTV> I made it reachable
<RockyTV> just wanted to know if it increases security over the webpanel
<VITAS> it could be usefull if their webserver implementation has flaws
<VITAS> or to protect from dos attacks
<VITAS> i would rate it at: nice addition but not essential
<VITAS> i would use some well established reverseproxy if i would do it
<VITAS> so e.g. apache ngnix trafficserver
<VITAS> etc.
<RockyTV> another question
<RockyTV> chroot is pretty much an isolation for the desired process, right? kinda like a container for the process
<VITAS> more like jails
<RockyTV> why?
<VITAS> it shares more with the host than containers do
<RockyTV> huh?
<VITAS> its a sandbox
<VITAS> but anyway
<VITAS> whats the question?
<RockyTV> if it's sandboxed, does it mean that if something affects that chroot, it won't affect the whole host?
<VITAS> yes but stuff that changes the host changes the chroot
<VITAS> e.g. changed libs
<RockyTV> ah
<RockyTV> so chroot can't change host
<VITAS> thats the idear
<VITAS> i still would suggest real containers unless you want to let others ssh into them
NathanKell is now known as NathanKell|Twitch
egg is now known as egg|zzz|egg