From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Cross compiling, etc
Date: Fri, 25 Jun 2004 11:28:40 +0100 [thread overview]
Message-ID: <200406251128.40113.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <40DBF710.1020200@4Dllc.com>
On Friday 25 June 2004 10:57 am, Steve Comfort wrote:
> Hi gents,
>
> I've sorted out the problems with my cross compilation. I hadn't noticed
> that the linker was using ar instead of arm-linux-ar. So, no more
> truncations and iptables with my semi-trivial little script appears
> hunky-dory. (Just tested on ping limits so far).
>
> Next question is whether you gurus can recommend any good test app that
> I can use for checking my rules and seeing whether there any holes?
nmap?
http://www.insecure.org
Antony.
--
There are two possible outcomes:
If the result confirms the hypothesis, then you've made a measurement.
If the result is contrary to the hypothesis, then you've made a discovery.
- Enrico Fermi
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-06-25 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 9:57 Cross compiling, etc Steve Comfort
2004-06-25 10:28 ` Antony Stone [this message]
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=200406251128.40113.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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