Date: Mon, 29 Jul 2002 09:53:40 -0400 From: "Joe White" <joe@edgehosting.com> To: <freebsd-isp@FreeBSD.ORG> Subject: Re: SSHD Lockdown Message-ID: <006201c23707$582b80e0$0a800a0a@edgehosting.com> References: <000d01c23703$b55e9760$c905010a@daylight.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Errr.. sorry about that, 'twas a typo. I WILL be implementing IPF. But does anyone else have any suggestions on the server side of things? config file changes for SSHD ? Thanks for all the responses so far! ----- Original Message ----- From: "John Brooks" <john@day-light.com> To: <freebsd-isp@FreeBSD.ORG> Sent: Monday, July 29, 2002 9:27 AM Subject: RE: SSHD Lockdown > ipf is easy to implement and would accomplish your task, why not use it? > > -- > John Brooks > john@stlbsd.org > > > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG [mailto:owner-freebsd-isp@FreeBSD.ORG]On > Behalf Of Joe White > Sent: Monday, July 29, 2002 8:19 AM > To: freebsd-isp@FreeBSD.ORG > Subject: SSHD Lockdown > > > I'm looking for the best way to secure SSHD. I'm creating a new server, > where only 2 other boxes should be able to access via SSH, and I was > wondering what the best way to allow those 2, and only those 2 boxes to > access it. Anything outside of SSHD daemon that could also help? I'm going > to implement tcpwrappers as well, but not packet filtering software (ipfw / > ipf). Any suggestions would be greatly appreciated. > > Cheers! > Joe White > Edge Networking Solutions > http://www.edgenetworkingsolutions.com > jwhite@EdgeNetworkingSolutions.com > 248.561.2827 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006201c23707$582b80e0$0a800a0a>