Apcupsd Bugs

Apcupsd Version 3.8.5 Bugs

Apcupsd Version 3.8.4 Bugs

Apcupsd Version 3.8.3 Bugs

Networking may not work in a mixed vendor setup

./configure --with-nis-port=7000 --with-net-port=6666

Unusual Case of Apcupsd Hanging during Boot

Apcupsd Version 3.8.2 Bugs

The Lock Directory in the Solaris is Incorrect

--- distributions/sun/old.apcupsd.in    Sat Jul  7 10:20:30 2001
+++ distributions/sun/apcupsd.in        Sat Jul  7 10:18:59 2001
@@ -17,7 +17,7 @@
         rm -f @PWRFAILDIR@/powerfail
         echo "Starting apcupsd power management ...\c"
         @sbindir@/apcupsd || return="  Failed."
-        touch /var/lock/apcupsd
+        touch @LOCKDIR@/apcupsd
         echo "$return"
     ;;
     stop)
@@ -29,7 +29,7 @@
         else
                 return=" Failed."
         fi
-        rm -f /var/lock/apcupsd
+        rm -f @LOCKDIR@/apcupsd
         echo "$return"
     ;;
     restart)

Solaris doesn't Shutdown

examples/safe.apccontrol has bad wall command

Networking does not work in a mixed vendor setup

./configure --with-nis-port=7000 --with-net-port=6666

Unusual Case of Apcupsd Hanging during Boot

Apcupsd Version 3.8.1 Bugs

As the bugs become known to us, we will post them here with any possible fixes or workarounds that we have.

Apcupsd may Hang when Attempting to Initialize the Serial Port

       if ((ups->fd = open(ups->device, O_RDWR | O_NOCTTY | O_NDELAY)) < 0) {
                Error_abort2(_("Cannot open UPS tty %s: %s\n"),
                                        ups->device, strerror(errno));
        }
        /* Cancel the no delay we just set */
        cmd = fcntl(ups->fd, F_GETFL, 0);
        fcntl(ups->fd, F_SETFL, cmd & ~O_NDELAY);

@@ -77,18 +81,21 @@
                 Error_abort0(_("Serial port already initialized.\n"));
        }
 
-       /* Open the the device */
-       if ((ups->fd = open(ups->device ,O_RDWR | O_NOCTTY )) < 0) {
+       /* Open the serial port device */
+       if ((ups->fd = open(ups->device, O_RDWR | O_NOCTTY | O_NDELAY)) < 0) {
                 Error_abort2(_("Cannot open UPS tty %s: %s\n"),
                                        ups->device, strerror(errno));
        }
+       /* Cancel the no delay we just set */
+       cmd = fcntl(ups->fd, F_GETFL, 0);
+       fcntl(ups->fd, F_SETFL, cmd & ~O_NDELAY);

Version 3.8.1 May Cause Networking Problems on Win95

STATUS Output for BackUPS Pro and SmartUPS VS Incorrect

            } else {
                      s_write("LINEFAIL : DOWN\n");
                      if (ups->BattLow == 0) {
                              s_write("BATTSTAT : RUNNING\n");
                              ups->Status = UPS_ONBATT;
                      } else {
                              s_write("BATTSTAT : FAILING\n");
                              ups->Status = UPS_BATTLOW;
                      }
              }
              s_write("STATFLAG : 0x%02X Status Flag\n", ups->Status);
              break;                                       <=========== delete this line
           case NBKPRO:
           case SMART:
           case SHARESMART:
           case MATRIX:
              if (ups->UPS_Cap[CI_IDEN]) {
                      s_write("UPSNAME  : %s\n", ups->name);
              } else {
                      s_write("UPSNAME  : N/A\n");
              }

@@ -158,7 +158,7 @@
                      }
              }
               s_write("STATFLAG : 0x%02X Status Flag\n", ups->Status);
-             break;
+             /* Note! Fall through is wanted */
           case NBKPRO:
           case SMART:
           case SHARESMART:

Automatic Self Test is Reported as Power failure

Improper Shutdown of Apcupsd on WinNT Systems

Name Resolution Does Not Work on Win32 Systems

The apccontrol Script Doesn't Work with All User Scripts

      ${SCRIPTSHELL} ${SCRIPTDIR}/${1}

      ${SCRIPTDIR}/${1}

Denial of Service Security Problem

I noticed that its (apcupsd's) handling of temp files during e-mail notification was prone to denial-of-service attacks. I found this vulnerability within these scripts found in the /etc/apcupsd directory in the above RPM:

        changeme
        commfailure
        commok
        mainsback
        onbattery

Since the notification scripts blindly write to a $$-selected /tmp filename, any user on the box could cause root to overwrite any file on the system (/etc/passwd, /boot/vmlinuz) with the UPS error message by making lots and lots of /tmp/apcupsd.onbattery.##### symlinks which point to the victim file and wline option for apcaccess allows you to examine the current values of your UPS' EPROM as well as to know the permitted values that can be set in the EPROM. For information about changing these values, see the section on Apcupsd EEPROM Configuration.

A typical output from apcaccess eprom is:

Valid EPROM values for the SMART-UPS 1000

                         Config        Current  Permitted
Description              Directive     Value    Values
===================================================================
Upper transfer voltage   HITRANSFER    253      253 264 271 280 
Lower transfer voltage   LOTRANSFER    208      196 188 208 204 
Return threshold         RETURNCHARGE  15       00 15 50 90 
Output voltage on batts  OUTPUTVOLTS   230      230 240 220 225 
Sensitivity              SENSITIVITY   H        H M L L 
Low battery warning      LOWBATT       2        02 05 07 10 
Shutdown grace delay     SLEEP         180      020 180 300 600 
Alarm delay              BEEPSTATE     T        0 T L N 
Wakeup delay             WAKEUP        60       000 060 180 300 
Self test interval       SELFTEST      336      336 168 ON  OFF 

./usr/share/doc/apcupsd/manual/bugs.html0100644000000000000000000004124407415303247017146 0ustar rootroot