Package: KernSmooth
Priority: recommended
Version: 2.23-10
Date: 2013-03-20
Title: Functions for kernel smoothing for Wand & Jones (1995)
Authors@R: c(person("Matt", "Wand", role = "aut", email =
        "Matt.Wand@uts.edu.au"), person("Brian", "Ripley", role =
        c("trl", "cre", "ctb"), email = "ripley@stats.ox.ac.uk",
        comment = "R port and updates"))
Depends: R (>= 2.5.0), stats
Suggests: MASS
Description: functions for kernel smoothing (and density estimation)
        corresponding to the book: Wand, M.P. and Jones, M.C. (1995)
        "Kernel Smoothing".
License: Unlimited
ByteCompile: yes
Packaged: 2013-03-19 08:19:45 UTC; ripley
Author: Matt Wand [aut], Brian Ripley [trl, cre, ctb] (R port and
        updates)
Maintainer: Brian Ripley <ripley@stats.ox.ac.uk>
NeedsCompilation: yes
Repository: CRAN
Date/Publication: 2013-03-19 13:18:58
Built: R 3.0.0; x86_64-w64-mingw32; 2013-04-03 12:41:14 UTC; windows
Archs: i386, x64
///////////////////
Let's say you try to download something using curl or install hub using brew, then, you get an error like:

==> Downloading https://ghcr.io/v2/linuxbrew/core/ncurses/manifests/6.2
curl: (60) SSL certificate problem: unable to get local issuer certificate
Then, let ghcr.io being the server, execute following commands:

cd ~
# Download the cert:
openssl s_client -showcerts -servername ghcr.io  -connect ghcr.io:443 > cacert.pem
# type "quit", followed by the "ENTER" key / or Ctrl+C
# see the data in the certificate:
openssl x509 -inform PEM -in cacert.pem -text -out certdata-ghcr.io.txt
# move the file to certificate store directory:
sudo mv cacert.pem /usr/local/share/ca-certificates/cacert-ghcr.io.crt
# update certificates
sudo update-ca-certificates
# done !
/////////////////
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
////////////////
# 1
openssl s_client -showcerts \
-connect jsonplaceholder.typicode.com:443 </dev/null 2>/dev/null \
| sed -n '/-----BEGIN CERTIFICATE-----/,/-----END CERTIFICATE-----/p'  > typicode.crt
# 2
curl --cacert typicode.crt -v \
-d "userId=5&title=Hello World&body=Post body." \
 https://jsonplaceholder.typicode.com/posts
OPTION 2 (installer script)
In case the curl command is executed by an installer you don't have control, then, update your certificates:

Extract the certificates from server (use the FQDN or IP and PORT, i.e: jsonplaceholder.typicode.com:443)
Move the XXX.crt certificate to your certificates directory
Update certificates
Execute installation script
# 1
openssl s_client -showcerts \
-connect jsonplaceholder.typicode.com:443 </dev/null 2>/dev/null \
| sed -n '/-----BEGIN CERTIFICATE-----/,/-----END CERTIFICATE-----/p'  > typicode.crt
# 2
sudo mv typicode.crt /usr/local/share/ca-certificates/
# 3
sudo update-ca-certificates
# 4 execute your installer script
////////////////////////////////
Thanks for the answer, however the problem is that "our company is using the Zscaler transparent proxy which is intercepting SSL requests with its own certificate", which doesn't seems to have been addressed, as it's quite different from getting a normal site certificate.
- xpt
Nov 18, 2021 at 4:34
I had same issue, my company is using Zscaler, I executed those steps and then, I was able to re-try an installation (snap) and went through without issues. Try: openssl s_client -showcerts -servername server -connect 165.225.216.33:443 > zscaler.pem Get the IP from ip.zscaler.com
- Adrian Escutia Soto
Nov 18, 2021 at 18:28 
If you are installing from script, review what is the address used by the curl command, execute with verbose to get the IP and Port that is failing, i.e.: curl -vv https://get.helm.sh * Rebuilt URL to: https://get.helm.sh/ * Trying 152.195.19.97... * TCP_NODELAY set * Connected to get.helm.sh (152.195.19.97) port 443 (#0)
- Adrian Escutia Soto
Nov 18, 2021 at 18:50
Last option... TEMPORAL if you trust in the scripts you are using and REMOVE the file after executing the installation stackoverflow.com/a/69933233/5078874
- Adrian Escutia Soto
Nov 19, 2021 at 3:11
Thanks Adrian. would you put your new comments (except the last one) into your answer to make it a whole and integrated answer please? I.e., in order to post to jsonplaceholder.typicode.com behind Zscaler, what are the necessary steps and their orders pls. thx.
- xpt
Nov 19, 2021 at 3:49
////////////////////
Then perform a one-time set up of Bioconda with the following commands. This will modify your ~/.condarc file:

conda config --add channels defaults
conda config --add channels bioconda
conda config --add channels conda-forge
conda config --set channel_priority strict
If you have used Bioconda in the past, note that the recommended configuration has changed over the years. You should run the above commands to ensure your settings follow the current recommendations.
//////////////////