Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>I... er, did?

You... Ugh... Didn't? You claimed that it suffers from MITM attack. You are not able to prove that it suffers from any MITM attack (the docs specifically outline a way to mitigate a specific MITM attack, but do not outline any others). Unless you have a source that states otherwise, you're wrong.

>You're intercepting the packet and blocking it by being in the path.

Wrong, that is by definition not a MITM attack.

>Bastion hosts are generally SSH/RDP/VNC type affairs. SSH in to the bastion and then you have access to the other servers.

Correct, and you set up port knocking for these. Thanks for proving my point.

>This is actually how I set things up in production environments - the VPN concentrator only allows access to the jumphosts, and then there's extensive logging and auditing there.

There should be extensive logging and auditing on the bastion host. Port knocking reduces the noise to effectively 0.

>I'm not sure why Wireguard only supporting UDP would be a problem - you can pass whatever type of traffic inside of the tunnel.

There have been multiple instances where UDP has been block at sites in the past. Looks like you're ignorant to this. Look up why OpenVPN supports TCP.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: