From: "James Stull" <rivitir@gmail.com>
To: gentoo-security@lists.gentoo.org
Subject: Re: [gentoo-security] TCP Wrapper Documentation
Date: Mon, 12 Jan 2009 19:32:04 -0500 [thread overview]
Message-ID: <c1dd97640901121632r6cb6be78k5a8dcf9c966fe3ca@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0901121148060.27244@beaker.tnarb.net>
[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]
Thank you for all the suggestions, they have been very helpful and I now
have my tcp wrappers up and running.
Just out of curiosity, why doesn't the ebuild install /etc/hosts.allow/deny
with some basic configuration examples or at least empty files?
On Mon, Jan 12, 2009 at 12:50 PM, brant williams <brant@tnarb.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
> Hi there...
>
> You can also install the "DenyHosts" package, which will parse your syslog
> for failed ssh entries, and then update/maintain /etc/hosts.{allow,deny}.
>
> http://denyhosts.sourceforge.net/
>
> You can run it as a daemon, or from within cron.
>
> hth
> - -brant
>
> brant williams
> FCAA CDCA 20BC 3925 D634 F5C4 7420 6784 4DEB 6002
>
>
>
> On Sat, 10 Jan 2009, Chris O'Regan wrote:
>
> Date: Sat, 10 Jan 2009 00:51:47 -0500
>> From: Chris O'Regan <chris.oregan@gmail.com>
>> Reply-To: gentoo-security@lists.gentoo.org
>> To: gentoo-security@lists.gentoo.org
>> Subject: Re: [gentoo-security] TCP Wrapper Documentation
>>
>>
>> Search for "tcp wrappers howto" on Google. Yes, this must be
>> maintained manually. I recommend to do away with /etc/host.deny and
>> have "ALL :ALL@ALL :deny" as the last line of /etc/hosts.allow.
>>
>> On Fri, Jan 9, 2009 at 11:51 PM, James Stull <rivitir@gmail.com> wrote:
>>
>>> I have a gentoo desktop profile system and I would like to use tcp
>>> wrappers
>>> to secure certain services like ssh. I followed the documentation I could
>>> find from the security guide to install the ebuild but I don't have the
>>> /etc/hosts.allow or hosts.deny. Do I have to manually create these? Is
>>> their
>>> any other documentation available that I can use to help me install and
>>> configure it properly?
>>>
>>> Thanks for your help.
>>>
>>>
>>
>> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
>
> iEYEAREIAAYFAklrgtkACgkQdCBnhE3rYAIsLQCgpLxynaOGVdxWlKh7YeOdpIC5
> oggAnRFgIwBudFTonqx2/ABUSdzDWNLx
> =N70i
> -----END PGP SIGNATURE-----
>
>
[-- Attachment #2: Type: text/html, Size: 3050 bytes --]
next prev parent reply other threads:[~2009-01-13 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 4:51 [gentoo-security] TCP Wrapper Documentation James Stull
2009-01-10 5:51 ` Chris O'Regan
2009-01-12 17:50 ` brant williams
2009-01-13 0:32 ` James Stull [this message]
2009-01-14 21:17 ` Matt Drew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1dd97640901121632r6cb6be78k5a8dcf9c966fe3ca@mail.gmail.com \
--to=rivitir@gmail.com \
--cc=gentoo-security@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox