...solved. AppArmor. GRRR. I WISH WE HAD SELINUX INSTEAD. That I would be able to use. Cheers MH On 09.07.2019 21:03, Mathias Homann wrote:
Oh, before I forget, I can access all other samba shares in the way they are intended to be used.
Here's the [global] and [homes] part of smb.conf:
[global] domain master = Yes interfaces = eth0 tun0 logon drive = P: logon home = \\%N\%U local master = yes map to guest = Bad User os level = 65 preferred master = Yes printcap name = cups security = USER usershare allow guests = Yes wins support = Yes workgroup = EREGION catia:mappings = 0x22:0xa8,0x2a:0xa4,0x2f:0xf8,0x3a:0xf7,0x3c:0xab,0x3e:0xbb,0x3f:0xbf,0x5c:0xff,0x7c:0xa6 idmap config * : backend = tdb cups options = raw mangled names = no
[homes] browseable = No comment = Home Directories inherit acls = Yes read only = No vfs objects = catia
On 09.07.2019 20:58, Mathias Homann wrote:
Hey there,
behold:
lemmy@akari:~> df -h . Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf /dev/mapper/system-users 252G 150G 91G 63% /users/lemmy lemmy@akari:~> smbclient -U lemmy //akari/lemmy Enter EREGION\lemmy's password: Try "help" to get a list of possible commands. smb: \> ls NT_STATUS_ACCESS_DENIED listing \* smb: \>
in other words, I can not access my own home via samba anymore.
And here are the two dreaded sentences: "It used to just work" and "I didn't do anything".
In this particular case, both are true - I literally havent touched my samba config for years, and it used to work just fine until a few days ago.
No, no samba updates, either.
Running samba-4.7.11+git.153.b36ceaf2235-lp150.3.14.1.x86_64 on openSUSE Leap 15.0, the package's from the Leap 15.0 updates repo.
Any ideas on where to start?
Cheers
MH
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org