Go Daddy root certificates

Martin Koller kollix at aon.at
Mon Jul 25 11:18:05 BST 2011

On Monday, 25. July 2011 02:10:56 Thiago Macieira wrote:
> On Sunday, 24 de July de 2011 14:51:34 Gary Greene wrote:
> > On Jul 23, 2011, at 10:33 AM, Martin Koller wrote:
> > > Hi,
> > > 
> > > can anyone answer the case https://bugs.kde.org/show_bug.cgi?id=277319 ,
> > > please ?
> > Honestly, I really wish that Mozilla/KDE/Google/Wget/<insert FOSS group that
> > has their own root certificate store here> would get together on fdo and
> > create a common project that the root certificates could be aggregated at
> > instead of each project doing it themselves...
> The answer is: STOP distributing our own certificates. Rely on Qt's support, 
> which also doesn't distribute certificates. The burden then falls on the system 
> integrator (the distros), which will select a root CA package that they feel 
> confident about.
> They're also the ones who can roll out security updates directly to the users. 
> We can't.

How does the resolution process work here in KDE - I mean: who has the final say that KDE
stops (or doesn't stop) to deliver the certificates ?

Can I close mentioned bko entry as INVALID or WONTFIX ?

Best regards/Schöne Grüße

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments

Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20110725/30a1b0ed/attachment.sig>

More information about the kde-core-devel mailing list