Hi Moso, your problem is not related to this one, this is a Feisty only
problem (7.04) I would guess that it's a problem with your
configuration. I'd suggest reinstalling a clean version of Firehol, and
submit a support request on the forums, or through the answer system.
** Summary changed:
- fi
Hi!
I tried both use bash 3.1 and replace %q strings with %b and none of the
workarounds solved the problem.
FireHOL even appears to be ok, without present error messages, but the firewall
rules aren't correctly implemented.
I read somewhere a post of Costa Tsaousis (FireHOL author) stating that
>From memory, Firehol locks down the system totally as a result of this
bug, so it shouldn't be too critical a problem (unless someone disables
it). The fix from scottmuz sounded good.
jMehdi, can you check that dansguardian etc are installed and working ok
as well? Possbly, check your log files?
A solution that doesn't involve copying bash31 from an edgy system is as
follows:
sudo vi /lib/firehol/firehol (replace vi with you editor of choice)
and replace all %q strings with %b.
This is what they've done in gentoo to solve the problem.
Will we be getting a security fix for this. A broken
I've configured firehol with dansguardian
(http://ubuntuforums.org/showthread.php?t=207008) and changed the /sbin/firehol
script to use bash31. I can now start firehol without errors but the
dansguardian/firehol/tinyproxy configuration doesn't work ; it works if I set
firefox to use directly ti
#90646 is a duplicate of this bug report. Copying my comments there:
What my boss worked out was the following:
Grab the "bash" file from /bin on a Edgy (or dapper) box/install.
Rename this to bash31 and move to /bin on your Feisty box.
Then change the first line of your firehol script (/sbin/
I'd really like to see this get fixed.. Any news?
--
firehol does no longer start
https://bugs.launchpad.net/bugs/78017
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ub
See #90646: firehol does not work with bash 3.2:-(
--
firehol does no longer start
https://launchpad.net/bugs/78017
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ditto on my machine running feisty.
--
firehol does no longer start
https://launchpad.net/bugs/78017
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'll take too Lukas' message as a confirmation;-)
--
firehol does no longer start
https://launchpad.net/bugs/78017
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
OK, I'll take Lukas' message as a confirmation;-)
** Changed in: firehol (Ubuntu)
Status: Unconfirmed => Confirmed
--
firehol does no longer start
https://launchpad.net/bugs/78017
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
Same here. FireHOL is unable to configure iptables correctly in feisty
(everything is OK in both dapper and edgy). With FireHOL's default
configuration it returns following errors and it blocks internet connection
completely:
--
12 matches
Mail list logo
