this post was submitted on 21 Mar 2026
43 points (95.7% liked)

Linux

63955 readers
1100 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

Related Communities

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

founded 6 years ago
MODERATORS
 

Hi, there!

Newbie question here: basically, the title. Perhaps what I'm asking is pretty obvious, but I'd like to double-check with the community on this.

I use Discover on my Debian KDE Plasma set-up, with Flatpaks enabled (but not Snaps). Sometimes, I come across apps (I did just yesterday, searching for translation apps to replace DeepL), that have according to its page, an unknown author and, sometimes, even an unkown licence, but which do require access permission to the whole system (this latter requirement applying specifically to Deb packages, from what I've seen).

Under these circumstances, is it safe to assume that such apps will still be safe because of the fact that they appear listed on Discover (in other words, is Discover a guarantee of safety for the apps it shows, as in, some type of checked or proved content), or should I still be wary of potentially malicious software included on it?

Thank you very much in advance :)

you are viewing a single comment's thread
view the rest of the comments
[–] Cekan14@lemmy.org 4 points 1 day ago (2 children)

Hi! Thank you for your reply. So, if I understood correctly, whenever I click on "Install from Debian/GNU Linux" on Discover I am getting software directly from Debian's repository (thus, a "repository" in the sense that it's a place where this software is stored and can be retrieved); same thing when clicking on "Install from Flathub" for a Flatpak from Flathub. This does seem like the safest approach in the sense that it's the less risky one and, if malware did slip through, such as the XZ backdoor, at least it would not have been due to a personal mistake of mine, but a general one which would've affected much more people too.

This, in turn, is different from APT, which is not Debian's repository, but Debian's package manager. So, technically, I could write "sudo apt install (anything)" to get any piece of software from Debian's repository indeed, but I could also use that command to get software from somewhere else also in the form of a Deb package but which would not have come from Debian itself.

Did I get this right?

Thanks a bunch.

[–] banazir@lemmy.ml 5 points 1 day ago (1 children)

It may be a lot to take in at first, but seems to me you've got it!

[–] Cekan14@lemmy.org 3 points 1 day ago (1 children)

Thanks to you all for helping me understand it :)

[–] ozymandias117@lemmy.world 2 points 1 day ago* (last edited 1 day ago)

Maybe to help, you can see where you've enabled "repositories" that APT can download from in /etc/apt/sources.list and /etc/apt/sources.list.d

As long as you haven't manually installed a .dpkg package, or manually modified it, they should be something like

deb.debian.org security.debian.org

Some things like Slack may try to add their own repositories down there

When you type "sudo apt install" it is allowed to install from any configured repos down there

[–] IsoKiero@sopuli.xyz 3 points 1 day ago

This, in turn, is different from APT, which is not Debian’s repository, but Debian’s package manager. So, technically, I could write “sudo apt install (anything)” to get any piece of software from Debian’s repository indeed, but I could also use that command to get software from somewhere else also in the form of a Deb package but which would not have come from Debian itself.

With apt (and discover which uses apt/dpkg at the background) you can install anything from repositories configured on your system. So, if you want to use apt to install packages not built by Debian team you'll need to add those repositories in your system, so they don't just appear out of nothing.

Some software vendors offers .deb packages you can install which then add their own repository on your system and then you can 'apt install' their product just like you would on native Debian software and the same upgrade process which keeps your system up to date will include that '3rd party' software as well. Also some offer instructions on how to add their repository manually, but with a downloaded .deb it might be a bit easier to add repository without really paying attention to it.

Spotify is one of the big vendors who have their own repository for Debian and Ubuntu and with Ubuntu there's "ppa" repositories, which are basically just random individuals offering their packages for everyone to use and they are generally not going trough the same scrutiny than official repositories.