Hello.
I'm trying to enable port knocking with `knockd'.
I configured `/etc/knockd.conf':
(I changed the default ports.)
[options]
UseSyslog
[openSSH]
sequence= 7000,8000,9000
seq_timeout = 5
command = /sbin/iptables -A INPUT -I 6 -p tcp --dport 22 -j
AC
I've read several threads about Logwatch. Many people say it's very
annoying. I think I'll stick with `by hand' approach. Anyway, it's not
convenient to use `more'. I'd like to try `grep' instead, but I don't
know the right words (like `Exim exploded' for `/var/log/mail.log' or
`PWN3D' for `/var/lo
Hello.
Some public networks don't allow to connect to port 25 or forbid
non-http traffic. How to check what ports are filtered/blocked? I
think it can be done with nmap, but I have never used it.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe".
Hello.
There are a lot of `possible break-in attempts' messages in my
logs. So it's hard to read them `by hand' (with last or more). How do
you read yours? Do you use any log analyzers? Which ones?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscrib
Hello.
I'm getting `warning:xsasl_cyrus_server_get_mechanism_list: no
applicable SASL mechanisms' (/var/log/mail.log) and `fatal: no SASL
authentication mechanisms' (/var/log/mail.err) in Squeeze.
Installed:
postfix: 2.7.1-1+squeeze1
libsasl2-2: 2.1.23.dfsg1-7
libsasl2-modules: 2.1.23.dfsg1-7
sa
5 matches
Mail list logo