Poll: where do you have certs installed?
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path? E.g., I'm running Goobuntu, and I have them installed in /etc/ssl/certs/ca-certificates.crt. Thanks, --Juan
Am Donnerstag, 16. August 2007 01:01 schrieb Juan Lang:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
E.g., I'm running Goobuntu, and I have them installed in /etc/ssl/certs/ca-certificates.crt. Gentoo here, same path
Juan Lang escribió:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
E.g., I'm running Goobuntu, and I have them installed in /etc/ssl/certs/ca-certificates.crt.
Thanks, --Juan
My certificates are at /etc/pki/tls/certs/ca-bundle.crt (Fedora 7, openssl-0.9.8b-14.fc7) -- perl -e '$x=2.4;print sprintf("%.0f + %.0f = %.0f\n",$x,$x,$x+$x);'
Same for Mandriva 2007 Spring. On 8/15/07, Alex Villacís Lasso <a_villacis(a)palosanto.com> wrote:
Juan Lang escribió:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
E.g., I'm running Goobuntu, and I have them installed in /etc/ssl/certs/ca-certificates.crt.
Thanks, --Juan
My certificates are at /etc/pki/tls/certs/ca-bundle.crt (Fedora 7, openssl-0.9.8b-14.fc7)
-- perl -e '$x=2.4;print sprintf("%.0f + %.0f = %.0f\n",$x,$x,$x+$x);'
Juan Lang schreef:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
E.g., I'm running Goobuntu, and I have them installed in /etc/ssl/certs/ca-certificates.crt.
Thanks, --Juan
Seems same for kubuntu, so probably for all debians as well. Cheers, Maarten
Juan Lang escreveu:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
E.g., I'm running Goobuntu, and I have them installed in /etc/ssl/certs/ca-certificates.crt.
Thanks, --Juan
Fedora 4 (2.6.17-1.2142_FC4) /etc/pki/tls/certs/ca-bundle.crt
On Wednesday August 15 2007 23:01, Juan Lang wrote:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
E.g., I'm running Goobuntu, and I have them installed in /etc/ssl/certs/ca-certificates.crt.
Thanks, --Juan
On Debian Etch I have it here: /etc/ssl/certs/ca-certificates.crt It seems to be the same on all Ubuntu-like and Debian distros.
On Wed, Aug 15, 2007 at 04:01:33PM -0700, Juan Lang wrote:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
E.g., I'm running Goobuntu, and I have them installed in /etc/ssl/certs/ca-certificates.crt.
openSUSE 10.2 /etc/ssl/certs/ has the .pem files (no crt bundle) Ciao, Marcus
On Wednesday 15 August 2007, Juan Lang wrote:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
Why? This is a non-issue. Make it a configure parameter, document in the changelog/release notes, and the packagers will take care of it. Cheers, Kuba
On 8/16/07, Kuba Ober <kuba(a)mareimbrium.org> wrote:
On Wednesday 15 August 2007, Juan Lang wrote:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
Why? This is a non-issue. Make it a configure parameter, document in the changelog/release notes, and the packagers will take care of it.
That sort of logic is the reason why packaging in Linux is such a mess.
Cheers, Kuba
Bye Damjan
On Thursday 16 August 2007, Damjan Jovanovic wrote:
On 8/16/07, Kuba Ober <kuba(a)mareimbrium.org> wrote:
On Wednesday 15 August 2007, Juan Lang wrote:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
Why? This is a non-issue. Make it a configure parameter, document in the changelog/release notes, and the packagers will take care of it.
That sort of logic is the reason why packaging in Linux is such a mess.
I don't know why would you call it a mess, it works pretty much fine for me... When is it less of a mess: 1. When you hardcode a bunch of "maybe" paths to look for, 2. When people who know the distro put in *the* path which is known to be correct... ? Cheers, Kuba
Kuba Ober <kuba(a)mareimbrium.org> writes:
On Wednesday 15 August 2007, Juan Lang wrote:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
Why? This is a non-issue. Make it a configure parameter, document in the changelog/release notes, and the packagers will take care of it.
It's very much an issue if you want to build a binary that works on multiple distros (like Crossover, to take a random example). That's already hard enough to do as it is... -- Alexandre Julliard julliard(a)winehq.org
On Thursday 16 August 2007, you wrote:
Kuba Ober <kuba(a)mareimbrium.org> writes:
On Wednesday 15 August 2007, Juan Lang wrote:
Could some of you check where you have, say, OpenSSL's CA certificates installed, and email me what distro you're running, and the path?
Why? This is a non-issue. Make it a configure parameter, document in the changelog/release notes, and the packagers will take care of it.
It's very much an issue if you want to build a binary that works on multiple distros (like Crossover, to take a random example). That's already hard enough to do as it is...
A configurable symlink then? Crossover can have their own hack in place for that, it doesn't really belong in an open-source system IMHO. It's a triviality, and hardcoding various "maybe here, maybe there" paths to look through will only prompt "hey, but it doesn't work for ME" issues... Again, IMHO. Anyway, on my FC6 system the certs are in /etc/pki/tls/certs/ca-bundle.crt Cheers, Kuba
On Thursday 16 August 2007 16:06:31 Kuba Ober wrote:
Why? This is a non-issue. Make it a configure parameter, document in the changelog/release notes, and the packagers will take care of it.
It's very much an issue if you want to build a binary that works on multiple distros (like Crossover, to take a random example). That's already hard enough to do as it is...
A configurable symlink then? Crossover can have their own hack in place for that, it doesn't really belong in an open-source system IMHO.
Maybe using Crossover as an example was unfortunate, as it was bound to provoke this response. However, it's a real example, as opposed to my more theoretical example. There are binaries that are supposed to work on multiple distributions. Autopackage is one system to create those, LSB binaries are another. In those cases, a configure option probably is a bad idea.
It's a triviality, and hardcoding various "maybe here, maybe there" paths to look through will only prompt "hey, but it doesn't work for ME" issues... Again, IMHO.
No one will ever be happy with any given solution. Such is life. Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton.
participants (12)
-
Alex Villacís Lasso -
Alexandre Julliard -
Damjan Jovanovic -
Juan Lang -
Kai Blin -
Kuba Ober -
L. Rahyen -
Lei Zhang -
Maarten Lankhorst -
Marcelo Duarte -
Marcus Meissner -
Stefan Dösinger