Hmmm, they do not work:
$> openssl s_client -connect api.snapcraft.io:443
139827700959040:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
139827700959040:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
139827700959040:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
139827700959040:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
139827700959040:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
139827700959040:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
139827700959040:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
139827700959040:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
139827700959040:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
139827700959040:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
139827700959040:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
139827700959040:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
connect:errno=111
$> openssl s_client -connect 91.189.92.38:443
140073447827264:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
140073447827264:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
connect:errno=111
Since most of my connectivity issues on this host end up having to do with the proxy it is behind and the various ways the host needs to be configured to use it, I went looking to see how to get openssl to use a proxy. It doesn’t seem to look to environment variables such as HTTPS_PROXY. I did find that I was able to get a connection by using proxytunnel:
$> proxytunnel -d 91.189.92.38:443 -a 7000 &
[1] 39561
$> openssl s_client -connect localhost:7000
CONNECTED(00000003)
Can't use SSL_get_servername
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = api.snapcraft.io
verify return:1
...output snipped...
Does snap use openssl-like commands to get at api.snapcraft.io? If so, then I am fairly sure that the proxy configuration is the issue. Is there a way to configure snap to use a proxy? Alternatively, is there a way to use a solution like proxytunnel?
Thanks again!