What is sketchy about downloading a torrent that it could save you from? Wouldn’t it be executing whatever you downloaded on another machine that would be the risky part?
What is sketchy about downloading a torrent that it could save you from? Wouldn’t it be executing whatever you downloaded on another machine that would be the risky part?
How would a thinking emoji make it clear your question isn’t serious? Also, things have been available for a limited time long before phishing attempts were a thing, and will continue to exist for legitimate purposes long after. You can’t expect the entire rest of the world to stop doing something innocuous just because it’s also used as a tactic to fool a small subset of inattentive people.
There’s no EULA just like there’s no NDA. That pop up and a one sentence post about not sharing info about the game on the forum is all there is.
There is no NDA for Deadlock, and anyone in it can invite anyone they want, as often as they want. It’s not like Valve has no idea how to privately test their game. I think they made these decisions deliberately.
lol I would open every port on my router and route them all to wireguard before I would ever consider doing this
I’d just install UFW and either set the default for incoming and outgoing to deny and unblock the game ports manually, or just set incoming to deny and outgoing to allow.
You could pair that with OpenSnitch to see all attempted incoming and outgoing connections and block them by default, and then just allow the ones you want as they happen.
I think I’m one of the very few people that actually like this game. I bought it when it came out and have played it a few times. This is all very valid criticism of it though.
My theory is that the RTSP port (554) is for streaming and that when I go to the local address (that is on 80), the site ITSELF initiates a connection to port 554 in the background. However, this apparently does not happen when I connect remotely.
I think you’re on the right track here. The DVR is probably telling your browser to connect to http://192.168.1.222:554 for the stream, which on LAN is fine because you have a route to 192.168.1.222, but when connecting externally you won’t be able to get to 192.168.1.222.
You can probably check the network connections in dev tools in the browser to confirm that.
Edit: Editing this to also stress the importance of the advice given by @SteveTech@programming.dev. My home cameras are also only accessible from outside my network via wireguard.
Removed by mod
Removed by mod
FPS, but mostly because I no longer have the free time to finish a 50-100 hour RPG.
I use Nextcloud with Nginx Proxy Manager and just use NPM to handle the reverse proxy, nothing in Nextcloud other than adding the domain to the config so it’s trusted.
I use Plex instead of Jellyfin, but I stream it through NPM with no issues. I can’t speak to the tunnel though, I prefer a simple wireguard tunnel for anything external so I’ve never tried it.
Edit: unless that’s what you mean by tunnel, I was assuming you meant traefik or tailscale or one of the other solutions I see posted more often, but I think one or both of those use wireguard under the hood.
I have a feeling the people making fiber internet faster aren’t the same people installing it in neighborhoods.
The product was an LLM.
I never switched to Proton for exactly this reason. I’d much rather use a service that does one thing really well than one that does 20 things okay.
It’s all just to keep you locked into your subscription. Now they want you to keep other money tied up in it too.
The issue is that the docker container will still be running as the LXC’s root user even if you specify another user to run as in the docker compose file or run command, and if root doesn’t have access to the dir the container will always fail.
The solution to this is to remap the unprivileged LXC’s root user to a user on the Proxmox host that has access to the dir using the LXC’s config file, mount the container’s filesystem using pct mount, and then chown everything in the container owned by the default root mapped user (100000).
These are the commands I use for this:
find /var/lib/lxc/xxx/rootfs -user 100000 -type f -exec chown username {} +;
find /var/lib/lxc/xxx/rootfs -user 100000 -type d -exec chown username {} +;
find /var/lib/lxc/xxx/rootfs -user 100000 -type l -exec chown -h username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type f -exec chown :username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type d -exec chown :username {} +;
find /var/lib/lxc/xxx/rootfs -group 100000 -type l -exec chown -h :username {} +
(Replace xxx with the LXC number and username with the host user/UID)
If group permissions are involved you’ll also have to map those groups in the LXC config, create them in the LXC with the corresponding GIDs, add them as supplementary groups to the root user in the LXC, and then add them to the docker compose yaml using group_add.
It’s super confusing and annoying but this is the workflow I’m using now to avoid having to have any resources tied up in VMs unnecessarily.
I’ve been doing this for at least a decade now and the drives are just as reliable as if you bought them normally. The only downside is having to block one of the pins on the SATA connector with kapton tape for it to work.
Acts as a wildcard for any directories that exist between arteries and clot.
I’m pretty sure Fooyin meets all these. It’s still very early in development but I like it more than any of the other native Linux music players I’ve tried.
They’re already ignoring robots.txt, so I’m not sure why anyone would think they won’t just ignore this too. All they have to do is get a new IP and change their useragent.