A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Write for DigitalOcean
You get paid, we donate to tech non-profits.
Find and meet other developers in your city.
Contribute to Open Source
Tables firewall d
iptables is a packet filter, or firewall in common terms. And yes, that is what you need in order to allow or deny traffic from reaching your server. There’s no “securing” packets per se, as iptables does nothing to the packet content (it does not encrypt/decrypt).
iptables management is a faily large subject, I suggest you get yourself some reading material.
This is a good starting primer :
Add comments here to get more clarity or context around a question. To answer a question, use the “Answer” field below.
Iptables for securing the packets is that right
IPTables does secure your server, you can create all kind of different configurations wich will provide you security in different sections. But mainly its a firewall for network traffic (Ports, IP’s etc.)
Now i understand about IPTables
You can type !ref in this text area to quickly search our full set of tutorials, documentation &
marketplace offerings and insert the link!
Hi i use cs-cart and i dont now a lot of things in server managment. How to ensure the security of the server.
I recently came across digital ocean and I am really interested to move my website over, I always hosted my websites on shared server where i can use cpanel.
My Question is do i need to worry about security and install firewall or digitalocean takes care of all the security? I am asking about server security and not code security.
Hi , I cannot remote ssh to my droplet, only from within the digitalocean web based ssh client. I am also using webmin and openvpn.
I get from osx
ssh: connect to host 178.x.x.x port 22: Connection refused
I have port 22 open with UFW inbound and outbound with tcp or udp
do i need to specify the external IP or have I broken something by trying to make RSA keys for login ?
My other services are working well, only ssh seams to have a problem. Any ideas would be much welcomed.
here is my ssh_config
# Package generated configuration file
# See the sshd_config(5) manpage for details
# What ports, IPs and protocols we listen for
# Use these options to restrict which interfaces/protocols sshd will bind to
# HostKeys for protocol version 2
#Privilege Separation is turned on for security
# Lifetime and size of ephemeral version 1 server key
systemctl reload sshd
# Don't read the user's ~/.rhosts and ~/.shosts files
# For this to work you will also need host keys in /etc/ssh_known_hosts
# similar for protocol version 2
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
# To enable empty passwords, change to yes (NOT RECOMMENDED)
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
# Change to no to disable tunnelled clear text passwords
# Kerberos options
# GSSAPI options
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
Subsystem sftp /usr/lib/openssh/sftp-server
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
# Added by DigitalOcean build process
# Configured 20160504
**I am accessing DigitalOcean Spaces with the help of AWS SDK**. I am able to connect and upload file to the Spaces bucket. I'm uploading a directory with recursive directories and files using 'TransferManager.uploadDirectory()' method. Is there a way to set permission as public as a part of uploading instead of iterating and setting individual object permission in another API call.
But I want to set permission of all files which I'm uploading as 'public'. By default it is 'private'.
I tried using AWS bucket policy .. but it is not supporting in DO Spaces.
Also everytime I upload files to that particular bucket, I want all those files to be public.
*Kindly help me with this. I'm searching for a generic solution. I'm not getting any way around.*