From: "J.B. Nicholson" <jbn@forestfield.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Free software is not trusted software
Date: Wed, 16 Jan 2019 21:44:43 -0600 [thread overview]
Message-ID: <938ef1bb-bb7e-54c3-5043-2aeb5fa9509d@forestfield.org> (raw)
In-Reply-To: <c067bfed-570b-9185-4935-305e8d29d0fe@lyberta.net>
Lyberta wrote:
> Today the Internet is filled with malware that is free software:
>
> https://lyberta.net/articles/tech/free_sw_untrusted.html
The article doesn't make it clear to me what is malware in any of the
listed software. It seems to me that the saving grace of free software is
that one can remove the malware, run and distribute the rest of the code,
and retain full control over their computer. This takes effort but at least
we're allowed to do it.
The article points out that auditing matters and I concur -- there's no
substitute for auditing by someone one trusts. There's too much free
software for anyone to do this alone but collectively we can get more of
this done.
This is also why open source is not the enemy. Proprietary software is the
enemy. In fact the FSF has long published this in their older article on
how free software differs from open source:
From https://www.gnu.org/philosophy/free-software-for-freedom.html
> We don't think of the Open Source movement as an enemy. The enemy is
> proprietary software.
Proprietary software denies one the freedom to do the vetting that needs to
be done. Open source may make some indefensible claims about how effective
the open source development methodology is at reducing bugs and improving
software, but that's nowhere near distributing malware.
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2019-01-17 3:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 14:09 Free software is not trusted software Lyberta
2019-01-16 17:00 ` Todd Weaver
2019-01-16 20:07 ` Caleb Herbert
2019-01-16 22:21 ` bill-auger
2019-01-16 22:57 ` bill-auger
2019-01-16 23:12 ` Leah Rowe
2019-01-17 1:01 ` bill-auger
2019-01-17 10:52 ` Thomas Harding
2019-02-25 20:44 ` Taiidan
2019-02-26 0:15 ` overthefalls
2019-01-17 3:44 ` J.B. Nicholson [this message]
2019-01-19 10:41 ` Nicolás Ortega Froysa
2019-01-19 14:34 ` Julian Daich
2019-01-20 18:01 ` Nicolás Ortega Froysa
2019-01-20 20:36 ` bill-auger
2019-01-20 22:54 ` Julian Daich
2019-01-21 3:02 ` bill-auger
2019-01-22 10:07 ` Nicolás Ortega Froysa
2019-01-23 3:48 ` bill-auger
2019-01-26 21:17 ` Julian Daich
2019-01-26 23:35 ` bill-auger
2019-01-27 1:07 ` bill-auger
2019-01-27 19:51 ` Julian Daich
2019-01-28 3:15 ` bill-auger
2019-01-27 19:40 ` Julian Daich
2019-02-17 5:34 ` overthefalls
2019-01-21 8:05 ` Andrew Luke Nesbit
2019-01-21 22:45 ` bill-auger
2019-01-22 9:34 ` Nicolás Ortega Froysa
2019-01-19 22:01 ` bill-auger
2019-01-20 18:06 ` Nicolás Ortega Froysa
2019-01-19 22:37 ` al3xu5 / dotcommon
2019-01-20 17:09 ` Lyberta
2019-01-20 18:16 ` Nicolás Ortega Froysa
2019-01-23 19:51 ` Adonay Felipe Nogueira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=938ef1bb-bb7e-54c3-5043-2aeb5fa9509d@forestfield.org \
--to=jbn@forestfield.org \
--cc=libreplanet-discuss@libreplanet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).