Warum ist Samba nicht von Ubuntu nach Manjaro übertragbar

linux-aarhus · 25 December 2022 13:15

I have added the following to Samba Basic Setup and Troubleshotting guide.

Filemanagers

Some file managers implement a Go → Network option.

Screenshot using PCManFM

To make this option usable you need the avahi package synced and services enabled and running. Network Manager depends on Avahi so on Manjaro it is installed but not enabled.

Enable using command (provide password when challenged) or use sudo
systemctl enable avahi-daemon.service avahi-daemon.socket avahi-dnsconfd.

I am available for hire as consultant if you need it

I have no idea what your issue is - because setting up a basic samba service is as simple as it gets.

Of course you need to know how but that is available as well.

I booted a Raspberry Pi using a default Manjaro ARM minimal image - and starting here Install Samba Package

Basic Samba demo installation

Basic installation and configuration

Install samba package

Install the samba package and ensure your system is fully updated in the process.
sudo pacman -Syu samba
Basic Server configuration

Create the configuration file /etc/samba/smb.conf - the folder may need to be created beforehand.
sudo mkdir -p /etc/samba
sudo touch /etc/samba/smb.conf
Edit the file - using superuser privilige - insert below content and save the file (need superuser). If you are connecting an existing network of servers change the WORKGROUP to match the existing network.
[global]
   workgroup = MANJARO
   server string = Manjaro Samba Server
   server role = standalone server
   log file = /var/log/samba/log.%m
   max log size = 50
   guest account = nobody
   map to guest = Bad Password
   
   min protocol = SMB2
   # max protocol = SMB3

[public]
   path = /srv/samba/rpi-share
   public = yes
   writable = yes
   printable = no
Test your config
sudo testparm /etc/samba/smb.conf

Started the service

sudo systemctl enable --now smb

Then I created the shared folder

sudo mkdir -p /srv/samba/rpi-share

I usually don’t images but in this showcase I think they prove my point.

Then I opened my Windows tablet (Windows 11 Pro) - I didn’t enable nmb daemon as I wanted to show off.

Image

Entering the locating of the service - in this case just an ip - you will need to replace with the ip for your system - and I get the list of shares

\\ip.x.y.z

Image

I can open the file I created

Image

The properties of the share tels us it is indeed the MANJARO workgroup

Image

If I try to change the file and save it - I get permission error - and this is to be expected - because even though I have defined the share as writable - the underlying folder has only read permissions.

Back to server side - I can make the file writable

sudo chmod go+w /srv/samba/rpi-share/rpi-share.txt

Then I can edit the file and save the changes

Image

If I try to create a new file in the share - I get permission error once more - again this is expected as the folder is readonly.

Image

Back to server side - I can make the folder writable

sudo chmod go+w /srv/samba/rpi-share

And then I can create a new file

Image

Conclusion

The share I showed off here has become a dangerous share as it has been changed to world writable - just the kind of share ransomware loves.

It is fine for demonstration purpose so a big warning is

NEVER USE SUCH KIND OF SHARE IN PRODUCTION

Settting up a samba server on Manjaro can be straight forward and without issues.