From: Hartmut Goebel <h.goebel@goebel-consult.de>
To: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] gnu: Add acme-client.
Date: Fri, 2 Sep 2016 20:01:55 +0200 [thread overview]
Message-ID: <57C9BE93.7090206@goebel-consult.de> (raw)
In-Reply-To: <f1649dd9aafe811c930ddaca825dbffe82e20818.1472827750.git.leo@famulari.name>
[-- Attachment #1.1: Type: text/plain, Size: 1161 bytes --]
Am 02.09.2016 um 16:49 schrieb Leo Famulari:
> + (name "acme-client")
I strongly suggest using a different name, as this is *one* of many
implementations and it is not the "official" one.
> + (synopsis "Let's Encrypt client")
The synopsis should already state, this is *one* of the acme-clients.
Something like "Let's Encrypt client used as standard at OpenBSD" is
more meaningful.
> + (description "acme-client is a Let's Encrypt client implemented in C. It
> +uses a modular design, and attempts to secure itself by dropping privileges and
*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?
--
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Development
Goebel Consult, Landshut
http://www.goebel-consult.de
Blog:
http://www.goebel-consult.de/blog/filmgesprach-zu-201ecitizenfour201c-in-herrsching
Kolumne: http://www.cissp-gefluester.de/2010-06-adobe-und-der-maiszunsler
[-- Attachment #1.2: Type: text/html, Size: 2740 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2430 bytes --]
next prev parent reply other threads:[~2016-09-02 18:02 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 [this message]
2016-09-02 18:50 ` Leo Famulari
2016-09-02 18:58 ` Leo Famulari
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
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=57C9BE93.7090206@goebel-consult.de \
--to=h.goebel@goebel-consult.de \
--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).