> it is your test methodology that is broken
Well, I said "I want the machine to be invisible", so I don't think
there is anything wrong with me testing which ports are open and
checking what I can do (besides pf) to close them.
Anyway, thanks for your help!
Cheers!
2018-03-19 8:07 GMT+01:00 Torsten :
> >> On my OpenBSD 6.2 syslogd is listening to port 514
> >> [...]
> >> prevent syslogd from opening that port in the first place?
>
> > If [...] no logging rules exist to send to a remote
> > host the socket is closed per default since 6.2. Perhaps you are logg
>> On my OpenBSD 6.2 syslogd is listening to port 514
>> [...]
>> prevent syslogd from opening that port in the first place?
> If [...] no logging rules exist to send to a remote
> host the socket is closed per default since 6.2. Perhaps you are logging
> to a remote host?
Thank you for you answe
> Am 16.03.2018 um 11:42 schrieb Torsten:
> > Hi!
> >
> > On my OpenBSD 6.2 syslogd is listening to port 514, even though it is
> > not started with "-r" (to receive remote syslog messages). It does not
> > actually seem to log anything if I send something to port 514 UDP,
> > however, I want the
Am 16.03.2018 um 11:42 schrieb Torsten:
> Hi!
>
> On my OpenBSD 6.2 syslogd is listening to port 514, even though it is
> not started with "-r" (to receive remote syslog messages). It does not
> actually seem to log anything if I send something to port 514 UDP,
> however, I want the machine to be
On Fri, March 16, 2018 6:42 am, Torsten wrote:
> I know I could use PF as a workaround
Really? I wouldn't consider blocking incomming connections to unused
ports by default to be a workaround, but a necessity.
Hi!
On my OpenBSD 6.2 syslogd is listening to port 514, even though it is
not started with "-r" (to receive remote syslog messages). It does not
actually seem to log anything if I send something to port 514 UDP,
however, I want the machine to be invisible when someone is probing for
open ports. I
7 matches
Mail list logo