![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/4271bdc6-5114-4749-a5a9-afbc82a99c78.png)
HTTPS isn’t only about encryption; it’s about talking to the right servers.
HTTPS isn’t only about encryption; it’s about talking to the right servers.
.txz
, I’m too lazy to type the full name
I’m trying a new approach. Since I won’t touch anything beyond W10, and W10 is getting officially phased out, I just informed people that I won’t provide tech support for W11 and beyond.
Not at all. I’m arguing that often, the issues, and fixes, are not distribution-dependant. Which is a good thing; it means we can go to arch forum and find fixes that can be applied in other distros most of the time, for example.
But people keep pitting them against each other like they’re some form of evolved lifeforms that necessarily have to erase others, when a lot of the issues are just generic software issues.
And, since this is already a justification post I’ll take the lead and note that it does not mean that there is no distribution-specific issues. Of course there are. The point is that most software issue in distribution X will have the same cause and fix in distribution Y, and often have nothing to do with either specific distributions.
People keep arguing about this or that distro.
Linux distributions are just a collection of software, initial settings, and sometimes online repository.
“New device detected: mouse. Please wait…”
But the mouse is already working dude.
Heck, I have errors in windows log that are just “sure, let’s move on”.
It’s ok, they just started the “security first” initiative, we’re all saved.
There is no software solution that protects from a crowbar, you have to go to the hardware side.
You really are missing the point that if the device is rooted there is nothing an app can do to protect itself. Defense in depth is layering (sometimes overlapping) solutions that do something. Detecting root and saying “nuh-uh” is not doing anything.
So? If I, the customer, want to access my banking info, on my phone, with whatever means I want, I should be able to. As I said, it’s not like every app gets root access, if I, as the owner of the device, explicitly gave root access to something, it’s for a reason.
And the main point that a rooted phone can basically hide itself from any app remains; these “detections” are trivially bypassed in the exact situation they’re supposed to detect.
As long as we’ll have control over the software, it’ll be there. If we reach the point were you’re not allowed to own computers, we’ll have bigger problem.
Root access means any app installed could potentially access sensitive banking
That’s not how it work. Having a rooted phone does not turn it into a digital farwest were every application can do anything. It becomes a permission like everything else; if you only grant it to safe stuff (like, for example, not granting root to a single app but using it to customize your phone through ADB), there’s not much to see here.
Because they want to “protect” you from “yourself”. Imagine, you could scrape your own data that you can already see.
I’d be really worried if the security of server operation for my bank depended on the client-side. But playing devils advocate, some people will most likely point out that a root exploit on a phone may be unintentional and used to spy on people, to which I answer:
Currently, option 2 is in effect, sadly.
I like being able to see my logs without waiting 20 minutes, knowing who started what without playing cat and mouse with random processes and being able to change something without going through multiple levels of merged configurations files from three different sources.
I also enjoy tools that were developed over decades and not rewritten from scratch reintroducing long-solved issues.
At this point, windows-only title that won’t work on Linux are overpriced cash grab with multiple layers of intrusive DRM that will try to wring you out for more money for a year before dropping the still unfinished thing off the support line.
Against the original joke, I’d recommend a samsung one, but their printer division has been bought by HP so…
Removed the libc by hand, and restored the system to a usable state without turning it off and putting the file back on the FS from external source.
And yet all of them indicates the actual cause of error. It’s nice to have a bit of fun sometimes.
I like the “encryption, but we have the keys” approach. Makes it very secure, especially since MS never had any security breach or leak, ever.