Custom Query (115 matches)
Results (43 - 45 of 115)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#90 | fixed | Debian package vuurmuur-conf fails to build | ||
Description |
The current svn (r243) fails to build a Debian package, using both
The problem with the last few commits is that the Also, the directory to install in is not created, so install might fail when the script directory does not exist at installation time.
The attached patch fixes both of these issues. However, I'm not completely sure this is the right approach. The same |
|||
#89 | fixed | Patch to clean up vuurmuur_fopen | ||
Description |
The attached patch cleans up
The patch is against svn r240. |
|||
#88 | fixed | Add an option to allow {world,group}-readable configuration files | ||
Description |
Currently, vuurmuur insists on its config files not having the group-read and other-read permission bits set (among a few other checks, such as not being writable by others and being owned by root). These checks make sense in general, but for my particular installation I need the files to be readable by world. Currently, vuurmuur resets the permissions of the files when it finds anything out of order.
After a small discussion on IRC it seems feasible to implement an option to prevent the permission changes for files that are readable for group or other. I would propose adding an option " I'm currently looking at the code and plan to submit a patch, probably preceded by some cleanup work in separate patches. |