On Mon, Nov 04, 2019 at 12:48:00PM -0500, Gene Heskett wrote:
> On Monday 04 November 2019 09:29:48 Greg Wooledge wrote:
>
> > On Mon, Nov 04, 2019 at 09:08:36AM -0500, Gene Heskett wrote:
[...]
> And that looks like nginx is a lot easier to program than apache2.
Nearly anything is -- except
On Monday 04 November 2019 09:29:48 Greg Wooledge wrote:
> On Mon, Nov 04, 2019 at 09:08:36AM -0500, Gene Heskett wrote:
> > Does apache2 have its own module that would prevent its responding
> > to an ipv4 address presented in a .conf file as "xx.xx.xx.xx/24"
> > format?
>
> Well, looking at
On Mon, Nov 04, 2019 at 09:44:56AM -0500, Gene Heskett wrote:
[...]
> If its not built to use libwrap0, then I assume it has its own module to
> similarly restrict its response to a specified incoming source address?
>
> And it is?
See above :)
Much more flexible than tcpwrappers. And once
On Monday 04 November 2019 08:50:20 Greg Wooledge wrote:
> On Fri, Nov 01, 2019 at 06:46:25PM -0400, Gene Heskett wrote:
> > I'll make sure its installed. Right now. But that is a problem:
> > root@coyote:etc$ apt install tcpwrappers
>
> ... no, Gene.
>
> TCP wrappers is a *library*, and its
On Mon, Nov 04, 2019 at 09:08:36AM -0500, Gene Heskett wrote:
> On Monday 04 November 2019 08:45:42 Greg Wooledge wrote:
>
> > On Fri, Nov 01, 2019 at 11:06:26PM +0100, to...@tuxteam.de wrote:
> > > That will depend on whether apache is compiled with tcpwrappers
> > > (that's the library
On Mon, Nov 04, 2019 at 09:08:36AM -0500, Gene Heskett wrote:
> Does apache2 have its own module that would prevent its responding to an
> ipv4 address presented in a .conf file as "xx.xx.xx.xx/24" format?
Well, looking at your larger issue, you might find it more useful
to block these bots
On Monday 04 November 2019 08:45:42 Greg Wooledge wrote:
> On Fri, Nov 01, 2019 at 11:06:26PM +0100, to...@tuxteam.de wrote:
> > That will depend on whether apache is compiled with tcpwrappers
> > (that's the library implementing the hosts.{allow,deny} policies). I
> > don't know whether Debian's
On Fri, Nov 01, 2019 at 06:46:25PM -0400, Gene Heskett wrote:
> I'll make sure its installed. Right now. But that is a problem:
> root@coyote:etc$ apt install tcpwrappers
... no, Gene.
TCP wrappers is a *library*, and its package name in Debian is libwrap0.
wooledg:~$ apt-cache search tcp
On Fri, Nov 01, 2019 at 11:06:26PM +0100, to...@tuxteam.de wrote:
> That will depend on whether apache is compiled with tcpwrappers (that's
> the library implementing the hosts.{allow,deny} policies). I don't
> know whether Debian's distribution does that (perhaps others will).
It's not.
arc3:~$
On Saturday 02 November 2019 08:55:51 Dan Purgert wrote:
> wrote:
> > On Fri, Nov 01, 2019 at 06:46:25PM -0400, Gene Heskett wrote:
> >> [...]
> >> Humm, further exercise with a digital potatoe fork discloses that
> >> "tcpd" is the old tcpwappers, and its installed and running.
> >
> > Yikes. I
Hi.
On Sat, Nov 02, 2019 at 12:55:51PM -, Dan Purgert wrote:
> wrote:
> > On Fri, Nov 01, 2019 at 06:46:25PM -0400, Gene Heskett wrote:
>
> >> [...]
> >> Humm, further exercise with a dital potatoe fork discloses that
> >> "tcpd" is the old tcpwappers, and its installed and running.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
wrote:
> On Fri, Nov 01, 2019 at 06:46:25PM -0400, Gene Heskett wrote:
>> [...]
>> Humm, further exercise with a dital potatoe fork discloses that
>> "tcpd" is the old tcpwappers, and its installed and running.
>
> Yikes. I didn't even know (or
On Fri, Nov 01, 2019 at 06:46:25PM -0400, Gene Heskett wrote:
[...]
> > For tcpwrappers... dunno.
> >
> I'll make sure its installed. Right now. But that is a problem:
[...]
> E: Unable to locate package tcpwrappers
Bummer.
> Humm, further exercise with a dital potatoe fork discloses that
On Friday 01 November 2019 18:06:26 to...@tuxteam.de wrote:
> On Fri, Nov 01, 2019 at 04:35:24PM -0400, Gene Heskett wrote:
> > On Friday 01 November 2019 14:44:07 Gene Heskett wrote:
> > > On Friday 01 November 2019 13:43:04 to...@tuxteam.de wrote:
> > > > On Fri, Nov 01, 2019 at 01:12:46PM
On Friday 01 November 2019 17:33:56 mick crane wrote:
> >> That was my assumption, and might help keep track of what apache2
> >> can see. Except I just ran it, and it didn't show to the full path
> >> depth. Perhaps it has a depth control?
> >
> > that's the "f" bit of the options
>
> Oh hang
On Fri, Nov 01, 2019 at 04:35:24PM -0400, Gene Heskett wrote:
> On Friday 01 November 2019 14:44:07 Gene Heskett wrote:
>
> > On Friday 01 November 2019 13:43:04 to...@tuxteam.de wrote:
> > > On Fri, Nov 01, 2019 at 01:12:46PM -0400, Gene Heskett wrote:
> > > > On Friday 01 November 2019 12:42:21
That was my assumption, and might help keep track of what apache2 can
see. Except I just ran it, and it didn't show to the full path depth.
Perhaps it has a depth control?
that's the "f" bit of the options
Oh hang on, there's something about a limit to the depth but I can't
remember what
On 2019-11-01 18:18, Gene Heskett wrote:
On Friday 01 November 2019 13:37:02 mick crane wrote:
On 2019-11-01 17:20, Gene Heskett wrote:
> On Friday 01 November 2019 13:12:42 mick crane wrote:
>> On 2019-11-01 17:01, mick crane wrote:
>> > On 2019-11-01 16:47, mick crane wrote:
>> >> On
On Friday 01 November 2019 14:44:07 Gene Heskett wrote:
> On Friday 01 November 2019 13:43:04 to...@tuxteam.de wrote:
> > On Fri, Nov 01, 2019 at 01:12:46PM -0400, Gene Heskett wrote:
> > > On Friday 01 November 2019 12:42:21 to...@tuxteam.de wrote:
> >
> > [...]
> >
> > > >
On Friday 01 November 2019 13:43:04 to...@tuxteam.de wrote:
> On Fri, Nov 01, 2019 at 01:12:46PM -0400, Gene Heskett wrote:
> > On Friday 01 November 2019 12:42:21 to...@tuxteam.de wrote:
>
> [...]
>
> > > https://en.wikipedia.org/wiki/Robots.txt
> >
> > Did that, blanket Disallow for all didn't
On Friday 01 November 2019 13:37:02 mick crane wrote:
> On 2019-11-01 17:20, Gene Heskett wrote:
> > On Friday 01 November 2019 13:12:42 mick crane wrote:
> >> On 2019-11-01 17:01, mick crane wrote:
> >> > On 2019-11-01 16:47, mick crane wrote:
> >> >> On 2019-11-01 16:18, Gene Heskett wrote:
>
On Fri, Nov 01, 2019 at 01:12:46PM -0400, Gene Heskett wrote:
> On Friday 01 November 2019 12:42:21 to...@tuxteam.de wrote:
[...]
> > https://en.wikipedia.org/wiki/Robots.txt
> >
> Did that, blanket Disallow for all didn't stop them. But they are spacing
> out the requests now, so the average
On 2019-11-01 17:20, Gene Heskett wrote:
On Friday 01 November 2019 13:12:42 mick crane wrote:
On 2019-11-01 17:01, mick crane wrote:
> On 2019-11-01 16:47, mick crane wrote:
>> On 2019-11-01 16:18, Gene Heskett wrote:
>>> lsof |grep www-data shows me several hundred lines of "no perms"
>>>
On Friday 01 November 2019 13:12:42 mick crane wrote:
> On 2019-11-01 17:01, mick crane wrote:
> > On 2019-11-01 16:47, mick crane wrote:
> >> On 2019-11-01 16:18, Gene Heskett wrote:
> >>> lsof |grep www-data shows me several hundred lines of "no perms"
> >>> errors
> >>> without nameing the
On Friday 01 November 2019 12:52:47 Dan Purgert wrote:
> wrote:
> > On Fri, Nov 01, 2019 at 04:29:38PM -, Dan Purgert wrote:
> >> Gene Heskett wrote:
> >>> [...]
> >>> Humm. in /var/log/httpd/other_vhosts_access.log, is looks as if
> >>> both www.yandex.com/bots and www.semrush.com/bot.html
On Friday 01 November 2019 12:47:46 mick crane wrote:
> On 2019-11-01 16:18, Gene Heskett wrote:
> > lsof |grep www-data shows me several hundred lines of "no perms"
> > errors without nameing the source of the errors other than apache2.
> > How do I find the file causing those errors? Thats
On 2019-11-01 17:01, mick crane wrote:
On 2019-11-01 16:47, mick crane wrote:
On 2019-11-01 16:18, Gene Heskett wrote:
lsof |grep www-data shows me several hundred lines of "no perms"
errors
without nameing the source of the errors other than apache2. How do
I
find the file causing those
On Friday 01 November 2019 12:42:21 to...@tuxteam.de wrote:
> On Fri, Nov 01, 2019 at 04:29:38PM -, Dan Purgert wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Gene Heskett wrote:
> > > [...]
> > > Humm. in /var/log/httpd/other_vhosts_access.log, is looks as if
> > >
On Fri, Nov 01, 2019 at 04:52:47PM -, Dan Purgert wrote:
[...]
> Whoops, could've sworn I had the link in there too. Curse
> telemarketers.
:-)
Cheers
-- t
signature.asc
Description: Digital signature
On 2019-11-01 16:47, mick crane wrote:
On 2019-11-01 16:18, Gene Heskett wrote:
lsof |grep www-data shows me several hundred lines of "no perms"
errors
without nameing the source of the errors other than apache2. How do I
find the file causing those errors? Thats question #1 here.
excuse
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
wrote:
> On Fri, Nov 01, 2019 at 04:29:38PM -, Dan Purgert wrote:
>> Gene Heskett wrote:
>>> [...]
>>> Humm. in /var/log/httpd/other_vhosts_access.log, is looks as if both
>>> www.yandex.com/bots and www.semrush.com/bot.html are trying to
>>>
On Friday 01 November 2019 12:29:38 Dan Purgert wrote:
> Gene Heskett wrote:
> > [...]
> > Humm. in /var/log/httpd/other_vhosts_access.log, is looks as if both
> > www.yandex.com/bots and www.semrush.com/bot.html are trying to
> > download all of my nitros9 stuff, which is a unix like OS for the
On 2019-11-01 16:18, Gene Heskett wrote:
lsof |grep www-data shows me several hundred lines of "no perms" errors
without nameing the source of the errors other than apache2. How do I
find the file causing those errors? Thats question #1 here.
excuse my ignorance.
You've got files have no
On Fri, Nov 01, 2019 at 04:29:38PM -, Dan Purgert wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Gene Heskett wrote:
> > [...]
> > Humm. in /var/log/httpd/other_vhosts_access.log, is looks as if both
> > www.yandex.com/bots and www.semrush.com/bot.html are trying to download
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gene Heskett wrote:
> [...]
> Humm. in /var/log/httpd/other_vhosts_access.log, is looks as if both
> www.yandex.com/bots and www.semrush.com/bot.html are trying to download
> all of my nitros9 stuff, which is a unix like OS for the trs-80 color
>
I run apache2 in a www-data sandbux, so I occasionally see some network
traffic as someone downloads what I offer on my web page.
gkrellm is showing heavy, at my upload bandwith limit traffic. and has
been for a couple hours.
But that not enough to point htop fingers at the perp.
lsof |grep
36 matches
Mail list logo
