this post was submitted on 18 Oct 2023
310 points (93.3% liked)
Privacy
40709 readers
719 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't use Windows but if you install a program that requires a service on Linux, the service will be written to your system's services daemon awaiting your activation. I don't see what the issue with that is.
What's to stop the installer on Linux from configuring the service such that the service always runs on boot? e.g.
systemctl enable malware.service
.Linux doesn't have "installers" as Linux uses package managers. The only way you can get malware is if you manually add a bad repo.
So it doesn't really matter in the long run
Are you really serious making this claim? lol.
Yes, prove me wrong. As long as your running a up to date system there shouldn't be anything that could be easily compromised.
I've been using Linux (and UNIX) professionally since the kernel version started with a "1." I have no need to try to prove anything to you. Linux has installers other than just those invoked by a package manager, and it is laughable that you claim otherwise.
You still need to manually enable the service. The configuration of the service has zero effect on its activation or lifecycle.
Huh? Any script can create a service, enable it and then start it. What would make you think the brave package (or just the application itself) can't do this?
Not possible to start or enable a created service without user intervention. You don't know what you are talking about.
Bruh you just ran the command to enable the 'written' service. Comprehension is a problem in this community.
Read my argument again.
OK.. challenge accepted. Maybe you don't know about systemd user services.
Content of
mytrojan.sh
:Content of
myscript.sh
:Now run the script (
mytrojan.sh
) and check service status after that:You failed. This requires the user to run a script aka manual intervention.
Now imagine that the script is set to run as part of the brave installation - you type "yes" please download brave, brave installs brave and runs this script. Linux isn't immune to malware as you seem to think.
You would need the power of root to do all these aforementioned things (run a VPN service).
And am not saying that Linux is immune to malware, just that it's not out of the norm to have package managers install services crucial for operation during installation. Since Windows doesn't have package managers, I'm gonna replace package managers with packages in this reasoning.
I thought that you only were ignorant, but no, you're more than that!
Maybe am ignorant but at least I understand the questions before I answer them.
Systemd "enabled" services are literal symlinks... whenever a target runs, it tries to start also all the service files on its "wants" directory.
You can literally enable any service for next boot by making a symlink in
/etc/systemd/system/multi-user.target.wants/
(or whichever other target you want it to run on) as root (and installation scripts are run as root).This is actually very close (just tested and confirmed it). I somehow stand corrected about requiring manual enablement but this is just using the package manager to do the dirty work for you.
However the program itself cannot write into those directories without root permissions. You still have to allow your package manager to do this with root permissions as mentioned.