Linux

1259 readers

77 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

How to create a sandbox folder, restricting write access to all files contained in it to that folder itself? (lemmy.kde.social)

submitted 1 year ago* (last edited 1 year ago) by tubbadu@lemmy.kde.social to c/linux@lemmy.ml

5 comments fedilink hide all child comments

Hello! Let's say I have an executable file, but I'm unsure of the source, and may contain bugs/errors/malwares/bad things that can mess up my machine. I want to execute it anyway, but I want to make sure that it does not mess things up. Is it possible to create a "sandbox" folder, place the executable inside it, and then give all files inside that folder only write privileges inside that folder, and not outside? so that echo "hello" >> log.txt would work, but echo "hello" >> ~/log.txt would not?

EDIT: thanks to everyone for the answers! I decided to opt for a VM to minimize the risk, but chroot is probably a faster solution for not-so-dangerous files

top 3 comments

sorted by: hot top controversial new old

[–] spencer@lemmy.ca 5 points 1 year ago

Depending on what level of malware you’re worried about, running it in a Docker container could be a solution.

[–] reggie@lemmy.fmhy.ml 2 points 1 year ago* (last edited 1 year ago)

To be completely safe I'd just use a VM, if you think that is an overkill then I suggest Bubblewrap.

[–] dlarge6510@lemm.ee 2 points 1 year ago

Look up chroot

load more comments