From: eli-schwartz <eli-schwartz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC/POC] Support checks for signify signature inside xbps-src
Date: Tue, 02 Feb 2021 21:29:41 +0100 [thread overview]
Message-ID: <20210202202941.Hvn9gz_E7MSOs2xE2BC3ddA27PehqTTNfapg2iASUDI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28400@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]
New comment by eli-schwartz on void-packages repository
https://github.com/void-linux/void-packages/pull/28400#issuecomment-771959898
Comment:
> If crypto system only considers happy path it's not that useful.
It considers both the happy path and the unhappy path.
It considers the happy path by saying "yay, let's be happy".
It considers the unhappy path by saying "oh no, looks like you're going to feel unhappy now".
I don't see the problem here.
- Are you optimizing for "I just want to package something, anything, that people put in front of me, and this will stop me from doing so"?
- Are you optimizing for "I want to make sure I'm packaging the right stuff, and not packaging the wrong stuff, and this will help me tell the difference"?
Do you have a reasonable expectation that people are going to be losing their security tokens, not have them securely backed up (e.g. printout in a safe or bank deposit box), and then be unable to be contacted IRL to provide legal evidence of ID connecting an old security token to a new security token?
If the Void repos suddenly lost the private key used to sign repodata, what would you do?
If a Void team member suddenly lost their github login and showed up the next day with a new account e.g. @Chocimier2 and insisted "yes I am the same person, please believe me and add me to the github org with push rights", what is your ideal proposed mechanism to verify the truthfulness of this statement?
next prev parent reply other threads:[~2021-02-02 20:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 2:37 [PR PATCH] " ericonr
2021-02-02 2:48 ` [PR PATCH] [Updated] " ericonr
2021-02-02 3:53 ` eli-schwartz
2021-02-02 18:42 ` Chocimier
2021-02-02 18:45 ` eli-schwartz
2021-02-02 18:48 ` Chocimier
2021-02-02 18:50 ` ericonr
2021-02-02 18:52 ` Chocimier
2021-02-02 18:53 ` Chocimier
2021-02-02 19:04 ` eli-schwartz
2021-02-02 19:05 ` ericonr
2021-02-02 20:04 ` Chocimier
2021-02-02 20:29 ` eli-schwartz [this message]
2021-02-02 20:55 ` Chocimier
2021-02-03 15:14 ` [PR PATCH] [Updated] " ericonr
2022-05-03 2:14 ` github-actions
2022-05-17 2:14 ` [PR PATCH] [Closed]: " github-actions
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=20210202202941.Hvn9gz_E7MSOs2xE2BC3ddA27PehqTTNfapg2iASUDI@z \
--to=eli-schwartz@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).