How do I install a system-wide SSL certificate on openSUSE?
Clash Royale CLAN TAG#URR8PPP
I have a PEM certificate that I just downloaded from a webserver. I want to install it system-wide so I can curl the server without it complaining about a missing certificate.
I tried putting the file in /etc/ssl/certs, but nothing happened.
opensuse suse ssl certificates
add a comment |
I have a PEM certificate that I just downloaded from a webserver. I want to install it system-wide so I can curl the server without it complaining about a missing certificate.
I tried putting the file in /etc/ssl/certs, but nothing happened.
opensuse suse ssl certificates
add a comment |
I have a PEM certificate that I just downloaded from a webserver. I want to install it system-wide so I can curl the server without it complaining about a missing certificate.
I tried putting the file in /etc/ssl/certs, but nothing happened.
opensuse suse ssl certificates
I have a PEM certificate that I just downloaded from a webserver. I want to install it system-wide so I can curl the server without it complaining about a missing certificate.
I tried putting the file in /etc/ssl/certs, but nothing happened.
opensuse suse ssl certificates
opensuse suse ssl certificates
edited Jun 20 '13 at 22:34
Gilles
540k12810931606
540k12810931606
asked Jun 20 '13 at 13:05
OinOin
162119
162119
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
As already mentioned SUSE supports ca-certificates starting with openSUSE 13.1 / SLES 12.
The difference to debian/Ubuntu is the directory for your certififcates. The SLES man page to update-ca-certificates
has these directories:
FILES
/usr/share/pki/trust/anchors
Directory of CA certificate trust anchors.
/usr/share/pki/trust/blacklist
Directory of blacklisted CA certificates
/etc/pki/trust/anchors
Directory of CA certificate trust anchors for use by the admin
/etc/pki/trust/blacklist
Directory of blacklisted CA certificates for use by the admin
The openSUSE package mentions these:
- Packages are expected to install their CA certificates in
/usr/share/pki/trust/anchors or /usr/share/pki/trust (no extra subdir) instead
of /usr/share/ca-certificates/<vendor> now. The anchors subdirectory is for
regular pem files, the directory one above for pem files in
openssl's 'trusted' format.
add a comment |
I would take a look for a package called ca-certificates
(that's the name it goes by on Red Hat distros). All of the main distros bundle certificates and they're generally in the same location.
Since SuSE uses RPM packages as well I'd guess you could do a query like this to find the name of the package that provides certificates:
$ rpm -aq | grep -i cert
ca-certificates-2010.63-3.el6_1.5.noarch
With the name of this package I can then rpm -qi <package name>
to find out more info about it:
$ rpm -qi ca-certificates-2010.63-3.el6_1.5.noarch
Name : ca-certificates Relocations: (not relocatable)
Version : 2010.63 Vendor: CentOS
Release : 3.el6_1.5 Build Date: Fri 23 Sep 2011 03:39:46 PM EDT
Install Date: Sat 15 Dec 2012 02:34:14 PM EST Build Host: c6b5.bsys.dev.centos.org
Group : System Environment/Base Source RPM: ca-certificates-2010.63-3.el6_1.5.src.rpm
Size : 1353134 License: Public Domain
Signature : RSA/SHA1, Mon 26 Sep 2011 12:17:03 AM EDT, Key ID 0946fca2c105b9de
Packager : CentOS BuildSystem <http://bugs.centos.org>
URL : http://www.mozilla.org/
Summary : The Mozilla CA root certificate bundle
Description :
This package contains the set of CA certificates chosen by the
Mozilla Foundation for use with the Internet PKI.
This command will list its contents:
$ rpm -ql ca-certificates-2010.63-3.el6_1.5.noarch
/etc/pki/java
/etc/pki/java/cacerts
/etc/pki/tls
/etc/pki/tls/cert.pem
/etc/pki/tls/certs
/etc/pki/tls/certs/ca-bundle.crt
/etc/pki/tls/certs/ca-bundle.trust.crt
/etc/ssl
/etc/ssl/certs
This last command will show you where the certificates are getting stored.
YaST
If you don't want to manually do this I believe you can use YaST to add CA certificates as well. Here's a tutorial titled: Chapter 15. Managing X.509 Certification that should guide you through that process.
The listed package search command only searches installed packages, not available (SUSE users will have better luck usingzypper -n search cert
to find packages). And listing the contents of the package does not tell you what the directories the package creates are for, just that they exist. The documentation linked to, when it existed (I'll fix the link in a sec), provides instructions on how to create a new CA, not manage imported CAs. All that said, this is not really a "bad" answer, as it provides good "how I'd figure this out" steps; it just does not belong as the top answer.
– dannysauer
Feb 7 at 20:25
add a comment |
I believe you can use update-ca-certificates
provided by ca-certificates, try these ubuntu instructions and update this answer if required
https://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu
On openSUSE you should copy to/usr/share/ca-certificates
instead of/usr/local/share/ca-certificates
.
– To1ne
Jul 10 '14 at 7:08
On OpenSUSE Leap 42.1 I've found:/usr/lib/ca-certificates
– david.perez
Jun 29 '16 at 7:55
See the answer @Christian posted for the current appropriate directory (/usr/share/pki/trust/anchors
).
– dannysauer
Feb 7 at 20:42
add a comment |
I installed:
ca-certificates-cacert
ca-certificates-mozilla
and it solved the issue.
ca-certficates-mozilla
should beca-certificates-mozilla
.
– ismailarilik
Jan 19 '17 at 12:49
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f80131%2fhow-do-i-install-a-system-wide-ssl-certificate-on-opensuse%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
As already mentioned SUSE supports ca-certificates starting with openSUSE 13.1 / SLES 12.
The difference to debian/Ubuntu is the directory for your certififcates. The SLES man page to update-ca-certificates
has these directories:
FILES
/usr/share/pki/trust/anchors
Directory of CA certificate trust anchors.
/usr/share/pki/trust/blacklist
Directory of blacklisted CA certificates
/etc/pki/trust/anchors
Directory of CA certificate trust anchors for use by the admin
/etc/pki/trust/blacklist
Directory of blacklisted CA certificates for use by the admin
The openSUSE package mentions these:
- Packages are expected to install their CA certificates in
/usr/share/pki/trust/anchors or /usr/share/pki/trust (no extra subdir) instead
of /usr/share/ca-certificates/<vendor> now. The anchors subdirectory is for
regular pem files, the directory one above for pem files in
openssl's 'trusted' format.
add a comment |
As already mentioned SUSE supports ca-certificates starting with openSUSE 13.1 / SLES 12.
The difference to debian/Ubuntu is the directory for your certififcates. The SLES man page to update-ca-certificates
has these directories:
FILES
/usr/share/pki/trust/anchors
Directory of CA certificate trust anchors.
/usr/share/pki/trust/blacklist
Directory of blacklisted CA certificates
/etc/pki/trust/anchors
Directory of CA certificate trust anchors for use by the admin
/etc/pki/trust/blacklist
Directory of blacklisted CA certificates for use by the admin
The openSUSE package mentions these:
- Packages are expected to install their CA certificates in
/usr/share/pki/trust/anchors or /usr/share/pki/trust (no extra subdir) instead
of /usr/share/ca-certificates/<vendor> now. The anchors subdirectory is for
regular pem files, the directory one above for pem files in
openssl's 'trusted' format.
add a comment |
As already mentioned SUSE supports ca-certificates starting with openSUSE 13.1 / SLES 12.
The difference to debian/Ubuntu is the directory for your certififcates. The SLES man page to update-ca-certificates
has these directories:
FILES
/usr/share/pki/trust/anchors
Directory of CA certificate trust anchors.
/usr/share/pki/trust/blacklist
Directory of blacklisted CA certificates
/etc/pki/trust/anchors
Directory of CA certificate trust anchors for use by the admin
/etc/pki/trust/blacklist
Directory of blacklisted CA certificates for use by the admin
The openSUSE package mentions these:
- Packages are expected to install their CA certificates in
/usr/share/pki/trust/anchors or /usr/share/pki/trust (no extra subdir) instead
of /usr/share/ca-certificates/<vendor> now. The anchors subdirectory is for
regular pem files, the directory one above for pem files in
openssl's 'trusted' format.
As already mentioned SUSE supports ca-certificates starting with openSUSE 13.1 / SLES 12.
The difference to debian/Ubuntu is the directory for your certififcates. The SLES man page to update-ca-certificates
has these directories:
FILES
/usr/share/pki/trust/anchors
Directory of CA certificate trust anchors.
/usr/share/pki/trust/blacklist
Directory of blacklisted CA certificates
/etc/pki/trust/anchors
Directory of CA certificate trust anchors for use by the admin
/etc/pki/trust/blacklist
Directory of blacklisted CA certificates for use by the admin
The openSUSE package mentions these:
- Packages are expected to install their CA certificates in
/usr/share/pki/trust/anchors or /usr/share/pki/trust (no extra subdir) instead
of /usr/share/ca-certificates/<vendor> now. The anchors subdirectory is for
regular pem files, the directory one above for pem files in
openssl's 'trusted' format.
answered Feb 18 '16 at 14:11
ChristianChristian
1,21677
1,21677
add a comment |
add a comment |
I would take a look for a package called ca-certificates
(that's the name it goes by on Red Hat distros). All of the main distros bundle certificates and they're generally in the same location.
Since SuSE uses RPM packages as well I'd guess you could do a query like this to find the name of the package that provides certificates:
$ rpm -aq | grep -i cert
ca-certificates-2010.63-3.el6_1.5.noarch
With the name of this package I can then rpm -qi <package name>
to find out more info about it:
$ rpm -qi ca-certificates-2010.63-3.el6_1.5.noarch
Name : ca-certificates Relocations: (not relocatable)
Version : 2010.63 Vendor: CentOS
Release : 3.el6_1.5 Build Date: Fri 23 Sep 2011 03:39:46 PM EDT
Install Date: Sat 15 Dec 2012 02:34:14 PM EST Build Host: c6b5.bsys.dev.centos.org
Group : System Environment/Base Source RPM: ca-certificates-2010.63-3.el6_1.5.src.rpm
Size : 1353134 License: Public Domain
Signature : RSA/SHA1, Mon 26 Sep 2011 12:17:03 AM EDT, Key ID 0946fca2c105b9de
Packager : CentOS BuildSystem <http://bugs.centos.org>
URL : http://www.mozilla.org/
Summary : The Mozilla CA root certificate bundle
Description :
This package contains the set of CA certificates chosen by the
Mozilla Foundation for use with the Internet PKI.
This command will list its contents:
$ rpm -ql ca-certificates-2010.63-3.el6_1.5.noarch
/etc/pki/java
/etc/pki/java/cacerts
/etc/pki/tls
/etc/pki/tls/cert.pem
/etc/pki/tls/certs
/etc/pki/tls/certs/ca-bundle.crt
/etc/pki/tls/certs/ca-bundle.trust.crt
/etc/ssl
/etc/ssl/certs
This last command will show you where the certificates are getting stored.
YaST
If you don't want to manually do this I believe you can use YaST to add CA certificates as well. Here's a tutorial titled: Chapter 15. Managing X.509 Certification that should guide you through that process.
The listed package search command only searches installed packages, not available (SUSE users will have better luck usingzypper -n search cert
to find packages). And listing the contents of the package does not tell you what the directories the package creates are for, just that they exist. The documentation linked to, when it existed (I'll fix the link in a sec), provides instructions on how to create a new CA, not manage imported CAs. All that said, this is not really a "bad" answer, as it provides good "how I'd figure this out" steps; it just does not belong as the top answer.
– dannysauer
Feb 7 at 20:25
add a comment |
I would take a look for a package called ca-certificates
(that's the name it goes by on Red Hat distros). All of the main distros bundle certificates and they're generally in the same location.
Since SuSE uses RPM packages as well I'd guess you could do a query like this to find the name of the package that provides certificates:
$ rpm -aq | grep -i cert
ca-certificates-2010.63-3.el6_1.5.noarch
With the name of this package I can then rpm -qi <package name>
to find out more info about it:
$ rpm -qi ca-certificates-2010.63-3.el6_1.5.noarch
Name : ca-certificates Relocations: (not relocatable)
Version : 2010.63 Vendor: CentOS
Release : 3.el6_1.5 Build Date: Fri 23 Sep 2011 03:39:46 PM EDT
Install Date: Sat 15 Dec 2012 02:34:14 PM EST Build Host: c6b5.bsys.dev.centos.org
Group : System Environment/Base Source RPM: ca-certificates-2010.63-3.el6_1.5.src.rpm
Size : 1353134 License: Public Domain
Signature : RSA/SHA1, Mon 26 Sep 2011 12:17:03 AM EDT, Key ID 0946fca2c105b9de
Packager : CentOS BuildSystem <http://bugs.centos.org>
URL : http://www.mozilla.org/
Summary : The Mozilla CA root certificate bundle
Description :
This package contains the set of CA certificates chosen by the
Mozilla Foundation for use with the Internet PKI.
This command will list its contents:
$ rpm -ql ca-certificates-2010.63-3.el6_1.5.noarch
/etc/pki/java
/etc/pki/java/cacerts
/etc/pki/tls
/etc/pki/tls/cert.pem
/etc/pki/tls/certs
/etc/pki/tls/certs/ca-bundle.crt
/etc/pki/tls/certs/ca-bundle.trust.crt
/etc/ssl
/etc/ssl/certs
This last command will show you where the certificates are getting stored.
YaST
If you don't want to manually do this I believe you can use YaST to add CA certificates as well. Here's a tutorial titled: Chapter 15. Managing X.509 Certification that should guide you through that process.
The listed package search command only searches installed packages, not available (SUSE users will have better luck usingzypper -n search cert
to find packages). And listing the contents of the package does not tell you what the directories the package creates are for, just that they exist. The documentation linked to, when it existed (I'll fix the link in a sec), provides instructions on how to create a new CA, not manage imported CAs. All that said, this is not really a "bad" answer, as it provides good "how I'd figure this out" steps; it just does not belong as the top answer.
– dannysauer
Feb 7 at 20:25
add a comment |
I would take a look for a package called ca-certificates
(that's the name it goes by on Red Hat distros). All of the main distros bundle certificates and they're generally in the same location.
Since SuSE uses RPM packages as well I'd guess you could do a query like this to find the name of the package that provides certificates:
$ rpm -aq | grep -i cert
ca-certificates-2010.63-3.el6_1.5.noarch
With the name of this package I can then rpm -qi <package name>
to find out more info about it:
$ rpm -qi ca-certificates-2010.63-3.el6_1.5.noarch
Name : ca-certificates Relocations: (not relocatable)
Version : 2010.63 Vendor: CentOS
Release : 3.el6_1.5 Build Date: Fri 23 Sep 2011 03:39:46 PM EDT
Install Date: Sat 15 Dec 2012 02:34:14 PM EST Build Host: c6b5.bsys.dev.centos.org
Group : System Environment/Base Source RPM: ca-certificates-2010.63-3.el6_1.5.src.rpm
Size : 1353134 License: Public Domain
Signature : RSA/SHA1, Mon 26 Sep 2011 12:17:03 AM EDT, Key ID 0946fca2c105b9de
Packager : CentOS BuildSystem <http://bugs.centos.org>
URL : http://www.mozilla.org/
Summary : The Mozilla CA root certificate bundle
Description :
This package contains the set of CA certificates chosen by the
Mozilla Foundation for use with the Internet PKI.
This command will list its contents:
$ rpm -ql ca-certificates-2010.63-3.el6_1.5.noarch
/etc/pki/java
/etc/pki/java/cacerts
/etc/pki/tls
/etc/pki/tls/cert.pem
/etc/pki/tls/certs
/etc/pki/tls/certs/ca-bundle.crt
/etc/pki/tls/certs/ca-bundle.trust.crt
/etc/ssl
/etc/ssl/certs
This last command will show you where the certificates are getting stored.
YaST
If you don't want to manually do this I believe you can use YaST to add CA certificates as well. Here's a tutorial titled: Chapter 15. Managing X.509 Certification that should guide you through that process.
I would take a look for a package called ca-certificates
(that's the name it goes by on Red Hat distros). All of the main distros bundle certificates and they're generally in the same location.
Since SuSE uses RPM packages as well I'd guess you could do a query like this to find the name of the package that provides certificates:
$ rpm -aq | grep -i cert
ca-certificates-2010.63-3.el6_1.5.noarch
With the name of this package I can then rpm -qi <package name>
to find out more info about it:
$ rpm -qi ca-certificates-2010.63-3.el6_1.5.noarch
Name : ca-certificates Relocations: (not relocatable)
Version : 2010.63 Vendor: CentOS
Release : 3.el6_1.5 Build Date: Fri 23 Sep 2011 03:39:46 PM EDT
Install Date: Sat 15 Dec 2012 02:34:14 PM EST Build Host: c6b5.bsys.dev.centos.org
Group : System Environment/Base Source RPM: ca-certificates-2010.63-3.el6_1.5.src.rpm
Size : 1353134 License: Public Domain
Signature : RSA/SHA1, Mon 26 Sep 2011 12:17:03 AM EDT, Key ID 0946fca2c105b9de
Packager : CentOS BuildSystem <http://bugs.centos.org>
URL : http://www.mozilla.org/
Summary : The Mozilla CA root certificate bundle
Description :
This package contains the set of CA certificates chosen by the
Mozilla Foundation for use with the Internet PKI.
This command will list its contents:
$ rpm -ql ca-certificates-2010.63-3.el6_1.5.noarch
/etc/pki/java
/etc/pki/java/cacerts
/etc/pki/tls
/etc/pki/tls/cert.pem
/etc/pki/tls/certs
/etc/pki/tls/certs/ca-bundle.crt
/etc/pki/tls/certs/ca-bundle.trust.crt
/etc/ssl
/etc/ssl/certs
This last command will show you where the certificates are getting stored.
YaST
If you don't want to manually do this I believe you can use YaST to add CA certificates as well. Here's a tutorial titled: Chapter 15. Managing X.509 Certification that should guide you through that process.
edited Feb 7 at 20:54
dannysauer
85049
85049
answered Jun 20 '13 at 14:32
slm♦slm
252k70533685
252k70533685
The listed package search command only searches installed packages, not available (SUSE users will have better luck usingzypper -n search cert
to find packages). And listing the contents of the package does not tell you what the directories the package creates are for, just that they exist. The documentation linked to, when it existed (I'll fix the link in a sec), provides instructions on how to create a new CA, not manage imported CAs. All that said, this is not really a "bad" answer, as it provides good "how I'd figure this out" steps; it just does not belong as the top answer.
– dannysauer
Feb 7 at 20:25
add a comment |
The listed package search command only searches installed packages, not available (SUSE users will have better luck usingzypper -n search cert
to find packages). And listing the contents of the package does not tell you what the directories the package creates are for, just that they exist. The documentation linked to, when it existed (I'll fix the link in a sec), provides instructions on how to create a new CA, not manage imported CAs. All that said, this is not really a "bad" answer, as it provides good "how I'd figure this out" steps; it just does not belong as the top answer.
– dannysauer
Feb 7 at 20:25
The listed package search command only searches installed packages, not available (SUSE users will have better luck using
zypper -n search cert
to find packages). And listing the contents of the package does not tell you what the directories the package creates are for, just that they exist. The documentation linked to, when it existed (I'll fix the link in a sec), provides instructions on how to create a new CA, not manage imported CAs. All that said, this is not really a "bad" answer, as it provides good "how I'd figure this out" steps; it just does not belong as the top answer.– dannysauer
Feb 7 at 20:25
The listed package search command only searches installed packages, not available (SUSE users will have better luck using
zypper -n search cert
to find packages). And listing the contents of the package does not tell you what the directories the package creates are for, just that they exist. The documentation linked to, when it existed (I'll fix the link in a sec), provides instructions on how to create a new CA, not manage imported CAs. All that said, this is not really a "bad" answer, as it provides good "how I'd figure this out" steps; it just does not belong as the top answer.– dannysauer
Feb 7 at 20:25
add a comment |
I believe you can use update-ca-certificates
provided by ca-certificates, try these ubuntu instructions and update this answer if required
https://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu
On openSUSE you should copy to/usr/share/ca-certificates
instead of/usr/local/share/ca-certificates
.
– To1ne
Jul 10 '14 at 7:08
On OpenSUSE Leap 42.1 I've found:/usr/lib/ca-certificates
– david.perez
Jun 29 '16 at 7:55
See the answer @Christian posted for the current appropriate directory (/usr/share/pki/trust/anchors
).
– dannysauer
Feb 7 at 20:42
add a comment |
I believe you can use update-ca-certificates
provided by ca-certificates, try these ubuntu instructions and update this answer if required
https://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu
On openSUSE you should copy to/usr/share/ca-certificates
instead of/usr/local/share/ca-certificates
.
– To1ne
Jul 10 '14 at 7:08
On OpenSUSE Leap 42.1 I've found:/usr/lib/ca-certificates
– david.perez
Jun 29 '16 at 7:55
See the answer @Christian posted for the current appropriate directory (/usr/share/pki/trust/anchors
).
– dannysauer
Feb 7 at 20:42
add a comment |
I believe you can use update-ca-certificates
provided by ca-certificates, try these ubuntu instructions and update this answer if required
https://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu
I believe you can use update-ca-certificates
provided by ca-certificates, try these ubuntu instructions and update this answer if required
https://superuser.com/questions/437330/how-do-you-add-a-certificate-authority-ca-to-ubuntu
edited Mar 20 '17 at 10:04
community wiki
2 revs
KCD
On openSUSE you should copy to/usr/share/ca-certificates
instead of/usr/local/share/ca-certificates
.
– To1ne
Jul 10 '14 at 7:08
On OpenSUSE Leap 42.1 I've found:/usr/lib/ca-certificates
– david.perez
Jun 29 '16 at 7:55
See the answer @Christian posted for the current appropriate directory (/usr/share/pki/trust/anchors
).
– dannysauer
Feb 7 at 20:42
add a comment |
On openSUSE you should copy to/usr/share/ca-certificates
instead of/usr/local/share/ca-certificates
.
– To1ne
Jul 10 '14 at 7:08
On OpenSUSE Leap 42.1 I've found:/usr/lib/ca-certificates
– david.perez
Jun 29 '16 at 7:55
See the answer @Christian posted for the current appropriate directory (/usr/share/pki/trust/anchors
).
– dannysauer
Feb 7 at 20:42
On openSUSE you should copy to
/usr/share/ca-certificates
instead of /usr/local/share/ca-certificates
.– To1ne
Jul 10 '14 at 7:08
On openSUSE you should copy to
/usr/share/ca-certificates
instead of /usr/local/share/ca-certificates
.– To1ne
Jul 10 '14 at 7:08
On OpenSUSE Leap 42.1 I've found:
/usr/lib/ca-certificates
– david.perez
Jun 29 '16 at 7:55
On OpenSUSE Leap 42.1 I've found:
/usr/lib/ca-certificates
– david.perez
Jun 29 '16 at 7:55
See the answer @Christian posted for the current appropriate directory (
/usr/share/pki/trust/anchors
).– dannysauer
Feb 7 at 20:42
See the answer @Christian posted for the current appropriate directory (
/usr/share/pki/trust/anchors
).– dannysauer
Feb 7 at 20:42
add a comment |
I installed:
ca-certificates-cacert
ca-certificates-mozilla
and it solved the issue.
ca-certficates-mozilla
should beca-certificates-mozilla
.
– ismailarilik
Jan 19 '17 at 12:49
add a comment |
I installed:
ca-certificates-cacert
ca-certificates-mozilla
and it solved the issue.
ca-certficates-mozilla
should beca-certificates-mozilla
.
– ismailarilik
Jan 19 '17 at 12:49
add a comment |
I installed:
ca-certificates-cacert
ca-certificates-mozilla
and it solved the issue.
I installed:
ca-certificates-cacert
ca-certificates-mozilla
and it solved the issue.
edited Feb 7 at 20:13
PRY
2,58131026
2,58131026
answered Jul 2 '16 at 1:27
alexalex
1
1
ca-certficates-mozilla
should beca-certificates-mozilla
.
– ismailarilik
Jan 19 '17 at 12:49
add a comment |
ca-certficates-mozilla
should beca-certificates-mozilla
.
– ismailarilik
Jan 19 '17 at 12:49
ca-certficates-mozilla
should be ca-certificates-mozilla
.– ismailarilik
Jan 19 '17 at 12:49
ca-certficates-mozilla
should be ca-certificates-mozilla
.– ismailarilik
Jan 19 '17 at 12:49
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f80131%2fhow-do-i-install-a-system-wide-ssl-certificate-on-opensuse%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown