From: Hongli Lai <hongli@phusion.nl>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Signing the gem with a PGP key
Date: Tue, 12 Mar 2013 00:10:52 +0100 [thread overview]
Message-ID: <CAM3ce8HGq+MMVUVK624mcO6caaBMDE=NnLWLRL8TA8vgpOZ1Jg@mail.gmail.com> (raw)
In-Reply-To: <20130311224812.GA26407@dcvr.yhbt.net>
On Mon, Mar 11, 2013 at 11:48 PM, Eric Wong <normalperson@yhbt.net> wrote:
> Can we designate gems be signed by a trusted third party (e.g. you?)
> That's how Debian (and presumably other OS distros work).
>
> _Nobody_ should trust me. I have and maintain zero credibility.
> The only credibility any unicorn has is what its users give it.
Well the kind of trust we're talking about here is not trustworthiness
(i.e. "does the software work well and will it refrain from formatting
my harddisk?"), but authenticity ("is this gem made by the Unicorn and
not someone pretending to be him?"). Given that definition of "trust",
having a third party sign the gem is not very useful, and letting you
sign the gem will not make it a statement about trustworthiness,
warranty or credibility.
What do you think?
--
Phusion | Ruby & Rails deployment, scaling and tuning solutions
Web: http://www.phusion.nl/
E-mail: info@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2013-03-11 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 19:57 Signing the gem with a PGP key Hongli Lai
2013-03-11 22:48 ` Eric Wong
2013-03-11 23:10 ` Hongli Lai [this message]
2013-03-11 23:59 ` Eric Wong
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://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM3ce8HGq+MMVUVK624mcO6caaBMDE=NnLWLRL8TA8vgpOZ1Jg@mail.gmail.com' \
--to=hongli@phusion.nl \
--cc=mongrel-unicorn@rubyforge.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://yhbt.net/unicorn.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).