* Re: Guardian 2 [not found] <CACOO0z-ZmvxauaLjrv5nLX_kctaPcbMB1nGNZy02iT=E5FDNEA@mail.gmail.com> @ 2016-07-16 15:12 ` Matthias Fischer 2016-07-16 18:43 ` R. W. Rodolico 1 sibling, 0 replies; 10+ messages in thread From: Matthias Fischer @ 2016-07-16 15:12 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 5151 bytes --] Hi, you're not alone - I was a bit confused, too. Being curious, I did the following: Downloaded the newer tarball from here, hoping it would be the right one: http://people.ipfire.org/~stevee/guardian-2.0/guardian-2.0-002.i586.tar.gz Downloaded the 'dependencies' from here: http://people.ipfire.org/~stevee/guardian-2.0/packages/dependencies/i586/perl-Net-IP-1.26-1.ipfire http://people.ipfire.org/~stevee/guardian-2.0/packages/dependencies/i586/perl-common-sense-3.74-1.ipfire http://people.ipfire.org/~stevee/guardian-2.0/packages/dependencies/i586/perl-inotify2-1.22-1.ipfire Unpacked the tarball and the three pakfire-archives and got it installed on my testmachine (offline). Hint: Take a 'close* look at the 'user:group'-rights. ;-) I don't know how Stefan created the 'tarball', but most of the files in it had 'samba:samba' assignments, even the symlinks (for these I used 'chown -h root:root' ...). The original archive looks like this: ... drwxr-xr-x 3 root root 4096 Jul 16 18:04 web [root(a)ipfiretest srv]# cd web [root(a)ipfiretest web]# ls -l total 4 drwxr-xr-x 3 samba samba 4096 Jul 4 11:03 ipfire [root(a)ipfiretest web]# cd ipfire [root(a)ipfiretest ipfire]# ls -l total 4 drwxr-xr-x 2 root root 4096 Jul 16 18:04 cgi-bin [root(a)ipfiretest ipfire]# cd cgi-bin/ [root(a)ipfiretest cgi-bin]# ls -l total 64 -rwxr-xr-x 1 samba samba 37174 Jul 14 14:51 guardian.cgi -rwxr-xr-x 1 samba samba 23201 Oct 22 2014 ids.cgi ... The whole thing is still offline, GUI seems to work, I can start/stop 'guardian' and edit the 'ignore'-list. But I'd like to hear something like "That was ok, go for it...", before I put this in production. ;-) HTH, Matthias On 16.07.2016 16:19, Mark Coolen wrote: > I'm a bit confused about that. Why would 2.0-002 be newer than 2.0-010? > There's a 2.0-012 under 'old approach' but those files have an older > timestamp. The 2.0-002 is a tarball, but the 2.0-010 is an ipfire package > as are the 'dependancies'. I've used Guardian 2 several times in the past > by just extracting according to the instructions on stevee's ;--) page, but > that doesn't seem to work with the 2.0-002 tarball. I just get a completely > blank page in the GUI. > How do we test? > > On Sat, Jul 16, 2016 at 2:59 AM, Matthias Fischer < > matthias.fischer(a)ipfire.org> wrote: > >> Hi, >> >> Ok, next. >> >> Am I right assuming that the '2.0-002'-version at >> http://people.ipfire.org/~stevee/guardian-2.0/ plus >> http://people.ipfire.org/~stevee/guardian-2.0/packages/dependencies/ is >> the latest!? >> >> Best, >> Matthias >> >> On 16.07.2016 04:03, Mark Coolen wrote: >> > I'm willing to test it as well. I take it the instructions from >> > http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire are >> still >> > good? >> > >> > On Fri, Jul 15, 2016 at 8:23 PM, R. W. Rodolico <rodo(a)dailydata.net> >> wrote: >> > >> >> -----BEGIN PGP SIGNED MESSAGE----- >> >> Hash: SHA1 >> >> >> >> Tell me what I need to do to test Guardian. I've never installed it, >> >> but I am doing it now. >> >> >> >> Rod >> >> >> >> On 07/15/2016 05:00 AM, Michael Tremer wrote: >> >> > Hi guys, >> >> > >> >> > even if you have a conversation on the phone, please try keeping us >> >> > in the loop. >> >> > >> >> > So the key points of what I know: >> >> > >> >> > * A release is targeted for core update 104 >> >> > >> >> > * There are a few changes required so that re-blocking a host after >> >> > it has been manually unblocked allows this host the configured >> >> > number of tries again and not only one. >> >> > >> >> > * Many more testers are required since feedback is really low at >> >> > this point. >> >> > >> >> > Did I get this right? What is the ETA for a set of patches on the >> >> > mailing list? >> >> > >> >> > What is the plan to engage more testers? >> >> > >> >> > Best, -Michael >> >> > >> >> > On Thu, 2016-07-14 at 14:36 +0200, Daniel Weismüller wrote: >> >> >> Hi Stevee I know you are very busy and working hard on the this. >> >> >> But if you want to release the new Guardian 2 with Core 104 we >> >> >> still need to do some work and it must be tested! So please tell >> >> >> us something about the new guardian2 and the state of your work. >> >> >> >> >> >> Maybe we find more testers here on the list. >> >> >> >> >> >> Meanwhile I've talked with Michael about the state which I know >> >> >> of the guardian2 and we both go confirm that the list of blocked >> >> >> IPs which runs in the background isn't a good idea. Please let us >> >> >> talk by phone about it again. >> >> >> >> >> >> - Daniel >> >> >> >> - -- >> >> Rod Rodolico >> >> Daily Data, Inc. >> >> POB 140465 >> >> Dallas TX 75214-0465 >> >> 214.827.2170 >> >> http://www.dailydata.net >> >> -----BEGIN PGP SIGNATURE----- >> >> Version: GnuPG v1.4.12 (GNU/Linux) >> >> >> >> iEYEARECAAYFAleJfncACgkQuVY3UpYMlTQ1ywCfdXuAC8ByMYEOKBpkvV0R+BRm >> >> hhAAnR9juXlTjDlTiFMPbGOpDAP9LkOG >> >> =5XbU >> >> -----END PGP SIGNATURE----- >> >> >> > >> > >> > >> >> > > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Guardian 2 [not found] <CACOO0z-ZmvxauaLjrv5nLX_kctaPcbMB1nGNZy02iT=E5FDNEA@mail.gmail.com> 2016-07-16 15:12 ` Guardian 2 Matthias Fischer @ 2016-07-16 18:43 ` R. W. Rodolico 2016-07-16 19:34 ` Guardian 2 - Correction R. W. Rodolico 1 sibling, 1 reply; 10+ messages in thread From: R. W. Rodolico @ 2016-07-16 18:43 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 3888 bytes --] I saw the same issue and filed a bug report (https://bugzilla.ipfire.org/show_bug.cgi?id=11146). When something like this pops up, I generally https://bugzilla.ipfire.org/show_bug.cgi?id=11146 immediately after the problem shows up; that usually gives some indication of the problem. As Matthias says, it is a permissions issue on the configuration file directory. Either manually create the files (with correct ownership and permission) or change ownership/permission on the directory. Then, you have a nice, pretty GUI. I was able to efficiently block myself from the GUI after that. Since I don't know anything about how to test Snort, I'm having problems getting it to block automatically, but that is another issue. Rod On 07/16/2016 09:19 AM, Mark Coolen wrote: > I'm a bit confused about that. Why would 2.0-002 be newer than 2.0-010? > There's a 2.0-012 under 'old approach' but those files have an older > timestamp. The 2.0-002 is a tarball, but the 2.0-010 is an ipfire > package as are the 'dependancies'. I've used Guardian 2 several times in > the past by just extracting according to the instructions on stevee's > ;--) page, but that doesn't seem to work with the 2.0-002 tarball. I > just get a completely blank page in the GUI. > How do we test? > > On Sat, Jul 16, 2016 at 2:59 AM, Matthias Fischer > <matthias.fischer(a)ipfire.org <mailto:matthias.fischer(a)ipfire.org>> wrote: > > Hi, > > Ok, next. > > Am I right assuming that the '2.0-002'-version at > http://people.ipfire.org/~stevee/guardian-2.0/ plus > http://people.ipfire.org/~stevee/guardian-2.0/packages/dependencies/ is > the latest!? > > Best, > Matthias > > On 16.07.2016 04:03, Mark Coolen wrote: > > I'm willing to test it as well. I take it the instructions from > > http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire > are still > > good? > > > > On Fri, Jul 15, 2016 at 8:23 PM, R. W. Rodolico > <rodo(a)dailydata.net <mailto:rodo(a)dailydata.net>> wrote: > > > Tell me what I need to do to test Guardian. I've never installed it, > but I am doing it now. > > Rod > > On 07/15/2016 05:00 AM, Michael Tremer wrote: >> Hi guys, > >> even if you have a conversation on the phone, please try keeping us >> in the loop. > >> So the key points of what I know: > >> * A release is targeted for core update 104 > >> * There are a few changes required so that re-blocking a host after >> it has been manually unblocked allows this host the configured >> number of tries again and not only one. > >> * Many more testers are required since feedback is really low at >> this point. > >> Did I get this right? What is the ETA for a set of patches on the >> mailing list? > >> What is the plan to engage more testers? > >> Best, -Michael > >> On Thu, 2016-07-14 at 14:36 +0200, Daniel Weismüller wrote: >>> Hi Stevee I know you are very busy and working hard on the this. >>> But if you want to release the new Guardian 2 with Core 104 we >>> still need to do some work and it must be tested! So please tell >>> us something about the new guardian2 and the state of your work. >>> >>> Maybe we find more testers here on the list. >>> >>> Meanwhile I've talked with Michael about the state which I know >>> of the guardian2 and we both go confirm that the list of blocked >>> IPs which runs in the background isn't a good idea. Please let us >>> talk by phone about it again. >>> >>> - Daniel > > >> > > > > > > > > > > > -- > _ _ _ ___ _ > )\/,) ___ __ )L, )) __ __ )) __ _ _ > ((`(( ((_( (| ((\ ((__((_)((_)(( (('((\( -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Guardian 2 - Correction 2016-07-16 18:43 ` R. W. Rodolico @ 2016-07-16 19:34 ` R. W. Rodolico 2016-07-16 20:10 ` Matthias Fischer 0 siblings, 1 reply; 10+ messages in thread From: R. W. Rodolico @ 2016-07-16 19:34 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 4126 bytes --] Second paragraph should be ... I generally tail /var/log/httpd/error.log On 07/16/2016 01:43 PM, R. W. Rodolico wrote: > I saw the same issue and filed a bug report > (https://bugzilla.ipfire.org/show_bug.cgi?id=11146). > > When something like this pops up, I generally > https://bugzilla.ipfire.org/show_bug.cgi?id=11146 > immediately after the problem shows up; that usually gives some > indication of the problem. > > As Matthias says, it is a permissions issue on the configuration file > directory. Either manually create the files (with correct ownership and > permission) or change ownership/permission on the directory. Then, you > have a nice, pretty GUI. > > I was able to efficiently block myself from the GUI after that. Since I > don't know anything about how to test Snort, I'm having problems getting > it to block automatically, but that is another issue. > > Rod > > On 07/16/2016 09:19 AM, Mark Coolen wrote: >> I'm a bit confused about that. Why would 2.0-002 be newer than 2.0-010? >> There's a 2.0-012 under 'old approach' but those files have an older >> timestamp. The 2.0-002 is a tarball, but the 2.0-010 is an ipfire >> package as are the 'dependancies'. I've used Guardian 2 several times in >> the past by just extracting according to the instructions on stevee's >> ;--) page, but that doesn't seem to work with the 2.0-002 tarball. I >> just get a completely blank page in the GUI. >> How do we test? >> >> On Sat, Jul 16, 2016 at 2:59 AM, Matthias Fischer >> <matthias.fischer(a)ipfire.org <mailto:matthias.fischer(a)ipfire.org>> wrote: >> >> Hi, >> >> Ok, next. >> >> Am I right assuming that the '2.0-002'-version at >> http://people.ipfire.org/~stevee/guardian-2.0/ plus >> http://people.ipfire.org/~stevee/guardian-2.0/packages/dependencies/ is >> the latest!? >> >> Best, >> Matthias >> >> On 16.07.2016 04:03, Mark Coolen wrote: >> > I'm willing to test it as well. I take it the instructions from >> > http://planet.ipfire.org/post/introducing-guardian-2-0-for-ipfire >> are still >> > good? >> > >> > On Fri, Jul 15, 2016 at 8:23 PM, R. W. Rodolico >> <rodo(a)dailydata.net <mailto:rodo(a)dailydata.net>> wrote: >> > >> Tell me what I need to do to test Guardian. I've never installed it, >> but I am doing it now. >> >> Rod >> >> On 07/15/2016 05:00 AM, Michael Tremer wrote: >>> Hi guys, >> >>> even if you have a conversation on the phone, please try keeping us >>> in the loop. >> >>> So the key points of what I know: >> >>> * A release is targeted for core update 104 >> >>> * There are a few changes required so that re-blocking a host after >>> it has been manually unblocked allows this host the configured >>> number of tries again and not only one. >> >>> * Many more testers are required since feedback is really low at >>> this point. >> >>> Did I get this right? What is the ETA for a set of patches on the >>> mailing list? >> >>> What is the plan to engage more testers? >> >>> Best, -Michael >> >>> On Thu, 2016-07-14 at 14:36 +0200, Daniel Weismüller wrote: >>>> Hi Stevee I know you are very busy and working hard on the this. >>>> But if you want to release the new Guardian 2 with Core 104 we >>>> still need to do some work and it must be tested! So please tell >>>> us something about the new guardian2 and the state of your work. >>>> >>>> Maybe we find more testers here on the list. >>>> >>>> Meanwhile I've talked with Michael about the state which I know >>>> of the guardian2 and we both go confirm that the list of blocked >>>> IPs which runs in the background isn't a good idea. Please let us >>>> talk by phone about it again. >>>> >>>> - Daniel >> >> >> >> > >> > >> > >> >> >> >> >> -- >> _ _ _ ___ _ >> )\/,) ___ __ )L, )) __ __ )) __ _ _ >> ((`(( ((_( (| ((\ ((__((_)((_)(( (('((\( > -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Guardian 2 - Correction 2016-07-16 19:34 ` Guardian 2 - Correction R. W. Rodolico @ 2016-07-16 20:10 ` Matthias Fischer 2016-07-16 22:26 ` R. W. Rodolico 0 siblings, 1 reply; 10+ messages in thread From: Matthias Fischer @ 2016-07-16 20:10 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 1626 bytes --] Hi, On 16.07.2016 21:34, R. W. Rodolico wrote: >> As Matthias says, it is a permissions issue on the configuration file >> directory. Either manually create the files (with correct ownership and >> permission) or change ownership/permission on the directory. Actually, these directories and files are effected: ... [root(a)ipfiretest guardian-2.0-002_expanded]# find -user samba -group samba ./opt/pakfire/db/installed/meta-guardian ./etc/rc.d/rc6.d ./etc/rc.d/rc0.d ./etc/rc.d/init.d/networking/red.up/35-guardian ./etc/rc.d/init.d/snort ./etc/rc.d/init.d/guardian ./etc/rc.d/rc3.d ./etc/logrotate.d ./etc/logrotate.d/guardian ./var/ipfire/menu.d ./var/ipfire/menu.d/EX-guardian.menu ./var/ipfire/backup/addons/includes ./var/ipfire/backup/addons/includes/guardian ./var/ipfire/langs/en.pl ./var/ipfire/langs/de.pl ./var/ipfire/guardian ./var/log/guardian/guardian.log ./usr/sbin/guardian ./usr/lib/perl5/site_perl/5.12.3/Net/IP.pm ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto/Linux/Inotify2/Inotify2.so ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/Linux ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/Linux/Inotify2.pm ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common/sense.pod ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common/sense.pm ./usr/bin ./usr/bin/guardianctrl ./srv/web/ipfire ./srv/web/ipfire/cgi-bin/guardian.cgi ./srv/web/ipfire/cgi-bin/ids.cgi ... Best, Matthias ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Guardian 2 - Correction 2016-07-16 20:10 ` Matthias Fischer @ 2016-07-16 22:26 ` R. W. Rodolico 2016-07-16 23:19 ` R. W. Rodolico 0 siblings, 1 reply; 10+ messages in thread From: R. W. Rodolico @ 2016-07-16 22:26 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 1981 bytes --] Hmmm. give me a couple of hours and I'll make a script that should return all to original. Rod On 07/16/2016 03:10 PM, Matthias Fischer wrote: > Hi, > > On 16.07.2016 21:34, R. W. Rodolico wrote: >>> As Matthias says, it is a permissions issue on the configuration file >>> directory. Either manually create the files (with correct ownership and >>> permission) or change ownership/permission on the directory. > > Actually, these directories and files are effected: > > ... > [root(a)ipfiretest guardian-2.0-002_expanded]# find -user samba -group samba > ./opt/pakfire/db/installed/meta-guardian > ./etc/rc.d/rc6.d > ./etc/rc.d/rc0.d > ./etc/rc.d/init.d/networking/red.up/35-guardian > ./etc/rc.d/init.d/snort > ./etc/rc.d/init.d/guardian > ./etc/rc.d/rc3.d > ./etc/logrotate.d > ./etc/logrotate.d/guardian > ./var/ipfire/menu.d > ./var/ipfire/menu.d/EX-guardian.menu > ./var/ipfire/backup/addons/includes > ./var/ipfire/backup/addons/includes/guardian > ./var/ipfire/langs/en.pl > ./var/ipfire/langs/de.pl > ./var/ipfire/guardian > ./var/log/guardian/guardian.log > ./usr/sbin/guardian > ./usr/lib/perl5/site_perl/5.12.3/Net/IP.pm > ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto > ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto/Linux/Inotify2/Inotify2.so > ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/Linux > ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/Linux/Inotify2.pm > ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common > ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common/sense.pod > ./usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/common/sense.pm > ./usr/bin > ./usr/bin/guardianctrl > ./srv/web/ipfire > ./srv/web/ipfire/cgi-bin/guardian.cgi > ./srv/web/ipfire/cgi-bin/ids.cgi > ... > > Best, > Matthias > -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Guardian 2 - Correction 2016-07-16 22:26 ` R. W. Rodolico @ 2016-07-16 23:19 ` R. W. Rodolico 2016-07-18 14:03 ` Stefan Schantl 0 siblings, 1 reply; 10+ messages in thread From: R. W. Rodolico @ 2016-07-16 23:19 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 3739 bytes --] A partial fix would be to run the following bash commands. The reason I say partial is because I got the permissions from a different firewall that does not have Guardian installed on it, so it could not determine the correct permissions for any of those directories. This was taken from the output of a perl script I threw together. It is NOT commented (sorry) but pretty straight forward. Simply gets the permissions and ownership from each directory (and parent directory) out of an array based on Matthias' research. I did NOT check to verify the permissions were not already set. The output is simply a list of commands to set permissions from one machine to the same as the permissions on another. The originating script is temporarily stored at http://unixservertech.com/fixPermissions.pl That is a web site in progress. Feel free to download and run it on a machine that has Guardian (after looking at it and making sure I didn't do something stoopid). No guarantee it won't eat your firewall, but I ran it on a production machine, then ran the output on my test router and it appears to have worked. ====================================================== chown 0:0 /etc chmod 0755 /etc chown 0:0 /etc/logrotate.d chmod 0755 /etc/logrotate.d chown 0:0 /etc/rc.d chmod 0755 /etc/rc.d chown 0:0 /etc/rc.d/init.d chmod 0755 /etc/rc.d/init.d chown 0:0 /etc/rc.d/init.d/networking chmod 0755 /etc/rc.d/init.d/networking chown 0:0 /etc/rc.d/init.d/networking/red.up chmod 0755 /etc/rc.d/init.d/networking/red.up chown 0:0 /etc/rc.d/init.d/snort chmod 0754 /etc/rc.d/init.d/snort chown 0:0 /etc/rc.d/rc0.d chmod 0755 /etc/rc.d/rc0.d chown 0:0 /etc/rc.d/rc3.d chmod 0755 /etc/rc.d/rc3.d chown 0:0 /etc/rc.d/rc6.d chmod 0755 /etc/rc.d/rc6.d chown 0:0 /opt chmod 0755 /opt chown 0:0 /opt/pakfire chmod 0755 /opt/pakfire chown 0:0 /opt/pakfire/db chmod 0755 /opt/pakfire/db chown 0:0 /opt/pakfire/db/installed chmod 0755 /opt/pakfire/db/installed chown 0:0 /srv chmod 0755 /srv chown 0:0 /srv/web chmod 0755 /srv/web chown 0:0 /srv/web/ipfire chmod 0755 /srv/web/ipfire chown 0:0 /srv/web/ipfire/cgi-bin chmod 0755 /srv/web/ipfire/cgi-bin chown 0:0 /srv/web/ipfire/cgi-bin/ids.cgi chmod 0755 /srv/web/ipfire/cgi-bin/ids.cgi chown 0:0 /usr chmod 0755 /usr chown 0:0 /usr/bin chmod 0755 /usr/bin chown 0:0 /usr/lib chmod 0755 /usr/lib chown 0:0 /usr/lib/perl5 chmod 0755 /usr/lib/perl5 chown 0:0 /usr/lib/perl5/site_perl chmod 0755 /usr/lib/perl5/site_perl chown 0:0 /usr/lib/perl5/site_perl/5.12.3 chmod 0755 /usr/lib/perl5/site_perl/5.12.3 chown 0:0 /usr/lib/perl5/site_perl/5.12.3/Net chmod 0755 /usr/lib/perl5/site_perl/5.12.3/Net chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto chown 0:0 /usr/sbin chmod 0755 /usr/sbin chown 0:0 /var chmod 0755 /var chown 0:0 /var/ipfire chmod 0755 /var/ipfire chown 0:0 /var/ipfire/backup chmod 0755 /var/ipfire/backup chown 0:0 /var/ipfire/backup/addons chmod 0755 /var/ipfire/backup/addons chown 0:0 /var/ipfire/backup/addons/includes chmod 0755 /var/ipfire/backup/addons/includes chown 0:0 /var/ipfire/langs chmod 0755 /var/ipfire/langs chown 0:0 /var/ipfire/langs/de.pl chmod 0644 /var/ipfire/langs/de.pl chown 0:0 /var/ipfire/langs/en.pl chmod 0644 /var/ipfire/langs/en.pl chown 0:0 /var/ipfire/menu.d chmod 0755 /var/ipfire/menu.d chown 0:0 /var/log chmod 0755 /var/log ====================================================== -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Guardian 2 - Correction 2016-07-16 23:19 ` R. W. Rodolico @ 2016-07-18 14:03 ` Stefan Schantl 0 siblings, 0 replies; 10+ messages in thread From: Stefan Schantl @ 2016-07-18 14:03 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 4073 bytes --] Thanks for testing and pointing this out. I've re-packed the latest version and uploaded the new tarballs with fixed permissions. -Stefan > A partial fix would be to run the following bash commands. The reason > I > say partial is because I got the permissions from a different > firewall > that does not have Guardian installed on it, so it could not > determine > the correct permissions for any of those directories. > > This was taken from the output of a perl script I threw together. It > is > NOT commented (sorry) but pretty straight forward. Simply gets the > permissions and ownership from each directory (and parent directory) > out > of an array based on Matthias' research. I did NOT check to verify > the > permissions were not already set. The output is simply a list of > commands to set permissions from one machine to the same as the > permissions on another. > > The originating script is temporarily stored at > http://unixservertech.com/fixPermissions.pl > That is a web site in progress. Feel free to download and run it on a > machine that has Guardian (after looking at it and making sure I > didn't > do something stoopid). No guarantee it won't eat your firewall, but I > ran it on a production machine, then ran the output on my test router > and it appears to have worked. > ====================================================== > chown 0:0 /etc > chmod 0755 /etc > > chown 0:0 /etc/logrotate.d > chmod 0755 /etc/logrotate.d > > chown 0:0 /etc/rc.d > chmod 0755 /etc/rc.d > > chown 0:0 /etc/rc.d/init.d > chmod 0755 /etc/rc.d/init.d > > chown 0:0 /etc/rc.d/init.d/networking > chmod 0755 /etc/rc.d/init.d/networking > > chown 0:0 /etc/rc.d/init.d/networking/red.up > chmod 0755 /etc/rc.d/init.d/networking/red.up > > chown 0:0 /etc/rc.d/init.d/snort > chmod 0754 /etc/rc.d/init.d/snort > > chown 0:0 /etc/rc.d/rc0.d > chmod 0755 /etc/rc.d/rc0.d > > chown 0:0 /etc/rc.d/rc3.d > chmod 0755 /etc/rc.d/rc3.d > > chown 0:0 /etc/rc.d/rc6.d > chmod 0755 /etc/rc.d/rc6.d > > chown 0:0 /opt > chmod 0755 /opt > > chown 0:0 /opt/pakfire > chmod 0755 /opt/pakfire > > chown 0:0 /opt/pakfire/db > chmod 0755 /opt/pakfire/db > > chown 0:0 /opt/pakfire/db/installed > chmod 0755 /opt/pakfire/db/installed > > chown 0:0 /srv > chmod 0755 /srv > > chown 0:0 /srv/web > chmod 0755 /srv/web > > chown 0:0 /srv/web/ipfire > chmod 0755 /srv/web/ipfire > > chown 0:0 /srv/web/ipfire/cgi-bin > chmod 0755 /srv/web/ipfire/cgi-bin > > chown 0:0 /srv/web/ipfire/cgi-bin/ids.cgi > chmod 0755 /srv/web/ipfire/cgi-bin/ids.cgi > > chown 0:0 /usr > chmod 0755 /usr > > chown 0:0 /usr/bin > chmod 0755 /usr/bin > > chown 0:0 /usr/lib > chmod 0755 /usr/lib > > chown 0:0 /usr/lib/perl5 > chmod 0755 /usr/lib/perl5 > > chown 0:0 /usr/lib/perl5/site_perl > chmod 0755 /usr/lib/perl5/site_perl > > chown 0:0 /usr/lib/perl5/site_perl/5.12.3 > chmod 0755 /usr/lib/perl5/site_perl/5.12.3 > > chown 0:0 /usr/lib/perl5/site_perl/5.12.3/Net > chmod 0755 /usr/lib/perl5/site_perl/5.12.3/Net > > chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi > chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi > > chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread- > multi/auto > chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread- > multi/auto > > chown 0:0 /usr/sbin > chmod 0755 /usr/sbin > > chown 0:0 /var > chmod 0755 /var > > chown 0:0 /var/ipfire > chmod 0755 /var/ipfire > > chown 0:0 /var/ipfire/backup > chmod 0755 /var/ipfire/backup > > chown 0:0 /var/ipfire/backup/addons > chmod 0755 /var/ipfire/backup/addons > > chown 0:0 /var/ipfire/backup/addons/includes > chmod 0755 /var/ipfire/backup/addons/includes > > chown 0:0 /var/ipfire/langs > chmod 0755 /var/ipfire/langs > > chown 0:0 /var/ipfire/langs/de.pl > chmod 0644 /var/ipfire/langs/de.pl > > chown 0:0 /var/ipfire/langs/en.pl > chmod 0644 /var/ipfire/langs/en.pl > > chown 0:0 /var/ipfire/menu.d > chmod 0755 /var/ipfire/menu.d > > chown 0:0 /var/log > chmod 0755 /var/log > ====================================================== > [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
[parent not found: <CACOO0z_XpLEKp3E7M1n6t6cgmVmDNO7OGzUaVN-pr9b7rOwWaQ@mail.gmail.com>]
* Re: Guardian 2 - Correction [not found] <CACOO0z_XpLEKp3E7M1n6t6cgmVmDNO7OGzUaVN-pr9b7rOwWaQ@mail.gmail.com> @ 2016-07-17 0:56 ` R. W. Rodolico 2016-07-17 5:43 ` Matthias Fischer 0 siblings, 1 reply; 10+ messages in thread From: R. W. Rodolico @ 2016-07-17 0:56 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 5651 bytes --] Do the following: Open a command prompt on the router, via whatever means you have, and issue the command: tail -f /var/log/httpd/error_log Note the latest timestamp of the entry Now, open a web browser and browse to the Guardian page, but nothing else. Copy the text from the command prompt after the timestamp you noted above. You can send that directly to me if you like, or reply here. If I can not suggest a fix, I'll be happy to work with you via messaging, email, or if you're in the US, phone. Rod On 07/16/2016 07:42 PM, Mark Coolen wrote: > I'm still getting nothing but a blank page. Everything else seems to > still be working fine, but I'm a bit afraid I'll mess something up > really badly with all this playing around. > > On Sat, Jul 16, 2016 at 7:19 PM, R. W. Rodolico <rodo(a)dailydata.net > <mailto:rodo(a)dailydata.net>> wrote: > > A partial fix would be to run the following bash commands. The reason I > say partial is because I got the permissions from a different firewall > that does not have Guardian installed on it, so it could not determine > the correct permissions for any of those directories. > > This was taken from the output of a perl script I threw together. It is > NOT commented (sorry) but pretty straight forward. Simply gets the > permissions and ownership from each directory (and parent directory) out > of an array based on Matthias' research. I did NOT check to verify the > permissions were not already set. The output is simply a list of > commands to set permissions from one machine to the same as the > permissions on another. > > The originating script is temporarily stored at > http://unixservertech.com/fixPermissions.pl > That is a web site in progress. Feel free to download and run it on a > machine that has Guardian (after looking at it and making sure I didn't > do something stoopid). No guarantee it won't eat your firewall, but I > ran it on a production machine, then ran the output on my test router > and it appears to have worked. > ====================================================== > chown 0:0 /etc > chmod 0755 /etc > > chown 0:0 /etc/logrotate.d > chmod 0755 /etc/logrotate.d > > chown 0:0 /etc/rc.d > chmod 0755 /etc/rc.d > > chown 0:0 /etc/rc.d/init.d > chmod 0755 /etc/rc.d/init.d > > chown 0:0 /etc/rc.d/init.d/networking > chmod 0755 /etc/rc.d/init.d/networking > > chown 0:0 /etc/rc.d/init.d/networking/red.up > chmod 0755 /etc/rc.d/init.d/networking/red.up > > chown 0:0 /etc/rc.d/init.d/snort > chmod 0754 /etc/rc.d/init.d/snort > > chown 0:0 /etc/rc.d/rc0.d > chmod 0755 /etc/rc.d/rc0.d > > chown 0:0 /etc/rc.d/rc3.d > chmod 0755 /etc/rc.d/rc3.d > > chown 0:0 /etc/rc.d/rc6.d > chmod 0755 /etc/rc.d/rc6.d > > chown 0:0 /opt > chmod 0755 /opt > > chown 0:0 /opt/pakfire > chmod 0755 /opt/pakfire > > chown 0:0 /opt/pakfire/db > chmod 0755 /opt/pakfire/db > > chown 0:0 /opt/pakfire/db/installed > chmod 0755 /opt/pakfire/db/installed > > chown 0:0 /srv > chmod 0755 /srv > > chown 0:0 /srv/web > chmod 0755 /srv/web > > chown 0:0 /srv/web/ipfire > chmod 0755 /srv/web/ipfire > > chown 0:0 /srv/web/ipfire/cgi-bin > chmod 0755 /srv/web/ipfire/cgi-bin > > chown 0:0 /srv/web/ipfire/cgi-bin/ids.cgi > chmod 0755 /srv/web/ipfire/cgi-bin/ids.cgi > > chown 0:0 /usr > chmod 0755 /usr > > chown 0:0 /usr/bin > chmod 0755 /usr/bin > > chown 0:0 /usr/lib > chmod 0755 /usr/lib > > chown 0:0 /usr/lib/perl5 > chmod 0755 /usr/lib/perl5 > > chown 0:0 /usr/lib/perl5/site_perl > chmod 0755 /usr/lib/perl5/site_perl > > chown 0:0 /usr/lib/perl5/site_perl/5.12.3 > chmod 0755 /usr/lib/perl5/site_perl/5.12.3 > > chown 0:0 /usr/lib/perl5/site_perl/5.12.3/Net > chmod 0755 /usr/lib/perl5/site_perl/5.12.3/Net > > chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi > chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi > > chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto > chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto > > chown 0:0 /usr/sbin > chmod 0755 /usr/sbin > > chown 0:0 /var > chmod 0755 /var > > chown 0:0 /var/ipfire > chmod 0755 /var/ipfire > > chown 0:0 /var/ipfire/backup > chmod 0755 /var/ipfire/backup > > chown 0:0 /var/ipfire/backup/addons > chmod 0755 /var/ipfire/backup/addons > > chown 0:0 /var/ipfire/backup/addons/includes > chmod 0755 /var/ipfire/backup/addons/includes > > chown 0:0 /var/ipfire/langs > chmod 0755 /var/ipfire/langs > > chown 0:0 /var/ipfire/langs/de.pl <http://de.pl> > chmod 0644 /var/ipfire/langs/de.pl <http://de.pl> > > chown 0:0 /var/ipfire/langs/en.pl <http://en.pl> > chmod 0644 /var/ipfire/langs/en.pl <http://en.pl> > > chown 0:0 /var/ipfire/menu.d > chmod 0755 /var/ipfire/menu.d > > chown 0:0 /var/log > chmod 0755 /var/log > ====================================================== > > -- > Rod Rodolico > Daily Data, Inc. > POB 140465 > Dallas TX 75214-0465 > 214.827.2170 <tel:214.827.2170> > http://www.dailydata.net > > > > > -- > _ _ _ ___ _ > )\/,) ___ __ )L, )) __ __ )) __ _ _ > ((`(( ((_( (| ((\ ((__((_)((_)(( (('((\( -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Guardian 2 - Correction 2016-07-17 0:56 ` R. W. Rodolico @ 2016-07-17 5:43 ` Matthias Fischer 0 siblings, 0 replies; 10+ messages in thread From: Matthias Fischer @ 2016-07-17 5:43 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 6269 bytes --] Hi, another suggestion: Delete ALL files in '/var/ipfire/guardian' and reload '/srv/web/ipfire/cgi-bin/guardian.cgi'. If these files don't exist, they will be created with standard settings. Perhaps GUI can't load because of already wrong file permissions... HTH, Matthias On 17.07.2016 02:56, R. W. Rodolico wrote: > Do the following: > > Open a command prompt on the router, via whatever means you have, and > issue the command: > > tail -f /var/log/httpd/error_log > > Note the latest timestamp of the entry > > Now, open a web browser and browse to the Guardian page, but nothing else. > > Copy the text from the command prompt after the timestamp you noted > above. You can send that directly to me if you like, or reply here. > > If I can not suggest a fix, I'll be happy to work with you via > messaging, email, or if you're in the US, phone. > > Rod > > On 07/16/2016 07:42 PM, Mark Coolen wrote: >> I'm still getting nothing but a blank page. Everything else seems to >> still be working fine, but I'm a bit afraid I'll mess something up >> really badly with all this playing around. >> >> On Sat, Jul 16, 2016 at 7:19 PM, R. W. Rodolico <rodo(a)dailydata.net >> <mailto:rodo(a)dailydata.net>> wrote: >> >> A partial fix would be to run the following bash commands. The reason I >> say partial is because I got the permissions from a different firewall >> that does not have Guardian installed on it, so it could not determine >> the correct permissions for any of those directories. >> >> This was taken from the output of a perl script I threw together. It is >> NOT commented (sorry) but pretty straight forward. Simply gets the >> permissions and ownership from each directory (and parent directory) out >> of an array based on Matthias' research. I did NOT check to verify the >> permissions were not already set. The output is simply a list of >> commands to set permissions from one machine to the same as the >> permissions on another. >> >> The originating script is temporarily stored at >> http://unixservertech.com/fixPermissions.pl >> That is a web site in progress. Feel free to download and run it on a >> machine that has Guardian (after looking at it and making sure I didn't >> do something stoopid). No guarantee it won't eat your firewall, but I >> ran it on a production machine, then ran the output on my test router >> and it appears to have worked. >> ====================================================== >> chown 0:0 /etc >> chmod 0755 /etc >> >> chown 0:0 /etc/logrotate.d >> chmod 0755 /etc/logrotate.d >> >> chown 0:0 /etc/rc.d >> chmod 0755 /etc/rc.d >> >> chown 0:0 /etc/rc.d/init.d >> chmod 0755 /etc/rc.d/init.d >> >> chown 0:0 /etc/rc.d/init.d/networking >> chmod 0755 /etc/rc.d/init.d/networking >> >> chown 0:0 /etc/rc.d/init.d/networking/red.up >> chmod 0755 /etc/rc.d/init.d/networking/red.up >> >> chown 0:0 /etc/rc.d/init.d/snort >> chmod 0754 /etc/rc.d/init.d/snort >> >> chown 0:0 /etc/rc.d/rc0.d >> chmod 0755 /etc/rc.d/rc0.d >> >> chown 0:0 /etc/rc.d/rc3.d >> chmod 0755 /etc/rc.d/rc3.d >> >> chown 0:0 /etc/rc.d/rc6.d >> chmod 0755 /etc/rc.d/rc6.d >> >> chown 0:0 /opt >> chmod 0755 /opt >> >> chown 0:0 /opt/pakfire >> chmod 0755 /opt/pakfire >> >> chown 0:0 /opt/pakfire/db >> chmod 0755 /opt/pakfire/db >> >> chown 0:0 /opt/pakfire/db/installed >> chmod 0755 /opt/pakfire/db/installed >> >> chown 0:0 /srv >> chmod 0755 /srv >> >> chown 0:0 /srv/web >> chmod 0755 /srv/web >> >> chown 0:0 /srv/web/ipfire >> chmod 0755 /srv/web/ipfire >> >> chown 0:0 /srv/web/ipfire/cgi-bin >> chmod 0755 /srv/web/ipfire/cgi-bin >> >> chown 0:0 /srv/web/ipfire/cgi-bin/ids.cgi >> chmod 0755 /srv/web/ipfire/cgi-bin/ids.cgi >> >> chown 0:0 /usr >> chmod 0755 /usr >> >> chown 0:0 /usr/bin >> chmod 0755 /usr/bin >> >> chown 0:0 /usr/lib >> chmod 0755 /usr/lib >> >> chown 0:0 /usr/lib/perl5 >> chmod 0755 /usr/lib/perl5 >> >> chown 0:0 /usr/lib/perl5/site_perl >> chmod 0755 /usr/lib/perl5/site_perl >> >> chown 0:0 /usr/lib/perl5/site_perl/5.12.3 >> chmod 0755 /usr/lib/perl5/site_perl/5.12.3 >> >> chown 0:0 /usr/lib/perl5/site_perl/5.12.3/Net >> chmod 0755 /usr/lib/perl5/site_perl/5.12.3/Net >> >> chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi >> chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi >> >> chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto >> chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto >> >> chown 0:0 /usr/sbin >> chmod 0755 /usr/sbin >> >> chown 0:0 /var >> chmod 0755 /var >> >> chown 0:0 /var/ipfire >> chmod 0755 /var/ipfire >> >> chown 0:0 /var/ipfire/backup >> chmod 0755 /var/ipfire/backup >> >> chown 0:0 /var/ipfire/backup/addons >> chmod 0755 /var/ipfire/backup/addons >> >> chown 0:0 /var/ipfire/backup/addons/includes >> chmod 0755 /var/ipfire/backup/addons/includes >> >> chown 0:0 /var/ipfire/langs >> chmod 0755 /var/ipfire/langs >> >> chown 0:0 /var/ipfire/langs/de.pl <http://de.pl> >> chmod 0644 /var/ipfire/langs/de.pl <http://de.pl> >> >> chown 0:0 /var/ipfire/langs/en.pl <http://en.pl> >> chmod 0644 /var/ipfire/langs/en.pl <http://en.pl> >> >> chown 0:0 /var/ipfire/menu.d >> chmod 0755 /var/ipfire/menu.d >> >> chown 0:0 /var/log >> chmod 0755 /var/log >> ====================================================== >> >> -- >> Rod Rodolico >> Daily Data, Inc. >> POB 140465 >> Dallas TX 75214-0465 >> 214.827.2170 <tel:214.827.2170> >> http://www.dailydata.net >> >> >> >> >> -- >> _ _ _ ___ _ >> )\/,) ___ __ )L, )) __ __ )) __ _ _ >> ((`(( ((_( (| ((\ ((__((_)((_)(( (('((\( > ^ permalink raw reply [flat|nested] 10+ messages in thread
[parent not found: <CACOO0z_2rhPGhW_rCe46VMCgWTT_4jLxMwSJZoAheY5ouiNt=g@mail.gmail.com>]
* Re: Guardian 2 - Correction [not found] <CACOO0z_2rhPGhW_rCe46VMCgWTT_4jLxMwSJZoAheY5ouiNt=g@mail.gmail.com> @ 2016-07-17 13:57 ` Matthias Fischer 0 siblings, 0 replies; 10+ messages in thread From: Matthias Fischer @ 2016-07-17 13:57 UTC (permalink / raw) To: development [-- Attachment #1: Type: text/plain, Size: 7645 bytes --] Hi, it seems that this problem is yours... ;-) I just added a few hosts manually and had no problem 'Unblocking all'. Which process uses 'xtables' on IPFire? GeoIP? Where do you get this message? On the GUI? Just to be sure, to see if everything is (hopefully) ok regarding the rights I would do a: ' find / -user samba -group samba' But I just found another one: RAM usage. On my production machine, the old guardian takes about *2529 KB* RAM. On my OFFLINE testmachine the NEW guardian claims to use *90011 KB*. Confirm? Best, Matthias On 17.07.2016 14:12, Mark Coolen wrote: > I set the /var/ipfire/guardian permissions to nobody:nobody and everything > started to work. > > Now I have other problems ;-) > > I tried 'Unblock all' and got: > > Another app is currently holding the xtables lock. Perhaps you want to use > the -w option?, referer: https://10.46.235.1:444/cgi-bin/guardian.cgi > > On Sun, Jul 17, 2016 at 1:43 AM, Matthias Fischer < > matthias.fischer(a)ipfire.org> wrote: > >> Hi, >> >> another suggestion: >> >> Delete ALL files in '/var/ipfire/guardian' and reload >> '/srv/web/ipfire/cgi-bin/guardian.cgi'. If these files don't exist, they >> will be created with standard settings. >> >> Perhaps GUI can't load because of already wrong file permissions... >> >> HTH, >> Matthias >> >> On 17.07.2016 02:56, R. W. Rodolico wrote: >> > Do the following: >> > >> > Open a command prompt on the router, via whatever means you have, and >> > issue the command: >> > >> > tail -f /var/log/httpd/error_log >> > >> > Note the latest timestamp of the entry >> > >> > Now, open a web browser and browse to the Guardian page, but nothing >> else. >> > >> > Copy the text from the command prompt after the timestamp you noted >> > above. You can send that directly to me if you like, or reply here. >> > >> > If I can not suggest a fix, I'll be happy to work with you via >> > messaging, email, or if you're in the US, phone. >> > >> > Rod >> > >> > On 07/16/2016 07:42 PM, Mark Coolen wrote: >> >> I'm still getting nothing but a blank page. Everything else seems to >> >> still be working fine, but I'm a bit afraid I'll mess something up >> >> really badly with all this playing around. >> >> >> >> On Sat, Jul 16, 2016 at 7:19 PM, R. W. Rodolico <rodo(a)dailydata.net >> >> <mailto:rodo(a)dailydata.net>> wrote: >> >> >> >> A partial fix would be to run the following bash commands. The >> reason I >> >> say partial is because I got the permissions from a different >> firewall >> >> that does not have Guardian installed on it, so it could not >> determine >> >> the correct permissions for any of those directories. >> >> >> >> This was taken from the output of a perl script I threw together. >> It is >> >> NOT commented (sorry) but pretty straight forward. Simply gets the >> >> permissions and ownership from each directory (and parent >> directory) out >> >> of an array based on Matthias' research. I did NOT check to verify >> the >> >> permissions were not already set. The output is simply a list of >> >> commands to set permissions from one machine to the same as the >> >> permissions on another. >> >> >> >> The originating script is temporarily stored at >> >> http://unixservertech.com/fixPermissions.pl >> >> That is a web site in progress. Feel free to download and run it on >> a >> >> machine that has Guardian (after looking at it and making sure I >> didn't >> >> do something stoopid). No guarantee it won't eat your firewall, but >> I >> >> ran it on a production machine, then ran the output on my test >> router >> >> and it appears to have worked. >> >> ====================================================== >> >> chown 0:0 /etc >> >> chmod 0755 /etc >> >> >> >> chown 0:0 /etc/logrotate.d >> >> chmod 0755 /etc/logrotate.d >> >> >> >> chown 0:0 /etc/rc.d >> >> chmod 0755 /etc/rc.d >> >> >> >> chown 0:0 /etc/rc.d/init.d >> >> chmod 0755 /etc/rc.d/init.d >> >> >> >> chown 0:0 /etc/rc.d/init.d/networking >> >> chmod 0755 /etc/rc.d/init.d/networking >> >> >> >> chown 0:0 /etc/rc.d/init.d/networking/red.up >> >> chmod 0755 /etc/rc.d/init.d/networking/red.up >> >> >> >> chown 0:0 /etc/rc.d/init.d/snort >> >> chmod 0754 /etc/rc.d/init.d/snort >> >> >> >> chown 0:0 /etc/rc.d/rc0.d >> >> chmod 0755 /etc/rc.d/rc0.d >> >> >> >> chown 0:0 /etc/rc.d/rc3.d >> >> chmod 0755 /etc/rc.d/rc3.d >> >> >> >> chown 0:0 /etc/rc.d/rc6.d >> >> chmod 0755 /etc/rc.d/rc6.d >> >> >> >> chown 0:0 /opt >> >> chmod 0755 /opt >> >> >> >> chown 0:0 /opt/pakfire >> >> chmod 0755 /opt/pakfire >> >> >> >> chown 0:0 /opt/pakfire/db >> >> chmod 0755 /opt/pakfire/db >> >> >> >> chown 0:0 /opt/pakfire/db/installed >> >> chmod 0755 /opt/pakfire/db/installed >> >> >> >> chown 0:0 /srv >> >> chmod 0755 /srv >> >> >> >> chown 0:0 /srv/web >> >> chmod 0755 /srv/web >> >> >> >> chown 0:0 /srv/web/ipfire >> >> chmod 0755 /srv/web/ipfire >> >> >> >> chown 0:0 /srv/web/ipfire/cgi-bin >> >> chmod 0755 /srv/web/ipfire/cgi-bin >> >> >> >> chown 0:0 /srv/web/ipfire/cgi-bin/ids.cgi >> >> chmod 0755 /srv/web/ipfire/cgi-bin/ids.cgi >> >> >> >> chown 0:0 /usr >> >> chmod 0755 /usr >> >> >> >> chown 0:0 /usr/bin >> >> chmod 0755 /usr/bin >> >> >> >> chown 0:0 /usr/lib >> >> chmod 0755 /usr/lib >> >> >> >> chown 0:0 /usr/lib/perl5 >> >> chmod 0755 /usr/lib/perl5 >> >> >> >> chown 0:0 /usr/lib/perl5/site_perl >> >> chmod 0755 /usr/lib/perl5/site_perl >> >> >> >> chown 0:0 /usr/lib/perl5/site_perl/5.12.3 >> >> chmod 0755 /usr/lib/perl5/site_perl/5.12.3 >> >> >> >> chown 0:0 /usr/lib/perl5/site_perl/5.12.3/Net >> >> chmod 0755 /usr/lib/perl5/site_perl/5.12.3/Net >> >> >> >> chown 0:0 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi >> >> chmod 0755 /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi >> >> >> >> chown 0:0 >> /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto >> >> chmod 0755 >> /usr/lib/perl5/site_perl/5.12.3/i586-linux-thread-multi/auto >> >> >> >> chown 0:0 /usr/sbin >> >> chmod 0755 /usr/sbin >> >> >> >> chown 0:0 /var >> >> chmod 0755 /var >> >> >> >> chown 0:0 /var/ipfire >> >> chmod 0755 /var/ipfire >> >> >> >> chown 0:0 /var/ipfire/backup >> >> chmod 0755 /var/ipfire/backup >> >> >> >> chown 0:0 /var/ipfire/backup/addons >> >> chmod 0755 /var/ipfire/backup/addons >> >> >> >> chown 0:0 /var/ipfire/backup/addons/includes >> >> chmod 0755 /var/ipfire/backup/addons/includes >> >> >> >> chown 0:0 /var/ipfire/langs >> >> chmod 0755 /var/ipfire/langs >> >> >> >> chown 0:0 /var/ipfire/langs/de.pl <http://de.pl> >> >> chmod 0644 /var/ipfire/langs/de.pl <http://de.pl> >> >> >> >> chown 0:0 /var/ipfire/langs/en.pl <http://en.pl> >> >> chmod 0644 /var/ipfire/langs/en.pl <http://en.pl> >> >> >> >> chown 0:0 /var/ipfire/menu.d >> >> chmod 0755 /var/ipfire/menu.d >> >> >> >> chown 0:0 /var/log >> >> chmod 0755 /var/log >> >> ====================================================== >> >> >> >> -- >> >> Rod Rodolico >> >> Daily Data, Inc. >> >> POB 140465 >> >> Dallas TX 75214-0465 >> >> 214.827.2170 <tel:214.827.2170> >> >> http://www.dailydata.net >> >> >> >> >> >> >> >> >> >> -- >> >> _ _ _ ___ _ >> >> )\/,) ___ __ )L, )) __ __ )) __ _ _ >> >> ((`(( ((_( (| ((\ ((__((_)((_)(( (('((\( >> > >> >> > > ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2016-07-18 14:03 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CACOO0z-ZmvxauaLjrv5nLX_kctaPcbMB1nGNZy02iT=E5FDNEA@mail.gmail.com>
2016-07-16 15:12 ` Guardian 2 Matthias Fischer
2016-07-16 18:43 ` R. W. Rodolico
2016-07-16 19:34 ` Guardian 2 - Correction R. W. Rodolico
2016-07-16 20:10 ` Matthias Fischer
2016-07-16 22:26 ` R. W. Rodolico
2016-07-16 23:19 ` R. W. Rodolico
2016-07-18 14:03 ` Stefan Schantl
[not found] <CACOO0z_XpLEKp3E7M1n6t6cgmVmDNO7OGzUaVN-pr9b7rOwWaQ@mail.gmail.com>
2016-07-17 0:56 ` R. W. Rodolico
2016-07-17 5:43 ` Matthias Fischer
[not found] <CACOO0z_2rhPGhW_rCe46VMCgWTT_4jLxMwSJZoAheY5ouiNt=g@mail.gmail.com>
2016-07-17 13:57 ` Matthias Fischer
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox