I believe it much more safer to use group-based access permission. E.g:

# chown .kannel /dev/ttyS0
# chmod ug+rw,o-rwx /dev/ttyS0

If you use Debian default installation, then device file /dev/ttyS0 will
be owned by 'uucp' group. You can easily set your kannel user to be in
'uucp' group, in order to access /dev/ttyS0. E.g:

# adduser kannel uucp
# chmod ug+rw,o-rwx /dev/ttyS0

On Tue, 2003-12-30 at 05:35, Rene Kluwen wrote:
> Without saying anything about whether Kannel, run by root, is secure or not:
> You can either choose that option
> 
> or
> 
> chmod ugo+rw /dev/ttyS0 so ordinary users can also use your modem.
> 
> Rene Kluwen
> Chimit
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
> Nicholas Calugar
> Sent: maandag 29 december 2003 22:34
> To: [EMAIL PROTECTED]
> Subject: Problems with Debian Startup Scripts
> 
> 
> I have Kannel-Devel 1.3.1 installed using the Debian package. I had to
> edit a few lines in /etc/init.d/kannel-devel to start the boxes. I'm not
> exactly sure what this is checking, but I assume it's trying to decide
> whether or not to start the smsbox. As far as I can tell $START_SMSBOX
> is not defined:
> 
>       test ! -z $START_SMSBOX && (
>               .
>               .
>               .
>       )
> 
> Also, this may be more of a Linux user group question: There is an
> argument given to start-stop-daemon:
> 
>       --chuid kannel
> 
> With this argument, the bearerbox doesn't have permission to access the
> GSM Modem I have attached to /dev/ttyS0. Here is info from the
> bearerbox.log:
> 
> 2003-12-29 10:31:17 [0] INFO: AT2[16195192314]: configuration shows
> modemtype <wavecom>
> 2003-12-29 10:31:17 [0] DEBUG: AT2[16195192314]: Reading modem
> definitions from </etc/kannel/kannel.conf>
> 2003-12-29 10:31:17 [0] DEBUG: AT2[16195192314]: Found <1> modems in
> config
> 2003-12-29 10:31:17 [0] INFO: AT2[16195192314]: read modem definition
> for <wavecom>
> 2003-12-29 10:31:17 [0] DEBUG: Started thread 5
> (gw/smsc/smsc_at2.c:at2_device_thread)
> 2003-12-29 10:31:17 [5] INFO: AT2[16195192314]: opening device
> 2003-12-29 10:31:17 [5] ERROR: AT2[16195192314]: open failed! ERRNO=13
> 2003-12-29 10:31:17 [5] ERROR: System error 13: Permission denied
> 2003-12-29 10:31:17 [5] ERROR: AT2[16195192314]: at2_device_thread:
> open_at2_device failed. Terminating
> 2003-12-29 10:31:17 [5] ERROR: System error 13: Permission denied
> 
> If I remove the argument, it starts fine but is run by root. I'm not
> sure if this is a security risk.
> 
> Thanks,
> 
> Nicholas Calugar
> 619-546-9803
> 866-404-2428
> 
> Chatter
> 3577 4th Ave.
> San Diego, CA 92103
> 
> www.2chatter.com
> 
-- 
Regards,
[cogito ergo sum]

GPG fingerprint:
 E2BC 9029 F3FB 90C7 2FAB 9E42 421E F015 119E 0D5D
GPG Public key:
  http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x119E0D5D

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to