Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Ashley M. Kirchner" <ashley@pcraft.com>
To: netfilter@lists.netfilter.org
Subject: Re: Re: iptables problem
Date: Thu, 03 Nov 2005 21:26:48 -0700	[thread overview]
Message-ID: <436AE308.4040806@pcraft.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0511032216061.9195@darkstar.sysinfo.com>

R. DuFresne wrote:

> 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....

    Tested for security?  Does the fact that they transmit order details 
(including plain text client information and an encrypted CC string 
within the same file) via plain old FTP tell you anything?  Do I, 
personally, trust this system?  Oh HELL NO.  Would I, personally, use 
them to place any orders?  Oh HELL NO.  Do I have a choice in not using 
them?  Nope.  I'm merely the one that has to make them work...the big 
guys paid the money.

-- 
H | I haven't lost my mind; it's backed up on tape somewhere.
  +--------------------------------------------------------------------
  Ashley M. Kirchner <mailto:ashley@pcraft.com>   .   303.442.6410 x130
  IT Director / SysAdmin / WebSmith             .     800.441.3873 x130
  Photo Craft Imaging                       .     3550 Arapahoe Ave. #6
  http://www.pcraft.com ..... .  .    .       Boulder, CO 80303, U.S.A. 





      reply	other threads:[~2005-11-04  4:26 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
2005-11-04  4:26                   ` Ashley M. Kirchner [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=436AE308.4040806@pcraft.com \
    --to=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