| 1 |
On 12/21/2011 04:59 PM, Joshua Murphy wrote: |
| 2 |
> On Wed, Dec 21, 2011 at 7:32 AM, LinuxIsOne<reallife@×××××××.com> wrote: |
| 3 |
>> On Wed, Dec 21, 2011 at 5:58 PM, Daniel Troeder<daniel@×××××××××.com> wrote: |
| 4 |
>> |
| 5 |
>>> Also (ir)relevant: bug report concerning the mascot Larry the cow: |
| 6 |
>>> https://bugs.gentoo.org/show_bug.cgi?id=27727 |
| 7 |
>> |
| 8 |
>> But your links shows untrusted connection in my browser! |
| 9 |
>> |
| 10 |
> |
| 11 |
> That would likely be because cacert.org isn't a "trusted' authority by |
| 12 |
> default and that is the issuer for B.G.O., making the certificate |
| 13 |
> throw up a red flag if you choose not to add cacert.org to your |
| 14 |
> trusted authorities. |
| 15 |
|
| 16 |
What sucks is that you can't even get rid of the warnings even if you |
| 17 |
accept and add the cert to Firefox. Every time you click on an |
| 18 |
attachment in a bug, you get presented with a warning dialog again, and |
| 19 |
again, and again, and again, until you get mad and start shooting |
| 20 |
bunnies. That's because the domain changes with attachments (for some |
| 21 |
reason, b.g.o. uses subdomains instead of URLs to link to attachments.) |
| 22 |
|
| 23 |
So it's either add cacert.org to your trusted authorities, or live in |
| 24 |
hell when browsing b.g.o. IMO that's just stupid. I want to trust just |
| 25 |
b.g.o, not every site out there that has a cacert certificate. Stupid. |
| 26 |
Just stupid. |
Archives