samba - Feb 2024 - Error: Failed to open share info database /var/lib/samba/share_info.tdb

Thanks Rowland,

Am 01.02.2024 10:16, schrieb Rowland Penny via samba:
> On Thu, 01 Feb 2024 08:58:29 +0100
> Bestattungen Vitt - Thomas Reitelbach via samba <samba at
lists.samba.org>
> wrote:
>> I have found a bug on bugzilla which looks similar but with a
>> different topic - but maybe the reason for the bug might be the same:
>> https://bugzilla.samba.org/show_bug.cgi?id=15265
>> 
>> Now we are at the point where I need your help to identify the cause
>> for my problem:
>> a) is it wrong file system permissions on the file, so I should blame
>> debian package maintainers to correct it?
>> b) is there a bug similar to bug no. 15265 as stated above, so I
>> would open a new bug on samba bugzilla
>> c) is it may fault because I have made a configuration error, so I
>> would blame myself and ask you kindly for a hint into the right
>> direction ...
>> 
>> Thank you in advance for your advice :)
>> Thomas
> 
> You may be correct about the reason, but using 'become_root()'
isn't
> really a good idea (in my opinion), it possibly might lead to another
> attack vector.
For sure it might be a attack vector, I'm with you here.
> What I cannot understand is why you feel you need to alter the
'share'
> tab, I never have. It is always (in my experience) set to just
> 'EVERYONE' with 'Allow' Full Control, Change and Read
permissions.
> 
> The tab you need to change is the 'Security' tab and the wiki page
> tells you this.
The reason for setting the share permissions here is the recommendation 
in the wiki, sorry I forgot to include a second link in my initial post:
https://wiki.samba.org/index.php/Windows_User_Home_Folders#Setting_up_the_Share_on_the_Samba_File_Server

I'm following this wiki howto to setup the "Users" Share. This
share
should be used for folder redirection later to hold users personal data. 
As I'm no windows expert I am unsure if I _really_ need those share 
permissions or not.
Anyway, using the Security Tab is working as expected.

Just for information: I have a very old self-compiled samba 4.6.4 
running on a different server. Just to be sure I tested the permissions 
tab settings on a share hosted on this server and it works flawlessly. 
share_info.tdb also has 700 permissions like my brand new debian.

Cheers
Thomas

-- 
Bestattungen Vitt oHG
Inhaber Willi & Thomas Reitelbach
Rochusstra?e 176
53123 Bonn-Duisdorf
Registergericht: Amtsgericht Bonn, HRA 7958

Facebook:     http://www.facebook.de/bestattungenvitt
Gedenkportal: http://begleiten.bestattungen-vitt.de
Internet:     http://www.bestattungen-vitt.de

Telefon: 0228 - 62 68 68
Fax: 0228 - 978 30 36

On Thu, 01 Feb 2024 10:27:36 +0100
Bestattungen Vitt - Thomas Reitelbach via samba <samba at lists.samba.org>
wrote:
> Thanks Rowland,
> 
> Am 01.02.2024 10:16, schrieb Rowland Penny via samba:
> > On Thu, 01 Feb 2024 08:58:29 +0100
> > Bestattungen Vitt - Thomas Reitelbach via samba
> > <samba at lists.samba.org> wrote:
> 
> >> I have found a bug on bugzilla which looks similar but with a
> >> different topic - but maybe the reason for the bug might be the
> >> same: https://bugzilla.samba.org/show_bug.cgi?id=15265
> >> 
> >> Now we are at the point where I need your help to identify the
> >> cause for my problem:
> >> a) is it wrong file system permissions on the file, so I should
> >> blame debian package maintainers to correct it?
> >> b) is there a bug similar to bug no. 15265 as stated above, so I
> >> would open a new bug on samba bugzilla
> >> c) is it may fault because I have made a configuration error, so I
> >> would blame myself and ask you kindly for a hint into the right
> >> direction ...
> >> 
> >> Thank you in advance for your advice :)
> >> Thomas
> > 
> > You may be correct about the reason, but using 'become_root()'
isn't
> > really a good idea (in my opinion), it possibly might lead to
> > another attack vector.
> 
> For sure it might be a attack vector, I'm with you here.
> 
> > What I cannot understand is why you feel you need to alter the
> > 'share' tab, I never have. It is always (in my experience) set
to
> > just 'EVERYONE' with 'Allow' Full Control, Change and
Read
> > permissions.
> > 
> > The tab you need to change is the 'Security' tab and the wiki
page
> > tells you this.
> 
> The reason for setting the share permissions here is the
> recommendation in the wiki, sorry I forgot to include a second link
> in my initial post:
>
https://wiki.samba.org/index.php/Windows_User_Home_Folders#Setting_up_the_Share_on_the_Samba_File_Server
> 
> I'm following this wiki howto to setup the "Users" Share.
This share
> should be used for folder redirection later to hold users personal
> data. As I'm no windows expert I am unsure if I _really_ need those
> share permissions or not.
> Anyway, using the Security Tab is working as expected.
OK, I see what is happening, at one time, Samba didn't know about
'Authenticated Users', 'EVERYONE' and a few others, this has no
been
fixed. I need to update that wiki page.
 
> 
> Just for information: I have a very old self-compiled samba 4.6.4 
> running on a different server. Just to be sure I tested the
> permissions tab settings on a share hosted on this server and it
> works flawlessly. share_info.tdb also has 700 permissions like my
> brand new debian.
Just a suggestion, but 4.6.4 is dead, it had a nice funeral :-) So it
probably would be a good idea to update to a later, supported version
of Samba.

Rowland