-
Updated
Jun 13, 2022 - Go
socket
Here are 4,714 public repositories matching this topic...
-
Updated
Jul 6, 2022 - PHP
Which version are you referring to
3.1dev
We list not all RFCs in ~/doc/ which we refer to in testssl.sh.
List used RFCs: grep RFC -w ./testssl.sh | grep -v TLS_CIPHER | grep RFC | sed 's/^.*RFC/RFC/' | sort -u
List RFCs referred to: grep -w RFC doc/testssl.1
-
Updated
May 18, 2022 - Objective-C
-
Updated
Nov 16, 2021 - Go
-
Updated
Jun 9, 2022 - JavaScript
-
Updated
Oct 31, 2021 - TypeScript
-
Updated
Jan 10, 2020 - Java
-
Updated
Jun 26, 2022 - Go
-
Updated
Feb 24, 2017 - Java
-
Updated
Jun 22, 2022 - C
-
Updated
Oct 4, 2021 - Swift
-
Updated
Jul 1, 2022 - Go
-
Updated
Jun 24, 2022 - PHP
-
Updated
Jan 16, 2019 - Objective-C
-
Updated
Feb 7, 2019 - C#
-
Updated
Sep 12, 2021 - C#
-
Updated
Nov 3, 2018 - Go
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."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef