Hi Shinichi,

you refence the wrong bug. The problem is described in bug #222384.
postinst sets up wrong init.d links. You can fix it with:

        /usr/sbin/update-rc.d -f mason remove > /dev/null
        /usr/sbin/update-rc.d mason start 41 S . > /dev/null

The bug is fixed in the unstable version but not in the sarge version. I
hope that there will be a security fix for sarge.

The bug #176654 is a different problem.

Christoph

Shinichi Sakata schrieb:
> Please consider including the fix of this bug into the security
> update. I think that this bug can be quite dangerous. The point is
> that many workstations may be running without firewalls because of the
> bug. To make my point clear, let me give you my own story.
> 
> I installed sarge to a few workstations a few days ago. It seemed that
> everything went very smoothly. In setting up the workstations, I
> edited /etc/mason.baserules to my satisfaction, started mason using
> /etc/init.d/mason, and verified that the firewall is up. In a few
> hours, however, I needed to shutdown and reboot the workstations to
> connect them to a UPS that had just arrived. Now, the workstations'
> firewalls were all down, though I was not aware. One day later, the
> system log is filled with a whole bunch of "illegal access" warnings,
> which I had never seen before. 
> 
> I hope that the fix of this bug will be included in the security
> update.

-- 
============================================================================
Christoph Martin, Leiter der EDV der Verwaltung, Uni-Mainz, Germany
 Internet-Mail:  [EMAIL PROTECTED]
  Telefon: +49-6131-3926337
      Fax: +49-6131-3922856

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to