Seup and Document server #480
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#480
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is mainly meant to be a quick summary and description of the hosting server configuration as it is being set up.
For password or other details, please contact @c24elipe
Document server setup!to Seup and Document serverI have updated the SSH port to instead be on port 2222 (This port was chosen because it is an alternative port for SSH)
Why?
I did this to be able to block the 22 (SSH default port) since this port is often attacked by bots and similar threats that look for insecure SSH setups. This is not much safer against a human (who can scan for open ports), but slightly safer against automatic attacks that look for attack vectors.
To change this back, look at "/etc/ssh/sshd_config"
OBS, make sure the new port isn't blocked by the UFW firewall!
I then followed the docker install documenation found at https://docs.docker.com/engine/install/ubuntu/
Docker compose is then inlcuded.
Then node was installed using the offical website:
http://nodejs.org/en/download
To install the dotnet dependencies, I used the official Microsoft guide:
https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu-install?tabs=dotnet10&pivots=os-linux-ubuntu-2204
Copied over public key using ssh-copy-id,
and set the following for exsta security.
PermitRootLogin no
StrictModes yes
PasswordAuthentication no
PermitEmptyPasswords no
X11Forwarding no
Now the private key is needed to log in
I then enable UFW (the firewall) with a single rule: ufw allow 2222.
Also ran:
ufw default deny incoming
ufw default allow outgoing
The plan is to poke holes for the frontend later
I have not set a root password.
For it, ask me, or Henrik (I will tell him later during our meeting)
This implementation looks solid. The use of SSH key authentication, disabling password login, and configuring the firewall with a default deny policy are all good security practices. Also using official documentation is reliable and correct.
The updated SSH port to 2222 instead of 22 is a security through obscurity approach. This can help against automated bot attacks but can not be a strong protection on its own. It does not help as much against targeted attacks. it is used good In this implementation as it is used with a stronger security messearue such as ssh keys.
Overall this is a good initial setup. This would be stronger with the addition regular system updates as it is important for the system to patch security vulnerabilities.
@a24danwe this issue can be close?
Yes!