From: Arun Isaac <arunisaac@systemreboot.net>
To: Konstantin Kliakhandler <kosta@slumpy.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Why no secure code retrieval
Date: Wed, 29 Jun 2016 11:41:22 +0530 [thread overview]
Message-ID: <87mvm4sewl.fsf@systemreboot.net> (raw)
In-Reply-To: <CAH+LVpme=JLA12+dWMjBsm+47niRJZFLvfmtJQ12NhPvOS8sUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
> However, gpg signing release tag commits is dead simple and would
> take a total of maybe 10 minutes of work over the lifetime of the project
> (please correct me if I'm wrong).
I second this statement. GPG signing sounds good to me. We should do this.
> I know that https can be a bit tedious to setup so I am not asking for it
> (though I do think it would be great if it was enabled on the site in some
> fashion).
HTTPS is not so tedious these days with Let's Encrypt.
https://letsencrypt.org/
We should set up HTTPS as well.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-06-29 6:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 12:10 Why no secure code retrieval Konstantin Kliakhandler
2016-06-29 6:11 ` Arun Isaac [this message]
2016-06-30 11:50 ` Nicolas Goaziou
2016-07-02 14:18 ` Bastien Guerry
2016-07-02 16:51 ` Ian Barton
2016-07-03 7:09 ` Bastien Guerry
2016-07-03 15:11 ` Robert Klein
2016-07-03 15:20 ` Achim Gratz
2016-07-03 16:57 ` Robert Horn
2016-07-03 18:18 ` Konstantin Kliakhandler
2016-07-03 18:25 ` Achim Gratz
2016-07-03 20:12 ` Robert Horn
2016-07-03 22:36 ` Konstantin Kliakhandler
2016-07-04 0:17 ` Robert Horn
2016-07-04 6:15 ` Konstantin Kliakhandler
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=87mvm4sewl.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=emacs-orgmode@gnu.org \
--cc=kosta@slumpy.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.