ssl
Here are 2,113 public repositories matching this topic...
The documentation for X509_NAME_print says:
X509_NAME_print() prints out name to bp indenting each line by obase characters. Multiple lines are used if the output (including indent) exceeds 80 characters.
https://github.com/openssl/openssl/blob/master/doc/man3/X509_NAME_print_ex.pod
However, the implementation does not actually do this. obase and 80 figure into l, but l is decreme
Sorry for not following the template. It's a straightforward question.
By enabling "WordPress-specific rules", the following codes will be added to the wordpress.conf:
# WordPress: deny general stuff
location ~* ^/(?:xmlrpc\.php|wp-links-opml\.php|wp-config\.php|wp-config-sample\.php|readme\.html|license\.txt)$ {
deny all;
}
However, this disables xmlrpc feature, which disa
Production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) running inside a container.
-
Updated
Apr 10, 2022 - Shell
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!
Automated ACME SSL certificate generation for nginx-proxy
-
Updated
Apr 10, 2022 - Shell
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
I'm trying to build a container image with oauth2-proxy as base image for the linux/arm64/v8 platform.
Expected Behavior
The build is successful
Current Behavior
The build failes with error building image: no child with platform linux/arm64/v8 in index quay.io/oauth2-proxy/oauth2-proxy:v7.2.1
Possible Solution
The arm64 entry in the image index is missing the v8
Share your terminal over the web
-
Updated
Apr 10, 2022 - C
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.
Mbed TLS only supports 12-byte nonces for PSA_ALG_STREAM_CIPHER with PSA_KEY_TYPE_CHACHA20 and for PSA_ALG_CHACHA20_POLY1305. The PSA Crypto specification allows both 12-byte and 8-byte nonces
HTTP and WebSocket built on Boost.Asio in C++11
-
Updated
Mar 16, 2022 - C++
Eclipse Jetty® - Web Container & Clients - supports HTTP/2, HTTP/1.1, HTTP/1.0, websocket, servlets, and more
-
Updated
Apr 11, 2022 - Java
Websockify is a WebSocket to TCP proxy/bridge. This allows a browser to connect to any application/server/service.
-
Updated
Jan 10, 2022 - Python
Easily upload files (Multipart/Binary/FTP out of the box) in the background with progress notification. Support for persistent upload requests, customizations and custom plugins.
-
Updated
Mar 28, 2022 - Kotlin
Blackbox tool to disable SSL certificate validation - including certificate pinning - within iOS and macOS applications.
-
Updated
Mar 28, 2021 - Objective-C
An FTP and FTPS client for .NET & .NET Standard, optimized for speed. Provides extensive FTP commands, File uploads/downloads, SSL/TLS connections, Automatic directory listing parsing, File hashing/checksums, File permissions/CHMOD, FTP proxies, FXP support, UTF-8 support, Async/await support, Powershell support and more. Written entirely in C#, with no external dependencies.
-
Updated
Mar 9, 2022 - C#
-
Updated
Apr 1, 2021 - Go
Improve this page
Add a description, image, and links to the ssl topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the ssl topic, visit your repo's landing page and select "manage topics."


Checklist
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