The mailing list for listmasters using Sympa

["Stefan Hornburg (Racke)" <address@concealed>]

On 8/8/19 6:45 AM, Thomas Scheffczyk wrote:
> On 07.08.19 um 14:36 Kissman, Paul (BLC) wrote:
>>
>> I don’t know if this will help at all, but I have setuid on my 
>> sympa_newaliases-wrapper
>>
>>  
>>
>> However, I also have sympa owning both sympa_aliases and sympa_aliases.db
>>
>>  
>>
>> -rw-r--r-- 1 sympa sympa 49152 May  6 11:31 sympa_aliases.db
>>
>> -rw-r--r-- 1 sympa sympa 30414 Feb 26 13:26 sympa_aliases
>>
>>  
>>
>>  
>>
> On 08.08.19 um 01:02 Steve Shipway wrote:
> 
>> Could it be a missing suid bit, or incorrect ownership, on 
>> sympa_newaliases-wrapper ?
>>
> Hi,
> 
> thank you for your answers. :-)
> 
> The suid bit was set and sympa_newaliases-wrapper was owned by root. 
> Changing the ownership of the aliases file did not
> solve the problem. but downgrading Sympa to 6.2.42 did.
> 
> Upgrading Sympa to 6.2.44 without any other modifications introduced it 
> again so that I assume that there is a bug in
> 6.2.44 or - more probable - that I did not read the release information 
> carefully enough. ;-)

Hello Thomas,

6.2.44 introduced a change of the location of the lock file for the alias file
(https://github.com/sympa-community/sympa/pull/593).

The problem might the permissions of the directory and not of the alias file.

Regards
        Racke


> 
> I will post it here when I found the cause of the problem.
> 
> Best regards
> 
> Thomas
> 
> -- 
> 
> --------------------------------------------------------------------------
> Mail  address@concealed  Johannes Gutenberg-Universität Mainz
> Tel.  +49 6131 39 26399               Zentrum für Datenverarbeitung
> GnuPG B84D 8BE9 6F5C A832 60A2        Anselm-Franz-von-Bentzel-Weg 12
>       41C0 C483 76EB AA49 FA72        55128 Mainz
> 


-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.

Attachment: signature.asc
Description: OpenPGP digital signature