From: "R. DuFresne" <dufresne@sysinfo.com>
To: "Ashley M. Kirchner" <ashley@pcraft.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Re: iptables problem
Date: Thu, 3 Nov 2005 22:18:09 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.60.0511032216061.9195@darkstar.sysinfo.com> (raw)
In-Reply-To: <436AB088.7050502@pcraft.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 3 Nov 2005, Ashley M. Kirchner wrote:
> R. DuFresne wrote:
>
>> Why not have one system that reaches out for the files, and brings them
>> inside, then point the kiosks at that one system? Far easier to maintain
>> and troubleshoot and far less FW coding.
>
> Because I didn't code these machines. They are proprietary and third
> party to us.
>
>
Interesting, and that means I suspect that you have no ability to tune or
config them as well? Could one put in a request the third parties config
them to look at one trusted host you could setup to pull the files from?
Have they been "tested" for their security? Seems a tad risky, depending
upon placement, hopefully they are in a dmz and not the soft chewy
center....
Thanks,
Ron DuFresne
- --
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
admin & senior security consultant: sysinfo.com
http://sysinfo.com
Key fingerprint = 9401 4B13 B918 164C 647A E838 B2DF AFCC 94B0 6629
...We waste time looking for the perfect lover
instead of creating the perfect love.
-Tom Robbins <Still Life With Woodpecker>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFDatL0st+vzJSwZikRArWLAKDA/urNj4sEruwm7KU8ezInKPLpJQCeJk+R
MFr5oi+c3stQZx0mqQJgqmE=
=Z32v
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-11-04 3:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 18:06 iptables problem Ashley M. Kirchner
2005-11-02 0:31 ` Buddy wu
2005-11-02 1:29 ` Ashley M. Kirchner
2005-11-02 1:37 ` Buddy wu
2005-11-02 5:56 ` Rob Sterenborg
2005-11-02 7:20 ` Nikolai Georgiev
2005-11-02 8:01 ` Rob Sterenborg
2005-11-02 22:49 ` Ashley M. Kirchner
2005-11-03 6:19 ` Rob Sterenborg
2005-11-03 6:45 ` Ashley M. Kirchner
2005-11-03 15:21 ` Re: iptables problem (nfcan: addressed to exclusive sender for this address) Jim Laurino
2005-11-03 16:02 ` Ashley M. Kirchner
2005-11-03 16:23 ` Sven Schuster
2005-11-03 17:17 ` Re: iptables problem (nfcan: addressed to exclusivesender " Rob Sterenborg
2005-11-03 17:00 ` Re: iptables problem (nfcan: addressed to exclusive (nfcan: addressed to exclusive sender for this address) sender " Jim Laurino
2005-11-03 19:57 ` Ashley M. Kirchner
2005-11-04 5:00 ` Re: iptables problem (nfcan: addressed to exclusive (nfcan: addressed to exclusive sender for this address) " Jim Laurino
2005-11-04 5:06 ` Ashley M. Kirchner
2005-11-04 6:04 ` Rob Sterenborg
2005-11-03 21:54 ` Re: iptables problem R. DuFresne
2005-11-04 0:51 ` Ashley M. Kirchner
2005-11-04 3:18 ` R. DuFresne [this message]
2005-11-04 4:26 ` Ashley M. Kirchner
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=Pine.LNX.4.60.0511032216061.9195@darkstar.sysinfo.com \
--to=dufresne@sysinfo.com \
--cc=ashley@pcraft.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