Linux

48144 readers

733 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

[email protected]

Installies, a site for managing, organizing, and retrieving shell scripts for installing things on Linux and Unix-based operating systems. (installies.org)

submitted 11 months ago by [email protected] to c/[email protected]

18 comments fedilink hide all child comments

Hi, for the past few months I have been working on my website Installies. It is a site for managing, organizing, and retrieving shell scripts for use to install, remove, update or compile apps on Linux and Unix-based systems.

You might be asking why can't you just use your system's built-in package manager. While that will work for most apps there might be some problems with others:

Some apps might not be on your system's package manager. This would make it so you might have to compile the app, which might be difficult for newer Linux users.
Apps you have to run through wine generally are not in package manager's repositories. They also might need extra libraries that might be complicated to install.
There might be some weirder software that isn't really an app, or is not traditionally installed on your computer e.g. TempleOS in a VM.
Some apps have different packages for similar versions of the app, so a script that lets you choose between all the options would make it easier to decide which one to install, such as QEMU.

As for script security, Installies has a voting and reporting system to help make sure that scripts are safe.

There are some design choices I am yet to make, so I would like your guy's input. One of them is if app maintainers should be able to stop non-maintainers from creating scripts on apps. Please comment what you think (also any other feedback).

Future Plans

Utility Scripts: General purpose shell scripts.
CLI: This will allow for a universal interface to install things on Linux. It will also allow for easier use of Installies on servers.
Collaboration: Allowing multiple people to directly contribute to scripts without being a maintainer.
User ranking system: A system to rank users by how popular their scripts. This will make it easier for users to judge if a script is good without having to analyze the source.

As it is in beta, there will be many bugs. If you find any bugs please report them on the GitHub. Feedback and feature requests are also welcome.

Happy Scripting!

Links

Site: https://installies.org
Docs: https://docs.installies.org
Source: https://github.com/Berserkware/installies

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

[–] [email protected] 5 points 11 months ago (1 children)

I wholeheartedly agree, yet this is the same for stuff like the AUR, every PPA, or even just blindly copy & pasting inductions from some blog - all of which are very popular. (Just to name some examples that are closer to what op wants to do).

I still wouldn't use scripts from a random dump site because they are just likely to mess up the os with junk and cruft that will be there forever. But fundamentally from a security point of few its not necessarily worse than what many are doing - simply because it doesn't get worse than blindly executing stuff from sources missing the reputation to justify trusting them.

[–] [email protected] 3 points 11 months ago (1 children)

Yup, there is a lot of prior art on how to get this wrong :(, and I dont know of any good solutions either. Curation and moderation are probably the best case, but arent bulletproof either.

I raised this not to kill OPs project, but to make sure they go into it eyes open. I personally would be very uncomfortable if my website was being abused to distribute malware, so they deserve to at least be aware of the risks.

[–] [email protected] 2 points 11 months ago* (last edited 11 months ago)

I think one puzzle piece of improvement is flatpak:

It has a verification system, such that users can see which apps are packaged by their developers. For those apps, this eliminates the need to trust a separate maintainer entirely
It targets almost all linux distributions with a single package. This cuts down the packaging effort for covering the majority of the linux landscape so much, that the number of package maintainers required to be trusted collapses - in the ideal case to just the developers themselves as in the first bullet point
It makes use of sandboxing, so in case of a malicious app it (in theory) only has access to the stuff the user gave it permission to.

In reality there's a plethora of problems obviously:

verified apps are the minority
some people don't like the additional storage needed for runtimes (although the more flatpaks you use the more runtimes can be shared and its overall impact gets smaller)
A lot of apps do not yet use all the portals, and require the classical full access to the system to work properly (in some cases the user can still remove some permission if certain features of the application are not needed by them though). This is just a question of ongoing development work, and hopefully we reach a point in the near future where a flatpak app without tied down permissions raises eyebrows