"Fossies" - the Fresh Open Source Software Archive

Member "libsafe-2.0-16/EMAIL_NOTIFICATION" (19 Jun 2001, 1768 Bytes) of package /linux/misc/old/libsafe-2.0-16.tgz:

As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 $Name: release2_0-16 $
    2 $Id: EMAIL_NOTIFICATION,v 1.3 2001/06/19 18:22:10 ttsai Exp $
    4 Libsafe-1.3 contained a facility for sending email whenever it detected a
    5 buffer overflow violation.  Several people expressed concerns about the
    6 implementation of the email code, especially since it relied on an external
    7 mail program to send the email.  The overriding concern was that software that
    8 is intended to increase security (such as libsafe) should not present
    9 additional vulnerabilities.
   11 For libsafe-2.0, we considered deleting the email code.  However, we feel that
   12 a notification capability is quite valuable.  After all, most people do not
   13 constantly check their log files.  As a compromise, we have overhauled the
   14 email code and kept the Makefile default of omitting the email code.
   16 The new code tries to establish a direct connection to the SMTP port.
   17 Obviously, some sort of mail agent has to be listening on the SMTP port for
   18 that machine.  No forks, execs, or temporary files are used.  
   20 To use email notification, you have to add -DNOTIFY_WITH_EMAIL to CCFLAGS.
   21 I.e., make line 35 of libsafe/src/Makefile look like
   25 Then do a "make" followed by a "make install".  The recipient of the email is
   26 determined based on the following conditions:
   28     1.	If the file /etc/libsafe.notify exists, then mail is sent to the
   29 	recipients listed in that file.  Each recipient must be listed on a
   30 	separate line.
   31     2.	Otherwise, mail is sent to root@localhost.
   33 Note that the mail transfer agent for the local machine must be configured
   34 properly.  In particular, if any of the recipients are on a different machine
   35 than the local machine, the mail agent must be capable of relaying mail to the
   36 remote machines.