Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have a machine running an ftp server and I'd like to access it from a machine located on another network behind a router only authorizing port 80.
I was thinking of a ssh tunnel like:
ssh -L local_port:${ftphost}:20 user#{sshhost}
Where ${sshhost} is another machine that have access to the ftp server ${ftphost}.
${sshhost} is reachable from my host while ${ftphost} is only reachable from ${sshhost} not mine.
Would that be the best solution ?
The O'Reilly Book "SSH, The Secure Shell: The Definitive Guide" contains a whole chapter about FTP Forwarding.
I think that should answer all of your questions.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I opened a PostgreSQL port by adding a line in /etc/postgresql/10/main/pg_hba.conf
host mydatabase myuser my_ip_adress/32 md5
and then opening the port like this:
sudo ufw allow 5432/tcp
Is this secure enough? Our should I also limit the IP adresses for port 5432 in ufw / iptables?
"Secure enough" depends a lot on your requirements.
I would say that that is good enough for normal purposes. An easy improvement would be to use scram-sha-256 instead of md5 (don't forget to change the password_encryption parameter and set a new password).
If your database contains the secret algorithm that the NSA uses to break TLS encryption, you might want to use a different authentication method like Kerberos that uses central identity management rather than database passwords.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I want to change the Kubernetes server endpoint port.
I am currently using port 6443 and would like to change it to port 7443.
Kubernetes is installed on-premises and is a single master node.
You can change the default secure port by passing the --secure-port flag when you start your k8s api server.
Checkout the next links for more:
https://kubernetes.io/docs/reference/access-authn-authz/controlling-access/#api-server-ports-and-ips
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Improve this question
I have a small sample application which send some data to the server and close the connection afterwards. I ran it on my localhost as server & client and it worked.
When I ran the same code after changing the IP to another host(running Cent OS in VM) as server and my client (Ubuntu), I get the following error from client binary.
client.c : 47 Error connection to remote machine
139915881411416:error:02002071:system library:connect:No route to host:bss_conn.c:246:host=192.168.56.101:6001
139915881411416:error:20073067:BIO routines:CONN_STATE:connect error:bss_conn.c:249:
I am able to ping the remote server from my terminal. Any suggestions or solutions are welcome :) .
Actually the problem was because of firewall running on server(Cent OS). After stopping the firewall using command,
service iptables stop
the client was able to make a connection with the server.
Better Solution (without stopping firewall):
Add your client's IP address in the iptables so that it will allow the client to connect to your server without stopping firewall.
iptables -I INPUT -s <client_ip_address> -j ACCEPT
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Im trying to excute few perl script but it just spit the code ..
I know perl script should be in cgi-bin but my host is www.something.com:8080 which consist of my website (mostly jsp) .. do i have to create another cgi-bin in 8080 !!?
help!!
IIRC, 80 is the default port for web servers. 8080 is one your system admin set up. The problems could be: 1) the web server is not configured to run on that port; 2) the server is not running on that port; 3) the server is not configured to handle CGIs on that port.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I have configured ejabberd server on localhost. I am able to connect to local host like admin#localhost, but i am not able to connect gtalk server. Some one please help me how to connect to gtalk server.
Thanks in advance,
sathi
In order for you to talk to GoogleTalk, they have to be able to talk back to you using Dialback. There are several steps you'll need to do:
Rename your server to a fully-qualified domain name. (e.g. example.com)
Open a hole in your firewall in both directions to your server on port 5269/tcp.
Add an SRV record to your DNS pointing at that firewall hole. If your domain was example.com, your SRV might have _xmpp-server._tcp.example.com pointing to 10 0 5269 myserver.example.com.
At some point in the future, you may also need an X.509 certificate for doing TLS.
I almost lost hope, but this thread was really helpful:
Short summary - disable google apps for domain, it can be the reason of getting 404 errors in ejabberd log.