>At 06:00 PM 3/14/99 -0800, you wrote:
>>Anyone know who checkpassword runs as? Isn't it the user?
>
>No. It typically runs as root. It switches to the user and only root can do
>that. You nominate the uid that it runs as on your tcpserver invocation.
>What have you got there?
>
>>If so, any ideas on how to modify a tcp.smtp file after checkpassword
>>succeeds? Only way I see to do it is open up permissions on the file,
which
>>doesn't help when running tcprules (resets them).
>>
>>my modified checkpassword auths the user then execl()'s a script to add
>>$TCPREMOTEIP to the tcp.smtp file if it does not exist.
>
>Right. At that point the process is running as the user. If you want to
>modify the file directly, all those users will need to have write access to
>the file directly.
>
>Another strategy might be to write TCPREMOTEIP to a temp file in a
directory
>that everyone has write access to, and have a separate cronjob/process scan
>the directory adding entries into tcp.smtp.
>
>The execl() script could be as simple as "touch /var/sometmp/$TCPREMOTEIP".
>E&OE.
>
>
>Regards.
>
>
