These types of attacks don't seem directed -- it's more like fishing
for unprotected systems.
FWIW, changing the ssh port dropped the illegal user attempts to 0 instantly...
- ben
On Mon, 10 Jan 2005 23:29:10 -0800, Ted Mittelstaedt
[EMAIL PROTECTED] wrote:
If I'm going to attack you I'm
Thanks for the input, everyone! Port-knocking is overkill at this
point, but I did do the following things to sshd_config:
Set port to non-default
PermitRootLogin no
LoginGraceTime 45s
AllowUsers lists only one user -- me. :)
I also did route -nq add -host xxx.xxx.xxx.xxx 127.0.0.1 -blackhole...
Hello again,
My 5.3R system has only been up a little over a week, and I've already
had a few breakin attempts -- they show up as Illegal user tests in
the /var/log/auth.log... It looks like they're trying common login
names (probably with the login name used as passwd). It takes them
hours to
Hello,
I seem to be having some issue with saslauthd and postfix on 5.3-R...
When I try to send mail out, it fails, and puts this in
/var/log/maillog:
Jan 4 05:56:17 n00330 postfix/smtpd[8103]: warning: SASL
authentication failure: cannot connect to saslauthd server: No such
file or directory
Thanks, though I've switched to qpopper, and it's working fine. Now my
only problem is trying to get postfix working with TLS and SASL. I'm
working off of these instructions:
http://yocum.org/faqs/postfix-tls-sasl.html
But even though postfix and saslauthd are running with no problems, I
can't
Hey everyone,
I'm a n00b to FreeBSD, and I'm trying to install courier-imap with
5.3, but I'm not sure what steps I should be taking. I did:
pkg_add -r courier-imap
However, when I do:
/usr/local/libexec/courier-imap/imapd.rc start
(as the courier-imap manual instructs), it gives me:
Martin,
Thanks for the quick reply! I ran
/usr/local/etc/rc.d/courier-imap-pop3d.sh.sample (because I'm trying
to run a POP3 server) and now I get:
/usr/local/etc/courier-imap/pop3d does not exist, forgot make install-configure?
Where would the pkg_mesg file be?
- ben
On Sat, 1 Jan 2005
Should I be using qpopper instead?
- ben
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Cool -- so now I think I may have the daemon running -- ps ax | grep
pop reveals:
564 p0 I 0:00.00 /usr/local/sbin/courierlogger pop3d
However, I'm unable to connect via a POP3 client...
I'm not sure what my /etc/inetd.conf line should look like -- I'm using:
pop3stream tcp nowait
