Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It seems "It's me" is the most popular port knocking client for windows…

Except… it sucks. It works for console-savvy users such as me, but, unsurprisingly, all my users (3 people) hate console windows. I know better than to force it upon them.

I would love to have a nice port knocker for Windows that would be windowed, have launchers, and be easily provisionable (i.e. I tell my user to paste some settings or import some file by double clicking it). To be honest, just not being console-based would be enough.

Edit: Please stop trying to convince me not to use port knocking. You're trying to solve a different problem than the problem port knocking solves. Whether port knocking is a good solution or not is irrelevant to this question.

share|improve this question

closed as off-topic by Michael Hampton Feb 23 at 10:02

This question appears to be off-topic. The users who voted to close gave this specific reason:

If this question can be reworded to fit the rules in the help center, please edit the question.

    
Is scripting IM with a .bat file an option? A console window would pop up (presumably with some nice, user-friendly and -assuring messages), sure, but then go away with no actual interaction necessary. Or do you need a solution where your users can select which ports to knock on? – Kromey Apr 7 '11 at 0:34
    
Port knocking, at it's best is merely security by obscurity and at it's worst, adds significant complexity to something that does not need to be complex. What services are you trying to protect using port knocking? – EEAA Apr 7 '11 at 1:29
1  
@ErikA: Not necessarily limited to "by obscurity". knockknock uses strong encryption to authenticate the requests. – grawity Apr 7 '11 at 5:23
2  
@ErikA: I already do. The failed attempts still pollute my logs and use up resources in other ways. Security through obscurity is insufficient, but it isn't unnecessary. – Ekevoo Apr 7 '11 at 19:44
1  
This is a question about clients, not servers. Changing the server is out of scope of this question by definition. That's all there is to this. – Ekevoo Nov 29 '12 at 21:14

you could use the http://sourceforge.net/projects/knockknock/ it has a simple GUI to add the ports that you want to knnock.

share|improve this answer

You should try this one: Windows Port Knocking Application.

It really suits well to my implementation of port knocking on my server! It has a simple GUI with basic options.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.