Is your feature request related to a problem? Please describe.
The {{< highlight none >}} :~q:foo:bar {{< / highlight >}} blocks don't work on GitHub. It's confusing and makes the code examples almost useless on GitHub itself. And also in your code editor if you have Markdown syntax highlighting with embedded highlighting for nested code.

Describe the solution you'd like

It'd be ne

Issue Description

I updated echo in one of my projects. After that my static configuration didn't work without changes. Before it automatically resolved to an existing index.html. After that I had to point to that file.

My code was something like that:

docsGroup := e.Group("")
docsGroup.Static("/", "docs")

In docs is an index.html which was delivered when no path was given

Can you add Blake3 support to openssl? It's over 10x faster than sha2 and will probably be widely adopted.

Yoast SEO is a fairly popular WordPress plugin. I've found the nginxconfig.io breaks the sitemaps on every install I've done.

In /etc/nginx/nginxconfig.io/wordpress.conf we could add

# WordPress SEO
location = /wp-content/plugins/wordpress-seo/css/main-sitemap.xsl {}
location = /wp-content/plugins/wordpress-seo-premium/css/main-sitemap.xsl {}

Above the # WordPress: line

I want to develop an iOS application that hosts its own web server (https://myiphone.server/index.html) on an iPad or iPhone users can access from a PC or Mac or other phone. Is this possible with Kitura? What level of support does this have? And are there any documentation or examples I can get started with? Thank you

Context

When another mailserver attempts to send an email to the one set up with this docker compose set up over IPv6, the mail will be incorrectly processed by SPF protection.

Expected Behavior

The SPF check is run against the originating IPv6 address

Actual Behavior

The SPF check is run against the IPv4 gateway that docker is using to proxy the IPv6 connection (172.20.0.1 is th

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

Problem:

When you initialize a stuffer with an existing blob, the typical pattern is to write

struct s2n_blob blob;
struct s2n_stuffer stuffer;

GUARD(s2n_stuffer_init(&stuffer, &blob));
GUARD(s2n_stuffer_write(&stuffer, &blob));

This causes a memcpy to write to overlapping pages, which is undefined behavior. A workaround is to use s2n_stuffer_raw_write, but this st

A Spring Boot user has reported a problem with Spring Boot's reference documentation linking to Jetty's documentation. Spring Boot's reference documentation links to the Jetty documentation for the specific version of Jetty that it built against. For example, the documentation for Spring Boot 2.2.4 links to https://www.eclipse.org/jet

https://www.boost.org/doc/libs/1_71_0/libs/beast/doc/html/beast/using_websocket/timeouts.html says

The timeout features of the TCP or basic stream should not be used when working with a websocket stream.

and

`The timeouts on the websocket stream are incompatible with the timeouts used in the tcp_stream. When constructing a websocket stream from a tcp stream that has timeouts enabled, th

To encourage people to use wss/tls encryption, we should make it really simple for people to implement a signed cert using letsencrypt.org (which should be going into general availability in the next couple of months). Perhaps direct automatic integration (since that's one of the goals of Let's Encrypt), but at least, we should document a straightforward process for using it.

The process is docum

Description

• Type: Bug
• Priority: Minor

Bug

This document should be updated and/or renamed now that mbed-crypto has been merged back in mbedtls.

With the “keycloak” provider the cookie-refresh feature does not work. Instead of using the refresh token for acquiring a new access token in the background, the user is redirected to Keycloak.

Expected Behavior

Given a web page which is protected by OAuth2 Proxy configured to use Keycloak as the identity provider
and given a user has authenticated and has loaded the page
when the user

it got updated to use only use TLS 1.3, but currently mozilla-modern.badssl.com only use tls 1.2 so it clearly not set to current version of 'modern' configuration. so it need to updated.
actually, it looks like pushed though a level down ( old modern-> intermediate, old intermediate -> now old )
https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility

This basically the same as certbot/certbot#1215 but for acmetool. I want to change the contact e-mail for accounts created by acmetool.

I just tried to "import" the acmetool account to certbot but failed doing it. Is there any documentation on how to do this? Is it even possible?

Please provide a dummy's guide on this. It'll be invaluable to all. Thanks in advance.

Basically using letsencrypt cert on rustls. Best if comes with docker instance, else it's fine.

我按照http://gmssl.org/docs/quickstart.html 上的步骤在Ubuntu 16.04LTS上安装GmSSL，出现了以下错误：

Makefile:6850: recipe for target 'engines/sdf_dummy.o' failed
make[1]: *** [engines/sdf_dummy.o] Error 1
make[1]: Leaving directory 'home/usr/Downloads/GmSSL-master'
Makefile:128: recipe for target 'all' failed
make: *** [all] Error 2

请问一下我该如何解决这个错误呢？

It would be helpful if there were more examples for allow_domain. I.e. how to make an upstream http request and return true or false based on the response text. Another helpful example would be a shell script exit code.

The tool should be smart enough to support reading pkcs8 private keys.

Ideally, we should support writing pkcs8 private keys if the user desires.

While following the quick start instructions in the documentation I encountered this. When directed to run make release it will fail during the npm install portion. When I then run the command again, it succeeds.

npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.

> core-js@2.6.9 pos