I am unable to install proxychains on a remote system because the system only has outbound access to port 22/tcp to my server. However, I can use ssh -D 9050 root#myip to listen on port 9050 for socks proxy.
That being said, how can I run apt update and apt install proxychains through socks port 9050 so that I can install proxychains and use it for future commands?
I've tried to run:
export http_proxy=socks5://127.0.0.1:9050 https_proxy=socks5://127.0.0.1:9050
but as soon as I ran apt update, the outbound connection fails. Not sure if this is the correct way to do it or if I'm just missing something small.
One solution I was able to use is by downloading the ZIP version of https://github.com/rofl0r/proxychains-ng, SCP'ing it over to the remote server, and then compiling it locally on that system.
Afterwards, I'm able to use ./proxychains4g -f src/proxychains.conf <command> and so now it looks like I'm good to go.
Related
I'm trying to connect a Raspberry Pi 3 to my VPN.
The VPN server is installed on a pfSense Apliance.
I followed the tutorial on this link to install and configure the VPN on the Raspberry Pi.
However, in place of the firewall files that the tutorial suggests, I put in the "/etc/openvpn" folder a file that I generated through the pfSense interface (.ovpn extension), in the VPN>OpenVPN>Client Export option.
After following all the installation steps and starting the VPN service, I get these errors in the system log:
System Log
First you install openvpn
sudo apt install openvpn
make your openvpn file from your pfsense server (client export)
insert the text inside a file in:
/etc/openvpn/client, like this:
sudo nano /etc/openvpn/client/newfile.ovpn
Also you may autostart openvpn if you like
Edit this file:
sudo nano /etc/default/openvpn
and uncomment, or remove, the “#” in front of
AUTOSTART="all"
When I use the shadowsock's client on windows, and I make it the global agent.
Then, whatever I use Fixfox or chrome, I could get the result I want.
I want to know , how the client make the other software use the Internet through it ? Could someone tell the knowledge about this?
on unix system, using proxychains
intall proxychains
ubuntu
sudo apt-get install proxychains
mac os x
brew install proxychains
from source code
Edit proxychains config
add below line to /etc/proxychains.conf on linux or ~/.proxychains/proxychains.conf on mac
socks5 127.0.0.1 1080 # on linux
socks5 127.0.0.1 1086 # on mac
Don't forget remove remove socks4 if exits
Usage
on linux
proxychains wget https://www.google.com
proxychains google-chrome
on mac
proxychains4 wget https://www.google.com
I am trying to install GitLab on a subdomain. I am not very familiar with web servers and stuff, only very little knowledge. I am currently connected to the subdomain via ssh admin#mysite.com on the Mac's Terminal. Then I ls to the subdomain's folder. Question is if I execute:
curl -O https://downloads-packages.s3.amazonaws.com/centos-6.5/gitlab-7.4.3_omnibus.5.1.0.ci-1.el6.x86_64.rpm
sudo yum install openssh-server
sudo yum install postfix
sudo yum install cronie
sudo service postfix start
sudo chkconfig postfix on
sudo rpm -i gitlab-7.4.3_omnibus.5.1.0.ci-1.el6.x86_64.rpm
on the current folder. Will GitLab be installed or downloaded only in the current folder or will other subdomains and folders of the site be affected?
Is there a way to test yum install first on the current directory?
The Omnibus/RPM version of Gitlab will install gitlab to the /opt/gitlab directory.
If you want to check the files that will be installed by an RPM package you can do so with:
rpm -qlp gitlab-7.4.3_omnibus.5.1.0.ci-1.el6.x86_64.rpm
After you install the RPM with "rpm -ivh gitlab*.rpm" you configure the URL/subdomain using the:
/etc/gitlab/gitlab.rb
file.
After amending the gitlab.rb file you can start gitlab with:
gitlab-ctl start
Or restart it with:
gitlab-ctl restart
You can configure the web address & port that gitlab/nginx listens on using the external_url parameter in the gitlab.rb file:
external_url "https://gitlab.mydomain.com"
If you already have a webserver (such as Apache) using port 80 or port 443 then you might want to ask gitlab/nginx to listen on a port other than 80 or 443 with:
external_url "https://gitlab.mydomain.com:8443"
You can check if anything is listening on particular ports using:
netstat -luntap | grep LISTEN
I'm having a little trouble getting my client to connect. I'm able to have ngrok tell me the port, but when I go to the client and execute:
ssh pairup#ngrok.com -p 57613
I get
ssh_exchange_identification: Connection closed by remote host
Any ideas why this is happening? I'm on a Mac, and I followed these steps: https://www.adaptivelab.com/blog/pair-programming-with-tmux/
Thanks a lot for your time
It could be that you don't have the ssh server installed on the machine you're running ngrok, so, the connection is refused.
To install it just type the following in a terminal:
sudo apt-get install openssh-server
I'm using ssh -D to create a socket proxy and want to know how to use pip(or easy_install) with it? I find this question but that's an http proxy.
Also, please give me a solution works under OS X. (I tried proxifier, it works with pip install, but not sudo pip install)
Easiest method, also works on many OS's:
pip install pysocks
pip install <yourpacakge> --proxy socks5:127.0.0.1:8123
Substitute socks4, and your own ip/port as needed.
Use socks proxifier, for example proxychains.
Command pip will be like proxychains pip install package_name.
Or use another proxifier.
For CentOS, you can use privoxy to convert socks5 proxy to http proxy.
yum install privoxy
Then edit /etc/privoxy/config, at the end of the file, add:
forward-socks5 / 127.0.0.1:1080 .
It will convert socks5 proxy from 1080 to http proxy 8118. Then you can specify the proxy in your pip config file:
[global]
proxy = 127.0.0.1:8118
DO NOT use polipo, as it is already deprecated.
As other users have posted the following works well for using pip via a remote host:
# SOCKS4 proxy creation
ssh -D9999 <remote host URI>
# use pip with the previously created proxy connection (requires pysocks)
python3 -m pip install <package name> --proxy socks5:localhost:9999
Bootstrapping
"But I need pysocks to run pip through a proxy and you can't connect to the pypi to download packages as I don't have functioning pip"
One way to get around this is to download the pysocks wheel package on another machine:
python3 -m pip download pysocks
This will download the pysocks package to your machine. Transfer the PySocks-x-x-x-py3-none-any.whl file to the machine that requires proxy functionality and install:
python3 -m pip install PySocks*.whl
Nevermind, --proxy seems to work with http(s) proxy only.
From "pip --help"
--proxy <proxy> Specify a proxy in the form
[user:passwd#]proxy.server:port.
Edit: I finally gave up sock proxy and run a java http proxy (jhttp2.sourceforge.net/) on my remote machine and use ssh -L port:localhost:port to forward the port to the remote machine and use that http proxy.
Run these two commands:
pip install pysocks5
pip install --proxy socks5://[user:passwd#]proxy.server:port something
first of all you can try install proxychains-ng using
brew install proxychains-ng
the can try make a socks5 proxy using ssh -D like
ssh -D 12345 -fqN root#[your-vps-ip]
and use public-key or password to access your vps
then you have both proxychain and socks5.
Now edit /etc/proxychains.conf , simply add this line at the end of it
socks5 127.0.0.1 12345
and comment this
socks4 127.0.0.1 9050
Finally
proxychains4 pip install [whateveryouwant]
On Windows (mine was Win2012R2) I managed connecting through SOCKS5-proxy by doing those steps:
All-user-level-pip:
Adding this lines to pip.ini under "C:\ProgramData\pip":
[global]
proxy = socks5:{proxy-ip}:{proxy-port}
Opening cmd.exe (maybe but not necessarily as administrator ... depends on your file-system configuration...)
Setting proxy variables to "no-proxy" explicitly!!! ... like that:
set http_proxy=no-proxy
set https_proxy=no-proxy
running for example pip install your_module and finally it works through the socks5-proxy specified in the pip.ini
For user-level-pip you need to place the pip.ini somewhere else according pip-documentation.