From: George Alexandru Dragoi <waruiinu@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Port 21, 23, and 80 are open according to Shields Up at grc.com
Date: Mon, 13 Sep 2004 04:15:22 +0300 [thread overview]
Message-ID: <3063e504091218152748ca34@mail.gmail.com> (raw)
In-Reply-To: <8ca4228204091200382f2d9a04@mail.gmail.com>
Ok, I was tired :)
I thought the Gibson stuff is some sort of web page used to scan, so i
thought you scanned 192.168.0.0/24 from some webpage, that's why my
answer (i was even worse tired, i thought that page is located at
insecure.org, that was actually the result of nmap output). I am
curious how that test explain the manner HOW the ports are opened.
Maybe they are just not filtered.
On Sun, 12 Sep 2004 03:38:48 -0400, Mike <1100100@gmail.com> wrote:
> I don't understand this response.
>
>
>
> On Sun, 12 Sep 2004 02:14:58 +0300, George Alexandru Dragoi
> <waruiinu@gmail.com> wrote:
> > Maybe insecure.org has theyr own 192.168.0.0 private LAN :)
>
--
Bla bla
next prev parent reply other threads:[~2004-09-13 1:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 18:50 MAC addresses Darren Kirby
2004-09-11 20:01 ` active
2004-09-13 15:57 ` Jose Maria Lopez
2004-09-13 20:03 ` srg
2004-09-11 21:31 ` Frank Gruellich
2004-09-11 22:23 ` Jason Opperisano
2004-09-12 0:26 ` Darren Kirby
2004-09-12 0:54 ` Jason Opperisano
2004-09-12 1:14 ` Darren Kirby
2004-09-12 2:30 ` Chris Brenton
2004-09-12 23:09 ` Darren Kirby
2004-09-11 23:09 ` Port 21, 23, and 80 are open according to Shields Up at grc.com Mike
2004-09-11 23:14 ` George Alexandru Dragoi
2004-09-12 7:38 ` Mike
2004-09-13 1:15 ` George Alexandru Dragoi [this message]
2004-09-13 12:35 ` Mike
2004-09-14 1:01 ` Nick Drage
2004-09-13 12:53 ` Jason Opperisano
2004-09-13 15:18 ` Mike
2004-09-13 21:22 ` James B. Hiller
2004-09-13 23:47 ` Mike
2004-09-14 5:09 ` Mike
2004-09-14 0:12 ` <SOLVED>Port " Mike
-- strict thread matches above, loose matches on Subject: below --
2004-09-13 15:21 Port " Miguel Laborde
2004-09-13 15:39 ` Mike
2004-09-13 16:04 ` Jose Maria Lopez
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=3063e504091218152748ca34@mail.gmail.com \
--to=waruiinu@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox