-
Updated
May 23, 2020 - Go
socket
Here are 2,849 public repositories matching this topic...
-
Updated
May 23, 2020 - PHP
Sometimes you see this message in Nmap output:
Warning: xxx.xxx.xxx.xxx giving up on port because retransmission cap hit (10).
It would be nice to add the port number here as well, in case you want to manually investigate that host and port after the scan has finished.
Something like:
Warning: xxx.xxx.xxx.xxx giving up on port 12345/tcp because retransmission cap hit (10).
``
-
Updated
May 21, 2020 - Objective-C
-
Updated
May 26, 2020 - JavaScript
I tested with the documentation of this repository but it doesn't work for me.
Please. How can I write a log file in hard disk?
Thanks.
-
Updated
May 12, 2020 - Go
-
Updated
Jan 10, 2020 - Java
-
Updated
Feb 24, 2017 - Java
The facebook page says:
App not set up: This app is still in development mode, and you don't have access to it. Switch to a registered test user or ask an app admin for permissions.
-
Updated
Mar 7, 2020 - Java
-
Updated
Apr 24, 2020 - Swift
-
Updated
Jan 16, 2019 - Objective-C
-
Updated
May 10, 2020 - Java
-
Updated
May 25, 2020 - PHP
-
Updated
May 21, 2020 - PHP
-
Updated
Feb 7, 2019 - C#
Improve this page
Add a description, image, and links to the socket topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the socket topic, visit your repo's landing page and select "manage topics."
Currently, testssl prints a big red warning when a server has no server preferred cipher order.
Mozilla recently relaxed their recommendations regarding cipher order. If only strong cipher suites are supported anyway, why not deciding according to the client's preferences. Maybe it's a phone that wants to optimize for performance on low hardware. Additionally, often browsers are better maintain