- 0 Posts
- 8 Comments
HappyFrog@lemmy.blahaj.zoneto
Privacy@lemmy.ml•Dropbox just disclosed ~5,000 compromised accounts😬
16·2 months agoI thought dropbox data was unencrypted by default, lol. I use Mega, and while I don’t fully trust the company, I believe that my data is safe. Also, I feel like 5k accounts are sp few compared to the amounts we usually see, lol
Thank you :3
Do you have any information where I can read more about this? I don’t want to listen to their podcast.
Are they trying to disrtance themselves, though?
Mullvad does not condone it, nor condemn it. It most likely was a bad idea; most things where there are a multitude of conflicting opinions necessarily are. But societies need a great diversity of ideas, initiatives and organizations who can be tested and sifted until the best ones remain.
HappyFrog@lemmy.blahaj.zoneto
Selfhosted@lemmy.world•Jellyfin Project Leadership ChangesEnglish
30·3 months agoI always find the phrasing of “effective immediately…” to sound a bit hostile, but I hope the transition is smooth.
I like mullvad and will continue to use them, but this was a terrible response. ÖrP is such a strange party. It’s nationalistic, but also Marxist, somehow. I haven’t read all their policies, but I dislike their immigration policy, and the way they act generally. They’re loud and provocational.
HappyFrog@lemmy.blahaj.zoneto
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com•Podman Quadlets Arr-Stack Setup And NetworkingEnglish
1·9 months agoI don’t know much about ip routing, but userns=keep-id id determined based on what podman is run as. For example, I run podman as user 1000 on the host, so if I do keep-id the user in the container will map to the same id. This often messes with things as the container require it is root inside it’s own context. It seems you are running podman as root, meaning that keep-id will map the container user to the actual root id, givintthe container essentially root access. Normally the container user is mapped to a random id on the host, like 653477, not 0. It’s unsafe to map the containers id to root as they would be unbounded if they managed to escape. I would recommend doing
systemctl caton the different services to see what the .container file expands to.When it comes to the networking I think that you need to create a podman network with internal set to true. I believe that this restricts internet access. Then you would need to only let these services communicate with gluetun.
I don’t know if this was any help, but it’s all I’ve managed to learn from doing it myself.
Here are some liks I found:
https://lists.podman.io/archives/list/podman@lists.podman.io/thread/NKVFO4JQO5JLYKWXHHODC2WHQRG7A2KO/
https://docs.podman.io/en/v4.6.1/markdown/options/userns.container.html
I would say that “develop Meta products” would still allow them to train their AIs on the content, even if that word is missing.