4 ms·
Nothing stopping you from HMACing the request IP+time with whatever crypto function you like and sending it in a series of encoded port knocks. The only issue
by zamadatix 7y ago
Nothing stopping you from HMACing the request IP+time with whatever crypto function you like and sending it in a series of encoded port knocks.
The only issue I've run into with port knocking is places that heavily restrict outbound ports/protocols. Though technically that is solvable too I just haven't bothered.
- exabrial 7y agoIt's still sent in the clear and observable by anyone that see your network traffic.
- zamadatix 7y agoThe only things in clear text are your currently IP, the time, and the AES signature. The attacker doing a packet capture already knows your IP and probably owns a watch but it's unlikely they know how to break AES to sign a modified message as you.