asterisk users - Feb 2006 - Rights problem with Voicemail and non-root user - yeah I know, I thought I had it fixed...

Hi,

I thought I had this problem licked but there still is a rights problem 
with ARI and Asterisk when using a non-root user (Following the wiki at 
http://www.voip-info.org/tiki-pagehistory.php?page=Asterisk+non-root&diff2=25).
When I issue the following:

chmod --recursive u=rwX,g=rX,o= /var/spool/asterisk

The above command results in the following rights on messages:

msg0000.gsm    rwxr-x---       asterisk
msg0000.txt    rw-r-----       asterisk
msg0000.wav    rwxr-x---       asterisk

I can transfer voicemails and play them but new messages comming in get 
the following:

msg0000.gsm    rwx------       asterisk
msg0000.txt    rw-r--r--       asterisk
msg0000.wav    rwx------       asterisk

After changing the rights a transferred messages has the folowing rights:

msg0000.gsm    rw-r-----       apache
msg0000.txt    rw-r-----       apache
msg0000.wav    rw-r-----       apache

New voicemail cannot be played, deleted or transferred by the ARI 
application. Apache is belongs to the Asterisk group. I thought I 
understood SUID, GUID and sticky bit now I am not so sure. What is 
really confussing to me is why the rights on the .txt file do not match 
the other 2 after running the 'chmod --recursive ...' command. Any help 
here would be greatly appreciated. I am using the lastest versions of 
Asterisk 1.2.4 and Zaptel 1.2.3, etc.

Thanks

Hi Chuck.

I had the same problem.
I solved it using the externnotify parameter inside voicemail.conf.
Just launch a script which changes the /var/spool/asterisk permissions.

Giorgio Incantalupo


Chuck Bunn wrote:
> Hi,
>
> I thought I had this problem licked but there still is a rights 
> problem with ARI and Asterisk when using a non-root user (Following 
> the wiki at 
>
http://www.voip-info.org/tiki-pagehistory.php?page=Asterisk+non-root&diff2=25).
> When I issue the following:
>
> chmod --recursive u=rwX,g=rX,o= /var/spool/asterisk
>
> The above command results in the following rights on messages:
>
> msg0000.gsm    rwxr-x---       asterisk
> msg0000.txt    rw-r-----       asterisk
> msg0000.wav    rwxr-x---       asterisk
>
> I can transfer voicemails and play them but new messages comming in 
> get the following:
>
> msg0000.gsm    rwx------       asterisk
> msg0000.txt    rw-r--r--       asterisk
> msg0000.wav    rwx------       asterisk
>
> After changing the rights a transferred messages has the folowing rights:
>
> msg0000.gsm    rw-r-----       apache
> msg0000.txt    rw-r-----       apache
> msg0000.wav    rw-r-----       apache
>
> New voicemail cannot be played, deleted or transferred by the ARI 
> application. Apache is belongs to the Asterisk group. I thought I 
> understood SUID, GUID and sticky bit now I am not so sure. What is 
> really confussing to me is why the rights on the .txt file do not 
> match the other 2 after running the 'chmod --recursive ...'
command.
> Any help here would be greatly appreciated. I am using the lastest 
> versions of Asterisk 1.2.4 and Zaptel 1.2.3, etc.
>
> Thanks
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>

Hi,

Just so I am clear this patch will work with 1.2.4 and requires manual 
updating to files and then a recomplie of Asterisk source correct??

Thanks


Ben Klang wrote:
>Hello,
>
>I found the same problem very frustrating, mostly because it causes Asterisk
>to ignore ACLs and umask settings.  If you are interested I have a patch 
>submitted as Digium bug 6334 at http://bugs.digium.com/view.php?id=6334.  
>This patch resolved the issue for me.
>
>Regards,
>/BAK/
>  
>

Hi,

Could you post the updated patch for 1.2.4

Thanks

Ben Klang wrote:
>On Thursday 16 February 2006 11:47, you wrote:
>  
>
>>Just so I am clear this patch will work with 1.2.4 and requires manual
>>updating to files and then a recomplie of Asterisk source correct??
>>    
>>
>This patch was written against trunk a couple weeks ago.  Last night I
applied
>it to 1.2.4 and there were only two small conflicts (easily resolved).  
>Recompile and install Asterisk.  You may need to manually poke existing
files
>to get the perms the way you like but all new files should be created 
>correctly.
>
>If you're having trouble getting it to apply to 1.2.4 let me know and
I'll
>send you my rebuild patch.  If you happen to be a SuSE user I've got
Asterisk
>1.2.4 RPMs built for SuSE 10.0.
>
>/BAK/
>
>
>
>
>  
>