On Thu, 30 Sep 2004 21:31:46 +0200 Matthijs <[EMAIL PROTECTED]> wrote:
> On Wed, 29 Sep 2004 23:10:11 +0200, Jacob S <[EMAIL PROTECTED]> > wrote: > > > On Wed, 29 Sep 2004 21:55:59 +0200 > > Matthijs <[EMAIL PROTECTED]> wrote: > > > > > It's not really what you're asking, but: > > > In the dutch computer magazine C't, I read an article a few months > > > ago about protecting your computer using a port knocking system. > > > If I remember correctly, you can close a port (your SSH port, for > > > example) and only open it when a pre-defined pattern of access > > > attempts on a pre-defined port (unused for applications) is > > > applied. The SSH port can then be set to open in your firewall, > > > perhaps only for the IP-adress that performed the knocking > > > sequence. > > > > hmm... You're right, it's not what I'm looking for, but it still > > sounds like a good concept. I'd be interested in learning more about > > that, if not for this use with ssh, I have a couple other > > applications it could work with on servers. > > Short note in advance: I've only read the article, I use neither this > portknocking stuff nor the iptables firewall (well, at least not that > I'm really aware of). So I can't be held responsible for mistakes in > the article that I've copied below... > > OK, here's some info from the article (Dutch C't september 2004, page > 112-114): > > Port knocking project by Martin Krzywinski: > http://www.portknocking.org <snip - great information and details about software from above url> Sounds neat. I can't wait to give it a try. Thanks! Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
