On 25/02/2021 17:02, David Sommerseth wrote:
On 25/02/2021 17:56, tincanteksup wrote:
How about ...
On 25/02/2021 01:03, tincanteksup wrote:
Keeping up with the internet is hard:
https://squeeze.isobar.com/2019/04/11/the-sad-story-of-tcp-fast-open/
I guess the bottom line is: Use UDP, if yo
On 25/02/2021 17:56, tincanteksup wrote:
How about ...
On 25/02/2021 01:03, tincanteksup wrote:
Keeping up with the internet is hard:
https://squeeze.isobar.com/2019/04/11/the-sad-story-of-tcp-fast-open/
I guess the bottom line is: Use UDP, if you are worried about TCP SYN
to your server.
I
dang!
On 25/02/2021 16:56, tincanteksup wrote:
How about ...
On 25/02/2021 01:03, tincanteksup wrote:
Keeping up with the internet is hard:
https://squeeze.isobar.com/2019/04/11/the-sad-story-of-tcp-fast-open/
I guess the bottom line is: Use UDP, if you are worried about TCP SYN
to your serv
How about ...
On 25/02/2021 01:03, tincanteksup wrote:
Keeping up with the internet is hard:
https://squeeze.isobar.com/2019/04/11/the-sad-story-of-tcp-fast-open/
I guess the bottom line is: Use UDP, if you are worried about TCP SYN to
your server.
Instead of UDP..
Use --port-share and have
On Thu, Feb 25, 2021 at 09:17:11AM +0100, Jan Just Keijser wrote:
> send raw packets. On linux this is possible, not sure about Windows, but
> it's definitely a no-no on Android or iOS.
If DDoS or cracking attempt is a problem with your setup, and port-knocking is
not applicable, why not add a sim
On 25/02/21 08:12, Marc SCHAEFER wrote:
On Wed, Feb 24, 2021 at 10:49:56PM +, tincanteksup wrote:
My idea (as daft as it is) would only serve one purpose: To hide a
listening TCP port. Because there would be no SYN-ACK from the server if
the SYN failed security checks.
This is what port
