I'll stick to windows. I don't want to deal with those people."
That's a strange conclusion to come to, installing an OS doesn't come with the obligation to deal with anyone.
I like to play games on Steam but that doesn't mean I have to deal with the atrocity that is the Steam forums.
Once again, the format doesn't work for me when the main topic is about a fad that nobody talks about anymore.
It worked in South Park for a long time because they had a relevant episode a week or two after it happened. In Futurama, not so much.
The Bender story was pretty neat though. They could have left out all of the NFT stuff and focused just on the Bender plot and it would have been a significantly better episode.
Random Access Memories by Daft Punk is my favorite album of all time.
Hey, same here.
Some other albums I really like (in no particular order):
Android also encrypts the user data by default since Android 10 (2019).
Android also has different permissions the apps need to ask for just like iOS. Including not allowing background apps to use the camera/GPS/mic by default.
Yeah, I'm also on my third controller RMA. First the stick on the left controller started drifting, then the right controller's plastic started peeling off and finally the right controller stopped working altogether.
At least they did the third RMA for free way out of warranty.
Had to buy a new headset cable on my own though when the display started flickering after 2 years. They also sent me a new plastic clip for the cable on the back when the old one broke and a new left speaker when it started crackling instead of requiring me to send in the full headset so that's pretty cool.
Also, abusing a Github issue as your personal Twitter timeline is not going to persuade anyone.
The comments in that issue are atrocious.
Yes, because Docker becomes significantly more powerful once every container has a different publicly addressable IP.
Altough IPv6 support in Docker is still lacking in some areas right now, so add that to the long list of IPv6 migration todos.
There is this notion that IPv6 exposes any host directly to the internet, which is not correct. When the client IP is attacked "directly" the attacker still talks to the router responsible for your network first and foremost.
While a misconfiguration on the router is possible, the same is possible on IPv4. In fact, it's even a "feature" in many consumer routers called "DMZ host", which exposes all ports to a single host. Which is obviously a security nightmare in both IPv4 and IPv6.
Just as CGNAT is a thing on IPv4, you can have as many firewalls behind one another as you want. Just because the target IP always is the same does not mean it suddenly is less secure than if the IP gets "NATted" 4 times between routers. It actually makes errors more likely because diagnosing and configuring is much harder in that environment.
Unless you’re aggressively rotating through your v6 address space, you’ve now given advertisers and data brokers a pretty accurate unique identifier of you. A much more prevalent “attack” vector.
That is what the privacy extension was created for, with it enabled it rotates IP addresses pretty regularily, there are much better ways to keep track of users than their IP addresses. Many implementations of the privacy extension still have lots of issues with times that are too long or with it not even enabled by default.
Hopefully that will get better when IPv6 becomes the default after the heat death of the universe.
Will take a look at the talk once I get time, thanks. If you can find the original one you were talking about, please link.
For servers, there is some truth that the address space does not provide much benefit since the addressing of them is predictable most of the time.
However, it is a huge win in security for private internet. Thanks to the privacy extension, those IPs are not just generated completely random, they also rotate regularily.
It should not be the sole source of security but it definitely adds to it if done right.
With NAT on IPv4 I set up port forwarding at my router. Where would I set up the IPv6 equivalent?
The same thing, except for the router translating 123.123.123.123 to 192.168.0.250 it will directly route abcd:abcd::beef to abcd:abcd::beef.
Assuming you have multiple hosts in your IPv6 network you can simply add "port forwardings" for each of them. Which is another advantage for IPv6, you can port forward the same port multiple times for each of your hosts.
I guess assumptions I have at the moment are that my router is a designated appliance for networking concerns and doing all the config there makes sense, and secondly any client device to be possibly misconfigured. Or worse, it was properly configured by me but then the OS vendor pushed an update and now it’s misconfigured again.
That still holds true, the router/firewall has absolute control over what goes in and out of the network on which ports and for which hosts. I would never expose a client directly to the internet, doesn't matter if IPv4 or IPv6. Even servers are not directly exposed, they still go through firewalls.
Anything connected to an untrusted network should have a firewall, doesn't matter if it's IPv4 or IPv6.
There's functionally no difference between NAT on IPv4 or directly allowing ports on IPv6, they both are deny by default and require explicit forwarding. Subnetting is also still a thing on IPv6.
If anything, IPv6 is more secure because it's impossible to do a full network scan. My ISP assigned 4,722,366,482,869,645,213,696 addresses just to me. Good luck finding the used ones.
With IPv4 if you spin up a new service on a common port it usually gets detected within 24h nowadays.
Hey there,
I used to have a command run 10 seconds after the screen is locked which turned all displays off. I can't find the option to run a command when the screen locks anymore.
In Plasma 5 I used this:
This is what it looks like in Plasma 6:
Is there another place to do this now?
Ha, they never learn. They also blocked most of Cloudflare in Austria a few years back.
Fun fact: It was the first IP block they tried. They haven't tried again since then.
https://blog.cloudflare.com/consequences-of-ip-blocking/