Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

download: link to Rock-solid curl #405

Closed
wants to merge 3 commits into from
Closed

download: link to Rock-solid curl #405

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5790406
download: link to Rock-solid curl
bagder Nov 7, 2024
028f65d
CVE-2024-9681.md: avoid the use of the word "will"
bagder Nov 7, 2024
aa8fded
fixup CVE-2024-9681.md words
bagder Nov 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions _download.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,12 @@
</tr>
</table>

SUBTITLE(Long-term support)
<p>
There are long-term support curl releases
called <a href="https://rock-solid.curl.dev/">Rock-solid curl</a>, provided
as a commercial offer.

SUBTITLE(Packages)
<p>
#include "dl/files.html"
Expand Down
6 changes: 3 additions & 3 deletions docs/CVE-2024-9681.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ was otherwise intended to *possibly* be protected.
But:

`example.com` as per above is deliberately setup for HSTS, and servers should
probably expect that clients will try upgrading to HTTPS for a while outside
probably expect that clients might try upgrading to HTTPS for a while outside
of the time range set in its headers.

The access that fails in this scenario tries to use plain HTTP to the domain.
Expand All @@ -56,8 +56,8 @@ ends up in now and then completely without involving curl issues and therefore
needs to have logic for. An application can for example work around the
situation by simply toggling off HSTS.

This bug is **not** considered a *C mistake* (ie not likely to have been
avoided had we not been using C).
This bug is **not** considered a *C mistake* (not likely to have been avoided
had we not been using C).

This flaw also affects the curl command line tool.

Expand Down
Loading