taskManeage - Tasks: task #15696, Security warning at the start of...


You are not allowed to post comments on this tracker with your current authentication level.

task #15696: Security warning at the start of Maneage

Submitter:  Mohammad Akhlaghi <makhlaghi>
Submitted:  Wed 17 Jun 2020 02:42:43 AM UTC
Should Start On:  Tue 16 Jun 2020 11:00:00 PM UTC Should be Finished on:  Tue 16 Jun 2020 11:00:00 PM UTC
Category:  Software Priority:  5 - Normal
Status:  Postponed Privacy:  Public
Assigned to:  None Percent Complete:  0%
Open/Closed:  Open Effort:  0.00

Wed 17 Jun 2020 03:07:41 PM UTC, comment #1: 

The example of a trojan that you give is a good reminder of what we can do as counterarguments when we are pressured to install non-free software, or even worse, non-free binaries, on our computers. As you point out, it's trival to insert a trojan in code.

Free-licensed code tends to be safer, because it's more likely, though not guaranteed, that people notice security flaws.

Free-licensed code in a git repository by identified scientists from your own scientific community tends to be even safer, because the dangerous part of the code would be traceable in the git history, and if it became clear that the flaw were deliberate, then that would be quite bad for the author's reputation. There's also no motivation for scientists to do this, where your informal scientific reputation is de facto important, even if it doesn't count in bibliometry.

Regarding the text of the warning, shifting the source URLs to a single file will be useful in this context - see https://savannah.nongnu.org/task/?15686 . Once this is done, we should recommend that the user browse through the list of URLs and make a judgment regarding how much s/he trusts those URLs to provide secure software.

There are several overlapping en.Wikipedia pages describing various forms of trust networks for software/computing/internet:


Debian effectively has a trust network in the sense of multiple pipelines for submitting software updates, a formally developed trust network of Debian Developers, together with bug reports and so on, plus a dedicated security team.

This suggests one way of increasing security, which will be easier when 15686 is implemented, which will be to have an option to preferentially use GNU and Debian sources as much as possible: so rather than strictly upstream sources, these will be quality controlled versions.

Boud Roukema <boud>
Group Member
Wed 17 Jun 2020 02:42:43 AM UTC, original submission:  

We try our best to keep the core Maneage project as secure as possible. The fact that it doesn't require root permissions is one such example.

However, we cannot make any promises for projects that are derived from Maneage! For example a malicious project author may put steps deep in their own project scripts that extract a user's private SSH keys (or other private data) and use a network connection to send it somewhere.

Therefore it is very important the users understand this major security implications and take the proper precautions if they don't trust the derived project's creator.

For example one option is build a new user for the "Maneaged" project and run the project in that user account, or to run it in a Docker container (task #15389) or to create a virtual machine and run it there.

This task was defined during the more specific discussion of task #15694.

Mohammad Akhlaghi <makhlaghi>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by boud (Posted a comment)
  • -email is unavailable- added by makhlaghi (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-b921.
    Corresponding source code