Has anyone run across anything (e.g. wine) that needs ca-certificates installed?

If so, I need testing and feedback on http://slackware.com/~rworkman/ca-ce...arch-1_rlw.tgz.
Sources are here: http://slackware.com/~rworkman/ca-certificates/

I use ca-certificates for sending mail. My setup uses mutt, msmtp,
and maildrop. The ones in /usr/share/curl/ca-bundle.crt have always
worked fine for me. If you can clue me in to why I would use these
different ones, I'd be more than willing to help out.

Well, it stemmed from this:
http://bugs.winehq.org/show_bug.cgi?id=15704

My memory is a bit fuzzy, and at this hour, so is my mind in general, but I seem to recall that the bundled certs were added to curl after openssl stopped bundling them in their sources (and thus the packages).

To be quite honest, I'm not entirely sure how (or even if) this will help you specifically. I'm guessing that it won't, so long as the /usr/share/curl/ca-bundle.crt is present. That being said, I'm not going to ask you to remove it for testing, but if you're feeling froggy, jump... :-)

Note that I've since updated those sources with a bugfix and included a package in the original post.

I'm using the certs that come with Slackware all the way back to 10.1 with no problems:
That's the oldest system I've got running on this LAN.

I read the bug report you posted, and don't see it as a bug for Slackware. Just a
problem not using the correct $PATH.

What sayest thou about this? Has he tried fixing the $PATH and building?

As the bug report indicates, it's not really a "bug" in Slackware at all - it's another system that doesn't have the Verisign root cert which is failing on a crypt test when building wine. I've never run across it in Slackware, so admittedly this is a low priority thing for us. The main thing I'm trying to figure out is whether we might actually *need* these certs or not.

Tangentially to that is whether installing them could potentially be undesirable; I don't see how they would, and it's a small (121k) package, but perhaps I'm missing something...

Look at the certs in /usr/share/curl/ca-bundle.crt and compare those to
the ones your source for that package would issue. The privacy service
for which I need a cert is pretty picky -- they even only used their
own, self-signed cert for years because they didn't see the need to
pay for one. Now I can use a cert from that package in Slackware, and
it's fine. I'm personally not changing, because it would mean using a
non-Slackware source when the one with Slack works just fine. There
are few packages that I choose to do that with, preferring to keep
everything that works satisfactorily an official Slackware package.

The original bug report you linked had a guy that postedI think he'd be better served by someone telling him about the
/usr/share/curl/ca-bundle.crt $PATH to certs in Slackware,
rather than building another package - especially based from
Debian. I, too, have built wine myself for years and never
came across that error message even once.

Just my opinion, worth what you paid for it.

I found a use case for the ca-certificates :-)
http://www.ews.uiuc.edu/~dantle2/UIwpa2.html

It is just a side-note to this thread but I wonder if you have seen this very nice piece of work:

http://curl.haxx.se/lxr/source/lib/mk-ca-bundle.pl

which I have written into a guide as:

Andrew