| 1 |
On Wed, Dec 21, 2011 at 10:24 AM, LinuxIsOne <reallife@×××××××.com> wrote: |
| 2 |
> On Wed, Dec 21, 2011 at 8:29 PM, Joshua Murphy <poisonbl@×××××.com> wrote: |
| 3 |
> |
| 4 |
>> That would likely be because cacert.org isn't a "trusted' authority by |
| 5 |
>> default and that is the issuer for B.G.O., making the certificate |
| 6 |
>> throw up a red flag if you choose not to add cacert.org to your |
| 7 |
>> trusted authorities. |
| 8 |
> |
| 9 |
> And finally there is no security risk in adding cacert.org to the |
| 10 |
> trusted authorities? |
| 11 |
> |
| 12 |
|
| 13 |
Well, that's up to whether you trust that issuer not to give out |
| 14 |
certificates to people using falsified credentials, setting up |
| 15 |
phishing sites, etc. Any time you choose to allow a person outside of |
| 16 |
yourself to decide who or what you trust, there's some element of |
| 17 |
risk. That the Gentoo devs trust cacert.org to be their issuer for |
| 18 |
b.g.o. is enough for me to feel that risk is worth it in my case, but |
| 19 |
that's as much as I can really say. |
| 20 |
|
| 21 |
-- |
| 22 |
Poison [BLX] |
| 23 |
Joshua M. Murphy |
Archives