Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.security > #156
| Newsgroups | comp.os.linux.networking, comp.os.linux.security, comp.os.linux.setup |
|---|---|
| From | JohnnyLately <JohnnyLately@nowhere.invalid> |
| Subject | Re: Is Guarddog incompatible with Kernel v3.2.0? |
| References | <_LedneOnhsszCHjNnZ2dnUVZ_tOdnZ2d@earthlink.com> |
| Followup-To | comp.os.linux.setup |
| Message-ID | <20130103111416.51@0.0.0> (permalink) |
| Organization | TeraNews.com |
| Date | 2013-01-03 16:44 +0000 |
Cross-posted to 3 groups.
Followups directed to: comp.os.linux.setup
["Followup-To:" header set to comp.os.linux.setup.]
On 2013-01-03, Ant <ANTant@zimage.com> wrote:
> Hello.
>
> I think my Guarddog program is not running/working anymore (e.g., no
> blockages shown in dmesg logs) after upgrading Kernel v2.6.32 to v3.2.0)
> recently. I tried to check its frontend GUI software as root/sudo, but
> it failed:
>
> $ guarddog -v
> Qt: 3.3.8b
> KDE: 3.5.10
> Guarddog: 2.6.0
>
> # guarddog
> No protocol specified
> guarddog: cannot connect to X server :0.0
> ICE default IO error handler doing an exit(), pid = 31229, errno = 11
>
> It works with regular user, but I don't see my custom settings and
> change anything. Is it incompatible with the latest Kernel version? If
> so, then is there a replacement for it?
>
> Thank you in advance. :)
You need to patch two files in src
and recompile guarddog to use it with that kernel.
The guarddog.cpp and guarddogdoc.cpp files must be edited/patched.
Look for the sections in both files that look like below:
(about line 2910 in guarddog.cpp and about line 603 in guarddogdoc.cpp)
# Check for iptables support.
if [ -e /proc/sys/kernel/osrelease ]; then
KERNEL_VERSION=`sed "s/^\([0-9][0-9]*\.[0-9][0-9]*\).*\$/\1/" < /proc/sys/kernel/osrelease`
if [ $KERNEL_VERSION == "2.6" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "2.5" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "2.4" ]; then
if [ -e /sbin/iptables ]; then
FILTERSYS=2
fi;
if [ -e /usr/sbin/iptables ]; then
FILTERSYS=2
fi;
if [ -e /usr/local/sbin/iptables ]; then
FILTERSYS=2
fi;
fi;
fi;
Download source if you have to.
Edit both files to look like below:
(save changes)
Then recompile guarddog.
And install.
Take a look at VuurMuur and Arno's firewall,
because Guarddog is not being maintained.
This hack will keep you going for a bit till
you can familarize yourself with a different option.
# Check for iptables support.
if [ -e /proc/sys/kernel/osrelease ]; then
KERNEL_VERSION=`sed "s/^\([0-9][0-9]*\.[0-9][0-9]*\).*\$/\1/" < /proc/sys/kernel/osrelease`
if [ $KERNEL_VERSION == "3.4" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "3.3" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "3.2" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "3.1" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "3.0" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "2.6" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "2.5" ]; then
KERNEL_VERSION="2.4"
fi;
if [ $KERNEL_VERSION == "2.4" ]; then
if [ -e /sbin/iptables ]; then
FILTERSYS=2
fi;
if [ -e /usr/sbin/iptables ]; then
FILTERSYS=2
fi;
if [ -e /usr/local/sbin/iptables ]; then
FILTERSYS=2
fi;
fi;
fi;
Back to comp.os.linux.security | Previous | Next — Previous in thread | Find similar
Is Guarddog incompatible with Kernel v3.2.0? ANTant@zimage.com (Ant) - 2013-01-03 08:29 -0600
Re: Is Guarddog incompatible with Kernel v3.2.0? Noob <root@127.0.0.1> - 2013-01-03 16:12 +0100
Re: Is Guarddog incompatible with Kernel v3.2.0? J G Miller <miller@yoyo.ORG> - 2013-01-03 16:15 +0000
Re: Is Guarddog incompatible with Kernel v3.2.0? ANTant@zimage.com (Ant) - 2013-01-03 12:37 -0600
Re: Is Guarddog incompatible with Kernel v3.2.0? J G Miller <miller@yoyo.ORG> - 2013-01-03 18:48 +0000
Re: Is Guarddog incompatible with Kernel v3.2.0? JohnnyLately <JohnnyLately@nowhere.invalid> - 2013-01-03 16:44 +0000
csiph-web