emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Konstantin Kliakhandler <kosta@slumpy.org>
To: emacs-orgmode@gnu.org
Subject: Why no secure code retrieval
Date: Tue, 28 Jun 2016 15:10:54 +0300	[thread overview]
Message-ID: <CAH+LVpme=JLA12+dWMjBsm+47niRJZFLvfmtJQ12NhPvOS8sUA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 779 bytes --]

Hello everyone,

I have continually been perplexed by the (apparent) lack of ways to
retrieve the code for org-mode in a secure fashion, but always thought that
I just haven't tried hard enough. Today it dawned on me that there probably
simply is no such way.

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). 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). Given this, is there a reason this is not
being done?

And if there is no reason, would it be possible to begin doing it, going
forward?

Thanks in advance for the consideration,
Kosta

[-- Attachment #2: Type: text/html, Size: 1022 bytes --]

             reply	other threads:[~2016-06-28 12:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 12:10 Konstantin Kliakhandler [this message]
2016-06-29  6:11 ` Why no secure code retrieval Arun Isaac
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

  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='CAH+LVpme=JLA12+dWMjBsm+47niRJZFLvfmtJQ12NhPvOS8sUA@mail.gmail.com' \
    --to=kosta@slumpy.org \
    --cc=emacs-orgmode@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/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).