public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tobias Klausmann <klausman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Gentoo and Root CAs
Date: Mon, 31 Dec 2012 15:42:39 +0100	[thread overview]
Message-ID: <20121231144238.GA86695@kaini.schwarzvogel.de> (raw)

Hey,

Ryan Sleevi, who's working on Chromium and is familiar with other
project's Root Cert programs has written an article on how he
perceives assorted distributions handle Root CAs:

https://plus.google.com/u/0/105761279104103278252/posts/eVdB6X3NpPg

"""
[...]
Debian: From [5]. According to README.debian, to get a CA
included, all you need is two or three people to support you.

Gentoo: From [6] Same as Debian. Note they also modify other
packages (such as dev-libs/nss) to inject root certs into other
programs' root stores.
[...]
References:
[5] http://packages.debian.org/squeeze/all/ca-certificates
[6] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-misc/ca-certificates/
"""

Now before you reply, RTFA. Also note that while my own opinion
on the matter is irrelevant, I _do_ think that his concerns need
to be addressed, particularly the second half of his statement.


Regards,
Tobias


             reply	other threads:[~2012-12-31 14:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-31 14:42 Tobias Klausmann [this message]
2012-12-31 15:06 ` [gentoo-dev] Gentoo and Root CAs Kevin Chadwick
2013-01-01  0:44 ` Rich Freeman
2013-01-01 10:51   ` Dirkjan Ochtman
2013-01-01 12:48     ` Rich Freeman
2013-01-01 15:28     ` Michael Mol
2013-01-02  2:37       ` [gentoo-dev] " Benjamin Peterson
2013-01-02  2:49         ` Michael Mol
2013-01-02  3:09           ` Rich Freeman
2013-01-01 18:32     ` [gentoo-dev] " "Paweł Hajdan, Jr."
2013-01-02  3:23   ` Mike Frysinger

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=20121231144238.GA86695@kaini.schwarzvogel.de \
    --to=klausman@gentoo.org \
    --cc=gentoo-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