• 1 Post
  • 10 Comments
Joined 1Y ago
cake
Cake day: Jun 12, 2023

help-circle
rss

Yeah, whoever thought that sd cards were a good idea for anything even resembling operating systems is a dum dum


The issue is, you can optimize a software encoders continually, you can use tricks for better quality etc.

A hardware encoder is just that - hardware. As soon as it’s burned to the silicon, you’re not making any (at least substantial) changes to it. You might also be limited by what you can actually do directly in hardware without using too much die space.

Tldr.: no, you won’t get the same result


I noticed it tries to start listening on 192.168.1.100, don’t see a “network: host” in the compose file, don’t think it should have access to that IP address.

Not sure how to explore that further but might put you on the right path



What is a password? A string of characters. What is a link? A string of characters.

If you make it long enough, it’ll be impossible to guess one.

Your files are safe


Yeah, fair, there is a UI, but it’s veeery basic, not at all comparable with TrueNAS


If they really want just ZFS, Proxmox offers it.

It just doesn’t come with a built-in UI


I’ve got 2FA set up and required, so I’m not too worried about brute force attacks.


I’ve got firewall set up, services are only accessible through the reverse proxy, was more concerned about something like logging into keycloak and having the password leaked with MitM or another attack of the sort.


Cross-container/vm communication security on Proxmox
Hey, I've got a bunch of services all running in their own containers/vms on Proxmox. All of these have their own ips that are accessible from my network. I also have a container with a reverse proxy, which acts as a gateway for access to these services (it's IP is the only one allowed to go through the firewall of each service). These services have http servers, no encryption. Could someone on my network listen to comms between a service and my reverse proxy? Would have to play around with VLANs if that's the case... Thanks
fedilink

Try a reverse proxy (like the nginx-proxy-manager)