I just installed fedora 9 and finally got everything working. I configured my router to assign static ip to this box (i guess i don't have to install ddclient) I have a dyndns.com account and set my dns name to the static ip I mentioned to this box.

Could anyone please indicate me how to make my fedora box a home server so I can telnet or use ssh and ftp to my home server?

Dani AI

Generated

Good follow-up from and a useful prompt from . With the host already reachable externally, the most valuable next steps are practical hardening and safe file transfer rather than more exposure. The short checklist below focuses on making remote access reliable and lowering the blast radius if credentials are discovered.

Key SSH hardening (concise):

  • Prefer key-based auth and remove password login for interactive shells.
  • Disable direct root login and limit which accounts can connect.
  • Use modern key types (ed25519 or strong RSA) and consider changing the default port only as noise reduction.
  • Add automated lockout (fail2ban or firewall rate-limits) to slow brute-force scans.

Recommended sshd snippets (add to /etc/ssh/sshd_config):

PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes
PermitEmptyPasswords no
# optional: Port 2222
AllowUsers alice bob

File-transfer and isolation:

  • Avoid plain telnet and FTP over the Internet (credentials travel unencrypted). Use SFTP (built into OpenSSH) or FTPS if an FTP server is required.
  • Chroot SFTP users to a minimal directory and force SFTP so shells aren't exposed.

Examples (create keys and SFTP chroot):

ssh-keygen -t ed25519 -C "admin@example"
ssh-copy-id -i ~/.ssh/id_ed25519.pub alice@host.example
# sshd_config: use internal-sftp and a Match block for a sftpusers group

Quick troubleshooting and hygiene:

  • Use ssh -v (or -vvv) to see handshake details when a connection fails.
  • Inspect SSH logs (e.g. /var/log/secure or /var/log/auth.log; on systemd hosts journalctl -u sshd) for rejects and fingerprint mismatches.
  • Keep the OS and OpenSSH packages current, rotate keys if a compromise is suspected, and apply the minimum privileges principle to all accounts.

Apparently this issue has been solved, presumably marked so by yourself. Could you please post up what the solution was so that others can learn?

sure i can. it was actually easier than I thought. To do that I had to register for a domain name, and set my domain name to the static ip representing my server. (I configured my router earlier to give a static ip to this specific box every time it reboots) Then everything follows, all i had to do to try this out is to open up my ssh or telnet, and enter the domain name , username, password and then login.

one more thing is you might need to open up ssh , telnet, and ftp ports so remote pc can come in the server through the specific port.

hope that helps ppl trying to learn like me ==*

commented: V helpful post +5

Yea that's cool. Cheers

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.