public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: From where the word 'gentoo' came?
Date: Wed, 21 Dec 2011 19:50:24 +0200	[thread overview]
Message-ID: <jct68i$t3b$1@dough.gmane.org> (raw)
In-Reply-To: <CAOTuDKonLJw4w0Z79Nvp7HOA8xp=Xbq9h5sXWqhhZUrKHDeF0A@mail.gmail.com>

On 12/21/2011 04:59 PM, Joshua Murphy wrote:
> On Wed, Dec 21, 2011 at 7:32 AM, LinuxIsOne<reallife@hmamail.com>  wrote:
>> On Wed, Dec 21, 2011 at 5:58 PM, Daniel Troeder<daniel@admin-box.com>  wrote:
>>
>>> Also (ir)relevant: bug report concerning the mascot Larry the cow:
>>> https://bugs.gentoo.org/show_bug.cgi?id=27727
>>
>> But your links shows untrusted connection in my browser!
>>
>
> That would likely be because cacert.org isn't a "trusted' authority by
> default and that is the issuer for B.G.O., making the certificate
> throw up a red flag if you choose not to add cacert.org to your
> trusted authorities.

What sucks is that you can't even get rid of the warnings even if you 
accept and add the cert to Firefox.  Every time you click on an 
attachment in a bug, you get presented with a warning dialog again, and 
again, and again, and again, until you get mad and start shooting 
bunnies.  That's because the domain changes with attachments (for some 
reason, b.g.o. uses subdomains instead of URLs to link to attachments.)

So it's either add cacert.org to your trusted authorities, or live in 
hell when browsing b.g.o.  IMO that's just stupid.  I want to trust just 
b.g.o, not every site out there that has a cacert certificate.  Stupid. 
  Just stupid.




  parent reply	other threads:[~2011-12-21 17:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 17:31 [gentoo-user] From where the word 'gentoo' came? LinuxIsOne
2011-12-20 17:34 ` Michael Mol
2011-12-20 17:43   ` [gentoo-user] " Nikos Chantziaras
2011-12-20 17:54     ` LinuxIsOne
2011-12-20 17:59     ` Dan Johansson
2011-12-20 18:02       ` LinuxIsOne
2011-12-20 21:15       ` Dale
2011-12-20 21:35         ` Nikos Chantziaras
2011-12-20 23:08           ` Mark Knecht
2011-12-20 17:54   ` [gentoo-user] " LinuxIsOne
2011-12-20 18:06 ` Volker Armin Hemmann
2011-12-20 18:12   ` LinuxIsOne
2011-12-21 21:59   ` Alan McKinnon
2011-12-21 12:28 ` Daniel Troeder
2011-12-21 12:32   ` LinuxIsOne
2011-12-21 14:59     ` Joshua Murphy
2011-12-21 15:22       ` LinuxIsOne
2011-12-21 15:24       ` LinuxIsOne
2011-12-21 16:01         ` Joshua Murphy
2011-12-21 16:29           ` LinuxIsOne
2011-12-21 16:43             ` Mark Knecht
2011-12-21 17:09               ` LinuxIsOne
2011-12-21 16:45             ` Neil Bothwick
2011-12-21 17:10               ` LinuxIsOne
2011-12-21 17:50       ` Nikos Chantziaras [this message]
2011-12-21 21:56         ` [gentoo-user] " Alan E. Davis
2011-12-21 21:58           ` Alan E. Davis
2011-12-21 22:00             ` Alan E. Davis
2011-12-22  6:25           ` LinuxIsOne
2011-12-22  6:26         ` LinuxIsOne
2011-12-22 20:14           ` Alan E. Davis
2011-12-23 11:18             ` LinuxIsOne
2011-12-23 19:23           ` [gentoo-user] Re: Accepting as trusted b.g.o. certificates [was: From where the word 'gentoo' came?] Mick

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='jct68i$t3b$1@dough.gmane.org' \
    --to=realnc@arcor.de \
    --cc=gentoo-user@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