Cybersecurity

6100 readers

245 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected]

Notable mention to [email protected]

founded 2 years ago

MODERATORS

[email protected]

Pumakit - Sophisticated Linux Rootkit That Persist Even After Reboots (gbhackers.com)

submitted 1 week ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 week ago

Thanks for the breakdown. I ofc use a root pwd different from my user PW (with sudo privileges) and often use appimages, as they don't require privileges at all to my understanding. I do run a few binaries though, as for example for team speak or corectl they are the only ones that work for me.

How would I go about restricting the files a program can access? Make a whole new user just for that program, put "run as this user" in the .desktop file an manually set read/write permissions for every single file on the system?

This seems unpractical. Is there a best practise guide? Do I need to get into apparmor and stuff?