search for: kruijff

Derek Ragona wrote: >> I tried to implement a similar scheme in my hosts.allow on a FreeBSD >> 5.2.1 server. But when I try to test it from an IP outside my LAN, it >> still allows ssh logins. I even put in a line in hosts.allow to >> explicitly deny the IP I was ssh'ing from, but it still let me in. >> The behavior gives the appearance that TCP wrappers

Hi, Is there a security problem with ssh that I've missed??? Ik keep getting these hords of: Failed password for root from 69.242.5.195 port 39239 ssh2 with all kinds of different source addresses. They have a shot or 15 and then they are of again, but a little later on they're back and keep clogging my logs. Is there a "easy" way of getting these ip-numbers added to

Good Day, Please cc me ( eperrin@cseven.ca ) on responses to this, I am not on either mailing list anymore. I cvsup'ed on the STABLE branch today (September 9th) at around 2:30PM EDT. No problems with buildworld or kernel build, but I am getting failures during installworld Error and output from uname -a are below. vm/pmap.h -> vm/pmap.ph vm/swap_pager.h -> vm/swap_pager.ph vm/vm.h

How 'bout PAM? /usr/ports/security/pam_ldap. If you have machines that can't do PAM, perhaps NIS is the way to go (assuming, of course, you're behind a firewall). You can store login information in LDAP like you want, then use a home-grown script to extract the information to a NIS map. Or, if you have a Solaris 8 machine lying around, you can cut out the middle step and use