From: Ken A <ka@pacific.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: a whitelist for outgoing syn port 80, 443 traffic for hosting
Date: Wed, 07 Feb 2007 11:09:04 -0800 [thread overview]
Message-ID: <45CA23D0.5050702@pacific.net> (raw)
In-Reply-To: <45CA1D0E.2040603@yahoo.co.uk>
franck wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ken A wrote:
>> Hello,
>>
>
> Hi,
>
>> Is anyone aware of a whitelist of hostnames of port 80,443 OUTGOING
>> traffic that should be considered 'normal' in a hosting environment?
>> ie: SYN traffic to ups.com, authorize.net, technorati, for ecommerce,
>> blogging, etc..
>>
>> Categorizing traffic as good/bad is useful in this day of many php
>> remote file include bugs.
>>
>> Thanks,
>
> Maybe this is what you are looking for :
>
> http://someonewhocares.org/hosts/zero/
Thanks, but I'm looking for a whitelist for a fairly wide range of web
applications, not a blacklist. There are plenty of good blacklists out
there. surbl.org, uribl.com , etc. :-)
Ken
>
> - --
> Franck Joncourt
> http://www.debian.org
> http://smhteam.info/wiki/
> GPG server : pgpkeys.mit.edu
> Fingerprint : C10E D1D0 EF70 0A2A CACF 9A3C C490 534E 75C0 89FE
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFyh0NxJBTTnXAif4RAoThAKDXxecdEq5gWmncfj7TmOcb5EAdbgCfZrnx
> S/QzndrwWbq1CPhal5eQy8k=
> =mf7k
> -----END PGP SIGNATURE-----
>
>
> ___________________________________________________________
> The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
>
>
next prev parent reply other threads:[~2007-02-07 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:23 a whitelist for outgoing syn port 80, 443 traffic for hosting Ken A
2007-02-07 18:40 ` franck
2007-02-07 19:05 ` Grant Taylor
2007-02-07 19:09 ` Ken A [this message]
2007-02-07 20:24 ` franck
2007-02-08 18:15 ` R. DuFresne
2007-02-08 19:04 ` Ken A
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=45CA23D0.5050702@pacific.net \
--to=ka@pacific.net \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.