all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Hartmut Goebel <h.goebel@goebel-consult.de>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] gnu: Add acme-client.
Date: Fri, 2 Sep 2016 14:58:27 -0400	[thread overview]
Message-ID: <20160902185827.GA31989@jasmine> (raw)
In-Reply-To: <20160902185028.GB31756@jasmine>

On Fri, Sep 02, 2016 at 02:50:28PM -0400, Leo Famulari wrote:
> > *shiver* Why would one implement this in an language like C, which is
> > prone to buffer overflows, if there are implementations available in
> > more secure languages?
> 
> I wouldn't propose this package if it wasn't part of OpenBSD's base
> system:
> 
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/acme-client/

To clarify my statement, I think the OpenBSD project has a reputation
for writing good C. Also they design software to fail safely, by
designing privilege separation into their tools, inventing and using
pledge(2), etc.

This portable version of the software only gets some of those benefits,
but it does get some of them.

That's I didn't propose this package until I saw that it had been
reviewed and adopted by OpenBSD.

  reply	other threads:[~2016-09-02 18:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 14:49 [PATCH 0/1] Another Let's Encrypt client Leo Famulari
2016-09-02 14:49 ` [PATCH 1/1] gnu: Add acme-client Leo Famulari
2016-09-02 18:01   ` Hartmut Goebel
2016-09-02 18:50     ` Leo Famulari
2016-09-02 18:58       ` Leo Famulari [this message]
2016-09-03  7:43       ` Hartmut Goebel
2016-09-03 10:04       ` Andreas Enge
2016-09-03 10:32         ` Marius Bakke
2016-09-04  2:43           ` Leo Famulari
2016-09-04  5:12             ` Marius Bakke
2016-09-04  2:29         ` Leo Famulari
2016-09-11 12:42           ` Andreas Enge
2016-09-11 12:57             ` Hartmut Goebel
2016-09-12 17:06   ` Leo Famulari

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

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

  git send-email \
    --in-reply-to=20160902185827.GA31989@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@goebel-consult.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.