Difference between revisions of "SAMBA Cross-Domain Trust File Server"

From Michael's Information Zone
Jump to navigation Jump to search
Line 20: Line 20:
 
*Install kerberose and related packages.
 
*Install kerberose and related packages.
 
<pre>
 
<pre>
−
sudo yum install -y realmd krb5-workstation oddjob oddjob-mkhomedir sssd samba-common
+
sudo yum install -y realmd krb5-workstation oddjob oddjob-mkhomedir sssd samba-common samba-common-tools
 
</pre>
 
</pre>
 
<ref>https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member</ref>
 
<ref>https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member</ref>

Revision as of 09:44, 13 January 2020

Purpose

Existing file server is not configured properly. Will be moving this non-critical data to a new server running in AWS. Since I can live with some downtime if needed, it is much cheaper to use a small AWS instance than to use the expensive Windows based file service AWS offers.

Host

Host is t3a.small CentOS7 instance running on EC2. At the time of this writing CentOS8 is not available on the AWS store.
Though not a critical system, it will be holding sensitive data and I want native SELinux.

Config

Work in progress

  • Prep base OS with automatic updates and a firewall. Make sure to edit the yum-cron config to install security only, and to install updates after downloading.
sudo yum install epel-release yum-cron firewalld
sudo systemctl enable --now firewalld
sudo systemctl enable --now yum-cron
  • Set host name and reboot.
sudo hostnamectl set-hostname myfileserver
sudo reboot -h now
  • Install kerberose and related packages.
sudo yum install -y realmd krb5-workstation oddjob oddjob-mkhomedir sssd samba-common samba-common-tools

[1]

  1. ↑ https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member
Retrieved from "https://wiki.1701technology.com/index.php?title=SAMBA_Cross-Domain_Trust_File_Server&oldid=1331"