From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: Bastien Guerry <bzg@gnu.org>,
emacs-orgmode@gnu.org, Konstantin Kliakhandler <kosta@slumpy.org>
Subject: Re: Why no secure code retrieval
Date: Thu, 30 Jun 2016 13:50:34 +0200 [thread overview]
Message-ID: <87y45m28vp.fsf@saiph.selenimh> (raw)
In-Reply-To: <87mvm4sewl.fsf@systemreboot.net> (Arun Isaac's message of "Wed, 29 Jun 2016 11:41:22 +0530")
Hello,
Arun Isaac <arunisaac@systemreboot.net> writes:
>> 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.
GPG signing tags is OK, but I wouldn't like to request every commit to
be signed.
>> 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.
It would be nice, indeed. I'm Cc'ing Bastien for his opinion on the
matter, and a possible step forward.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-06-30 11:50 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
2016-06-30 11:50 ` Nicolas Goaziou [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y45m28vp.fsf@saiph.selenimh \
--to=mail@nicolasgoaziou.fr \
--cc=arunisaac@systemreboot.net \
--cc=bzg@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).