Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only first knock recognised #2

Open
lcapriotti opened this issue Sep 11, 2014 · 12 comments
Open

Only first knock recognised #2

lcapriotti opened this issue Sep 11, 2014 · 12 comments

Comments

@lcapriotti
Copy link

Using knockd on server side (both debian wheezy and ubuntu trusty), I set a sequence of knocks like:

sequence = 20xx,30yy,20xx

and while I can have the sequence correctly processed with latest Kitty ssh client, using this plugin only the knocks on the first port are received, ie a port knocking sequence configured as above results in the following on the syslog:

Sep 11 10:01:49 mynas knockd: aa.bb.cc.dd: SSH: Stage 1
Sep 11 10:01:52 mynas knockd: aa.bb.cc.dd: SSH: Stage 1

@horstk
Copy link

horstk commented Oct 26, 2014

Same problem here. I think I found the reason for this problem. According to the logfiles of my server every knock will be sent twice.

@lcapriotti
Copy link
Author

I managed to have the plugin work flawlessly by using pauses between knocks.
In case of high latency connections it is critical to be able to decrease the knock rate, kudos to developers to have this feature right away, I'm now struggling with Kytty that does not have this functionality (yet).

@flabbergast
Copy link

I have the same issue - that individual "knocks" are sent twice (so only the first once is recognised as valid, but the second knock on the first port invalidates the sequence). I had to rewrite my iptables based knocking to see double knocks as allowed behaviour.
Using pauses between knocks does not help in my situation.

@apeyroux
Copy link

I have the same issue

@uvjim
Copy link

uvjim commented Feb 17, 2015

Same issue here. Only the first knock is seen. Occasionally the second knock will be seen but pauses do not help me either.

Using Debian Jessie and knockd on the server side.

Edit: I can now confirm that I see a double knock as well.

@adrianke
Copy link

I did also experience the double knock bug. My workaround: Use UDP packets instead.

@fhfa
Copy link

fhfa commented Nov 25, 2015

Greetings.
I've also experience this issue, pauses did not help either. Only using UDP packets.

@jheiselman
Copy link

Switching from TCP packets to UDP packets resolved this issue for me.

@OvoiDs
Copy link

OvoiDs commented Apr 2, 2016

Same as well. UDP did the trick !

@gioalex
Copy link

gioalex commented Jan 16, 2017

Duplicated tcp packet also for me.
I've bought juicessh... why no support for this piece of software??
regards
Alessandro

@jheiselman
Copy link

@gioalex my guess is because while the app makes the devs money, the plugins do not, so they don't support them. Kind of sucks because you expect such a good app to have good support for all of its features.

@HelLViS69
Copy link

Same problem here. TCP packets are sent twice.. using only UDP worked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests