unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: server and client in one package -> security issue
Date: Tue, 14 Feb 2017 11:44:30 +0100	[thread overview]
Message-ID: <58A2DF8E.3040902@crazy-compilers.com> (raw)
In-Reply-To: <20170214101651.068fb59a@scratchpost.org>

Am 14.02.2017 um 10:16 schrieb Danny Milosavljevic:
> I don't think Guix should do that, though. 

I think guix should provide the tools for doing so. Guix has the big
advantage of providing trustworthy packages, but kicks itself out of the
race if hardening is so much complicated.

> IMO locking down everything for users is basically the antithesis of the FSF.

The "user" is the company, the employees work on behalf of the company.
So the software freedom has to be available toe the company not to the
individual employee.

As a company I'm expecting the user to *not* install software on their
computers (not talking about developers here). Otherwise its like
allowing workers to bring their own hammer to the building site or their
own machines into the factory building. If the hammer is inappropriate
and is deforming all nails, or the machine is producing scrap, the
company the the one bear the consequences.


-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

  parent reply	other threads:[~2017-02-14 10:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 20:43 Add murmur contact.ng0
2017-02-01 20:43 ` [PATCH] gnu: mumble: Add 'murmur' output contact.ng0
2017-02-01 21:15 ` Add murmur ng0
2017-02-09 16:50 ` Ludovic Courtès
2017-02-09 18:20   ` ng0
2017-02-09 22:50     ` Ludovic Courtès
2017-02-10 21:39       ` ng0
2017-02-10 21:54         ` Marius Bakke
2017-02-10 22:15           ` ng0
2017-02-11 14:31             ` Ludovic Courtès
2017-02-11 14:39               ` ng0
2017-02-12 13:37                 ` Ludovic Courtès
2017-02-12 13:53                   ` ng0
2017-02-12 13:57                     ` David Craven
2017-02-12 14:02                       ` ng0
2017-02-12 14:37                         ` David Craven
2017-02-12 17:01                           ` Hartmut Goebel
2017-02-12 17:42                             ` pelzflorian (Florian Pelz)
2017-02-13 14:15                               ` Ludovic Courtès
2017-02-12 17:54                             ` David Craven
2017-02-14 10:13                               ` Hartmut Goebel
2017-02-14  9:00                   ` ng0
2017-02-12 12:23       ` server and client in one package -> security issue (was: Add murmur) Hartmut Goebel
2017-02-12 12:31         ` ng0
2017-02-12 12:53           ` David Craven
2017-02-12 16:52             ` server and client in one package -> security issue Hartmut Goebel
2017-02-13 14:13         ` Ludovic Courtès
2017-02-14 10:28           ` Hartmut Goebel
2017-02-14 11:19             ` Andy Wingo
2017-02-14  9:16         ` server and client in one package -> security issue (was: Add murmur) Danny Milosavljevic
2017-02-14  9:51           ` ng0
2017-02-14 10:44           ` Hartmut Goebel [this message]
2017-04-24  7:01             ` server and client in one package -> security issue Maxim Cournoyer

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58A2DF8E.3040902@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).