public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Schleizer <patrick-mailinglists@whonix.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Security and Comparison of Portage with other Package Managers
Date: Sun, 08 Mar 2015 14:59:28 +0000	[thread overview]
Message-ID: <54FC63D0.2000108@whonix.org> (raw)
In-Reply-To: <54FB8922.90408@gentoo.org>

Zac Medico:
> On 03/06/2015 09:50 AM, Mark Kubacki wrote:
>> We're on the same side here.
>>
>> Do we have numbers showing the ratio "portage used with defaults" vs.
>> where "[webrsync-gpg] is described in many hardening guides for gentoo
>> and widely used among the security conscious" applies?
>>
>> DNS not being encrypted is just painting the whole picture. Point is,
>> the default is that "emerge --sync" results in a transfer using RSYNC
>> (or http).
>>
>> And by default you cannot compare the result with any authoritative source.
>>
> 
> Ideally, we can rely on security mechanisms built into git [1], possibly
> involving signed commits.
> 
> [1] https://github.com/gentoo/gentoo-portage-rsync-mirror

Then the question is, how secure are signatures when used wit hgit?

A while ago I wrote a blog post asking that question, referencing a lot
related information, started a discussion and also posted this on the
git mailing list.

"How safe are signed git tags? Only as safe as SHA-1 or somehow safer?"
[1] [2]

Cheers,
Patrick

[1]
https://www.whonix.org/blog/how-safe-are-signed-git-tags-only-as-safe-as-sha-1-or-somehow-safer
[2] http://www.mail-archive.com/git@vger.kernel.org/msg61087.html



  parent reply	other threads:[~2015-03-08 14:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 14:49 [gentoo-portage-dev] Security and Comparison of Portage with other Package Managers Patrick Schleizer
2015-03-05 15:30 ` Rick "Zero_Chaos" Farina
2015-03-05 19:14   ` Patrick Schleizer
2015-03-06  0:56     ` Rick "Zero_Chaos" Farina
2015-03-06 13:53       ` Mark Kubacki
2015-03-06 15:20         ` Rick "Zero_Chaos" Farina
2015-03-06 16:13           ` Brian Dolbec
2015-03-06 17:50           ` Mark Kubacki
2015-03-07 23:26             ` Zac Medico
2015-03-08  1:24               ` Brian Dolbec
2015-03-08  2:31                 ` Zac Medico
2015-03-08  5:44                   ` Brian Dolbec
2015-03-08 14:59               ` Patrick Schleizer [this message]
2015-03-08 20:10                 ` Zac Medico
2015-03-08 15:02               ` Mark Kubacki
2015-03-08 21:02                 ` Zac Medico
2015-03-06 15:43 ` Patrick Schleizer

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=54FC63D0.2000108@whonix.org \
    --to=patrick-mailinglists@whonix.org \
    --cc=gentoo-portage-dev@lists.gentoo.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