291–300 of 391 posts
What I want is Little Snitch on steroids built into the OS where every process, including all native ones, including UI apps, are blocked from network connectivity by default, and the user gets an easy monitor of outgoing traffic with TLS/SSL inspection built in (you'd need some OS API to enable that). Kind of like granular oauth permissions, apps should have to declare which outgoing they have, a description/why, an…
Earlier quoted context omitted.
On Linux there is OpenSnitch that does its job nicely, although I experienced some occasional desktop slowdowns even after training it to open everything for trusted programs. https://github.com/evilsocket/opensnitch I still recall the old days of Windows when I tried Kerio Personal Firewall and realized how much software already phoned home two decades ago. That was the last wake up call that pushed me into getting…
Keep in mind, OpenSnitch is Linux-based and none of Linux firewalls can filter incoming packets by process ID like macOS/FreeBSD (Lil'Snitch) can.
Does it beam home? Yes Do I like it? No
We have LibreOffice for decades. Be the change.
Earlier quoted context omitted.
What I want is Little Snitch on steroids built into the OS where every process, You cannot trust an OS you cannot build yourself. That's why I see Linux as the only option for professionals and privacy minded people.
In fact, you cannot trust an OS you DIDN'T build yourself. And there are only two of those: Linux from scratch and Gentoo.
... with a compiler you wrote yourself. In assem-- uh, in hexade... no. With toggle switches.
What I want is Little Snitch on steroids built into the OS where every process, including all native ones, including UI apps, are blocked from network connectivity by default, and the user gets an easy monitor of outgoing traffic with TLS/SSL inspection built in (you'd need some OS API to enable that). Kind of like granular oauth permissions, apps should have to declare which outgoing they have, a description/why, an…
Just like PayPal. There's a table you can bring up that lists everyone you ever engaged with on paypal for recurring pricing, and deactivate them.
I've wanted exactly what you describe for years. Little Snitch taught me that there's just too much data that isn't organized properly. Even if you get down to the app level (like PowerPoint), it is still transceiving a lot of data. How do you tell what is necessary and what is dubious telemetry?
Earlier quoted context omitted.
What happened in 2014? Also someone told me here that LS should be considered harmful.
It's complicated, but the 2013-2014 years were when the bulk of the Snowden leaks were hitting the internet, and people were starting to dig up really suspicious stuff relating to all big tech companies, not just Apple. However, Apple was still among the companies compliant with PRISM, the NSA's newly established surveillance/tracking effort that also roped in Microsoft, Google, AOL and any other major service provid…
Paint: having Admin rights when you can find it since Windows 95
There's a pervasive lack of precision in privacy discussions. There's a difference between a network request that does some computation on the server side, one that does the same but may log errors and increment counters, and one that actually stores the data temporarily or for a long time. And in the last case, there's a difference between the data being nigh-impossible for internal employees to access (perhaps only…
This seems like less of a "precision" issue and more of a "transparency and accountability" issue. Do you know how long this information is stored by Microsoft? Where it is stored? Who has access? What the process is for requesting that data is deleted or even for opting-out of it's collection? An opt-in prompt is a great place for organizations to provide access to resources that answer these questions.
When we don't have the answers to the questions, (or don't trust the organization providing the answers to be truthful), we should assume the worst case, not the best as you seem to be implying.
> And asking the user to consent for every little thing isn't the solution either.
Prompts/permission can have varying and nested levels of granularity. This is absolutely not an excuse for not providing opt-in for data collection. (Edit: E.G. You can simply ask "Allow Us to Collect Data: Always, Never, Sometimes" and then you only need to show additional prompts if they select "Sometimes". If you are seeing to many people saying "Never" then you can do a better job of explaining the benefits/features, but you can't just ethically ignore the wishes of the user.)
I see no problem with organizations pre-deciding this for their employees, (thus no need for a prompt), but this doesn't remove the need for individuals and members of less organized organizations to have the ability to not have their data collected.