New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow go get from https://*.onion with self-signed certificates #41076
Comments
Using |
Looks like something strange happening: now I've modified above script so: export all_proxy="socks5://127.0.0.1:9050"
export http_proxy=$all_proxy
export https_proxy=$all_proxy
ONION_DOMAIN='someonion.onion'
export GOINSECURE=$ONION_DOMAIN
#export GOPRIVATE=$ONION_DOMAIN
#export GONOPROXY=$ONION_DOMAIN
#export GONOSUMDB=$ONION_DOMAIN
"$@" I've saved it to as You asked about environment:
GOINSECURE=someonion.onion
GONOPROXY=someonion.onion
GONOSUMDB=someonion.onion
GOPATH=/home/animuspexus/gopath_main:/home/animuspexus/gopath_work
GOPRIVATE=someonion.onion
GOROOT=/usr/lib/golang
all_proxy=socks5://127.0.0.1:9050
http_proxy=socks5://127.0.0.1:9050
https_proxy=socks5://127.0.0.1:9050
|
What's the output of |
without --insecure
with --insecure
|
This is not the go tool erroring out, the go tool can reach the HTML page, which points it to Not sure why |
thanks, I'll look into this. ~/if/soxy go env
|
Ah, GOINSECURE only works in module mode, while you might still be using GOPATH here. I think the go tool is working as intended, and you need to resolve your issue with git. |
If somebody interested, I've managed this working git simply requires this in config:
also I used following script to run go programs over tor (note: GOINSECURE and GOPRIVATE not needed if go modules not used): #!/bin/bash
export all_proxy="socks5://127.0.0.1:9050"
export http_proxy=$all_proxy
export https_proxy=$all_proxy
"$@" also I used ~/.netrc file to provide http username:password |
For some reasons I can not use clearnet for some of My golang packages.
So I'm trying to host my packages using gitea and tor hidden services.
calling
results in x509: certificate signed by unknown authority
server hosts self-signed certificate
probably it is ok to allow serf-signed .onion certificates for golang packages hosts
also, trying to use --insecure flag, result in
Could not resolve host
errorThe text was updated successfully, but these errors were encountered: