ssl

Checklist

• Dependencies installed
• No typos
• Searched existing issues and docs

Issue Description

When using the RateLimiter Middleware with a rate between 0 and 1 all events will be rejected instead of applying the specified rate. E.g.: e.Use(middleware.RateLimiter(middleware.NewRateLimiterMemoryStore(0.5)))

I am not saying that it is a common use case to have

Information

Browser Info

Details

Description

The translation for "Copy a base64 string of the compressed config" will revert to English after clicked. Also, the "Copied" text isn't translatable.

Steps to reproduce

Scroll down to Download section and "click on the Copy a base64 string of the compressed config" link.

Reported by @botovq:

The public API exposes the AFI using X509v3_addr_get_afi(), but doesn't
expose the SAFI. The SAFI can only be fed into the API but not be read
from it. Another unfortunate thing about X509v3_addr_get_afi() is that it
uses the reserved AFI 0 as an in-band error. It does not care about the
reserved AFI 65535.

Context and Description

The READMEs and any example code in all projects should be updated to reflect the move from the IBM-Swift organization to the Kitura organization.

If anyone wants to take on all or part of this, please comment here so other's know what you're working on and submit PR's. :-)

Thanks!

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

Expected Behavior

When making a request with headers "Connection: keep-alive, Upgrade; Upgrade: websocket", the keep-alive should be ignored when checking if the request should be served by a Websocket, per IETF protocol document, the Connection header must include Upgrade, but is not limited to exactl

Problem:

A common pattern is:

GUARD(s2n_stuffer_skip_write(stuffer, bytes_to_write));
uint8_t* ptr = suffer->blob.data + stuffer->write_cursor - bytes_to_write;

which could be simplified.

Solution:

*ptr could be an *out parameter to s2n_stuffer_skip_write

• Does this change what S2N sends over the wire? No.
• Does this change any public APIs? No.