Bugs and bug reports -------------------------------------------- Bug reports should be sent to the appropriate list or forum (see http://sourceforge.net/forum/?group_id=136514). Here are some possible signs of a sysmask bug, listed in decreasing order of seriousness. * Daemon crash. On a system will fully deployed sysmask, a crash of smkd will lock up the whole system. Often a hard reboot is the only solution. * umount failure. When you shut down the system, one or several partitions cannot be umounted. This means memory leak in the kernel, therefore a potential vulnerability for DoS attacks. Must be debugged. * Race condition management in the kernel codes of sysmask. A bug in this management may have many different appearances. * Mask implementation error. A system call supposed to be closed by a mask is left open, or vice versa. More often it is a documentation error. * Token / mask management error. Wrong masks are attributed to a given token, when token switching takes place. The probability is very low. * File access check design error. This is the case if an unforseen method allows the process to bypass a file access control. * Erroneous file access check. This may lead to possible loopholes, but at most of the times, it is simply a human configuration error. It is a bug only if a specially crafted pathname allows the process to bypass the access control. * Erroneous socket access check. There are known bugs for local sockets. * Bugs in overflow management. For example, when one of the configuration files is of unusually large size or has unusually many lines or blocks, or is constantly regenerated at an extremely rapid pace, or contains a special syntax error. Such a bug will affect the normal work of smkd. * Possible bugs in the utility /bin/sysmask. Such bugs do not affect the security of the system. They only bring about usage inconveniences.