So, really the issue is you expect KDE to present it in UI which is not the case.
You would have to use the control binary to stop it from running (akonadictl stop).
To prevent it from running in the future, you’d have to edit/create it’s configuration in $HOME/.config and add something like StartServer=false to [].
There is no way to do this in the UI.
This really isn’t a technical issue, it’s more an estate planning issue. The basic concern is if you die, everyone gets locked out. That is where a will, safety deposit box, and named executor come into play.
Whatever credentials and guides needed can be safely stored and upon death that will activates and the executor hands over the access to whoever you are needing. The safest assumption to make in these scenarios isn’t that someone won’t know how to access the information, it’s that they won’t even know that information exists.
You also have to remember that there is a lot of things to do after someone dies and that these people would also be mourning. So, with that consideration in mind, try to make the process as seamless as possible. Off-loading to an executor of the estate (someone who is not family) also lets those people close to you mourn without having that final burden.
This is a fair question to ask given recent events. I don’t run Fedora currently, so others could probably give a much more exact answer, but from what I understand of it:
Bazzite is built on top of Fedora with uBlue. To compromise one of the packages, the attacker would have to bypass the Fedora enterprise team who are rage filled roid-driven experts who don’t take kindly to that sort of thing. They heavily secure their stuff. Even if an attack was successful, it would have little lasting effect because of immutability and having access to easy rollbacks.
It’s not impossible (like somehow stealing Bazzite’s keys), but it’s incredibly unlikely. AUR/NPM package sketchiness is not anywhere on the same level as compromising Fedora’s keys.
14-day free trial, then €4.99/month. No credit card required.
Just because I ads, here is a straight-forward guide to setting up Grafana and Prometheus to do this exact thing and without any monthly charge: https://medium.com/@achanandhi.m/how-to-monitor-a-linux-host-using-prometheus-node-exporter-and-grafana-3c1d259c22e5
You already ruled out Tailscale and the internal network and potentially the route taken to each your router. Does your router run any services that perform IDS/IPS maybe? Any sort of packet filtering on the external interface?
IMEI. You really would make an awful criminal lol.
Yes it is easy to find you. No, it is not hard to track someone just moving it.
I mean that’s just cinnamon with a debian backend instead of the regular ubuntu.
But Bonzai Buddy was my friend! He wouldn’t do those things to me! He cared!
4G/5G cellular? So, in some ways you’re actually easier to find. Your cell gateway is connecting to a tower which is logged and includes cell strength metrics. That gets compared to other towers and via trilateralization your location is determined.
Again, going back to what I previously said: there is a path back to you even if only for either billing or connectivity purposes.
Ok, this I can answer personally as we did multiple cases of this happening (CSAM, bomb threats, etc) at work.
So, anonymity on the Internet is not actually a thing. Whether its an IP address or telecom switch or whatever, there is a path back to you even if only for either billing or connectivity purposes. So, for IP, we would receive a subpoena signed by a judge to hand over any and all information regarding the identify of the a given IP address (they include a long list of things whether applicable or not in the order so every potential base is covered). Once legal was able to review and handed it off to us, we take that and look at the DHCP logs to see that on a given date at a given time that the IP address was assigned as part of shelf A / slot B / port C. That shelf/slot/port combination is tied physically to an address/account. We provide the relevant logs and personal information of that user to law enforcement.
For bomb threats over the phone, telecom switches love to tell every other telecom switch who they are (again, connectivity purposes). So, when you make a call to a business/school doing that, their PBX is going to log to the millisecond when that call occurred and who the switch was. Again, subpoena and we pull the SIP logs. We can even provide the RTP/RTCP packets and reconstruct the phone call audio if the subpoena asks for that.
You can just look at the testimonies from others who have run exit nodes. The cost of your “free” VPN is that law enforcement will constantly be in contact and investigating you because your network/machine is being used to download CSAM.
There is no “oh don’t worry, A.B.C.D is just a tor node, we can give it a pass”. Every time that happens, it has to be treated with a full investigation.
I think 10% self-promotion is a very fair rule. It enforces the idea that if you are going to take from the community that you also give something back.
As someone who is partially self-hosted, I think that will help keep ads from muddying the waters when I’m searching posts for setup suggestions.
It would be like running TOR, but not a relay, it would be like an exit node.
That should be enough to warn anyone away from using them.
So, it’s like Grindr for crypto bros? Nostr is a sex thing, right?
EDIT: I’m not judging. Love is love.
You mention crappy security practices from the ISP but then mention the user’s action (installing “free” VPNs). Why is the ISP on the hook for the user making terrible decisions?
What is the correct security practice in that instance? Fire the customer for being an idiot? Maybe just DENY IP ANY ANY on outbound traffic?
How do you protect somebody who is intent on running themselves off a cliff?
I worked as a network analyst for a provider for several years and during that time I’d say ~90% of the issue stemmed from sketchy apps/services that the user loaded from their end.
A lot of “free” VPN services will basically allow bad actors (the paid tier) to use your connection. A lot of IoT devices are also just openly available on the Internet to route through.
From the ISP perspective, we managed the roads, not your car. There is a push to blame the ISP as it’s their network, but realistically how are they meant to provide security (in the context that is being asked) to any device that gets plugged into that network? We even had business customers demand we add clauses to contracts where we would accept responsibility for any malware they sent between sites over an MPLS setup.
In the end, a lot of people seem to want this impossible scenario of the ISP managing security for them but also not inspecting their traffic.
At it’s heart, this is what @selfhosted is meant for:
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
I would say that members talking about paid/closed products they use (ex. “I connect to this via Tailscale” or “I use company ABC for hosted VPS”) to accomplish something is fine, but marketing or job boarding (ex. “Looking for QA on my commercial product”) is not.
Self-Hosted isn’t a job board, though. If you’re going to post job listings, there are better places to do that.
Yeah, he needs to use named keys to make that work.