secure
Here are 672 public repositories matching this topic...
-
Updated
Sep 25, 2021 - PHP
-
Updated
Sep 27, 2021 - TypeScript
-
Updated
Sep 18, 2021 - Java
-
Updated
Sep 27, 2021 - JavaScript
-
Updated
Sep 20, 2021 - PHP
-
Updated
Sep 21, 2021 - JavaScript
-
Updated
Sep 22, 2021 - JavaScript
-
Updated
Nov 20, 2020
-
Updated
Jan 25, 2020 - JavaScript
-
Updated
Aug 20, 2021 - JavaScript
-
Updated
Sep 4, 2021 - JavaScript
-
Updated
Apr 28, 2021 - JavaScript
-
Updated
May 8, 2021 - Rust
-
Updated
Mar 22, 2019 - PHP
-
Updated
Dec 9, 2019 - C
-
Updated
Sep 9, 2021 - Go
As hinted in aidantwoods/SecureHeaders#67 (comment), the public API could do with some better coverage.
Blocked by #2
-
Updated
Oct 27, 2020 - Go
Update all of the dependencies. Scan what is in our build, and if there is a new version then pull it in.
Note: some dependencies may require code updates to get working.
The approach is, update the dependency in question and run a built, if it works
Happy to track them here in a list and check them off:
- fs2 update to 2.4.4 or later
-
Updated
Sep 26, 2021 - C++
-
Updated
Sep 22, 2021 - HCL
Improve this page
Add a description, image, and links to the secure topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the secure topic, visit your repo's landing page and select "manage topics."
Describe the feature you'd like supported
We should change the CID after enough idle time so that any possible NAT rebinding would be harder to be tracked by an outside observer. The simplest way to implement this would be in the flush send code path. When first starting a flush, check how much time has elapsed since the last send. If it's greater than X (20? 30?) seconds force a CID update