boringssl
wgcf
Our great sponsors
boringssl | wgcf | |
---|---|---|
10 | 59 | |
1,719 | 5,467 | |
3.4% | - | |
6.5 | 7.7 | |
5 days ago | 20 days ago | |
C | Go | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
boringssl
-
New vulnerabilities (CVE-2022-3602 and CVE-2022-3786) in OpenSSL, how they affect IoT and RTOS Devices.
I have nothing constructive to add except that OpenSSL has a long history of producing vulnerabilities so much so that Google has created their own fork publicly available here: https://boringssl.googlesource.com/boringssl/ (used in chromium, chrome, and android).
-
OpenSSL added new C parser code [...] without doing any basic security testing
> Large web companies like Google implement their own encryption stack anyway.
Google uses BoringSSL[1], which is another OpenSSL fork. I believe AWS uses a mix of OpenSSL and Boring SSL (someone can correct me!).
So it's "their own encryption stack," but that stack is at least originally comprised of OpenSSL's code. They've probably done an admirable job of refactoring it, but API and ABI constraints still apply (it's very hard to change the massive body of existing code that assumes OpenSSL's APIs).
[1]: https://boringssl.googlesource.com/boringssl/
-
CVE-2022-3786 and CVE-2022-3602: X.509 Email Address Buffer Overflows
OpenSSL gets plenty of funding but we need to put more funding into TLS implementations that have a bigger focus on security and stability like boringssl, nss, go's tls, and rustls. It's 2022 and we have both languages better suited for this and tools to make existing languages safer and more robust, it's incredible to me that we aren't even more anxious over the current state of openssl.
-
BearSSL: A smaller SSL/TLS library
It was not built for chromium AFAIK
To quote: https://boringssl.googlesource.com/boringssl/
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
- OpenSSL Security Advisory for CVE-2022-0778
-
I think a major issue with the rust ecosystem is that it's full of unexpected design decisions
Use Google's fork of OpenSSL which exists because Google likes to do it's own weird things sometimes. This doesn't say anything about "OpenSSL is considered dangerous", it says "This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you."
- Information and learning resources for cryptography newcomers
-
OpenSSL Security Advisory (14 December 2021)
And this is why projects like https://boringssl.googlesource.com/boringssl/ exist
-
U.S. Telecoms Are Going to Start Physically Removing Huawei Gear
The immediate effect of Heartbleed was the OpenBSD folk [1] and Google [2] forking OpenSSL.
There's a talk from Bob Beck of OpenBSD on pruning OpenSSL, it's pretty hilarious [3].
In that case open source was at least able to react appropriately, even if it didn't act preemptively.
[1]: https://www.libressl.org
[2]: https://boringssl.googlesource.com/boringssl/
[3]: https://www.youtube.com/watch?v=GnBbhXBDmwU
-
Cloudflare: Warp for Linux and Proxy Mode
I doubt the reference to Musk's brand is intentional. It's more likely that it's a reference/homage to BoringSSL (https://github.com/google/boringssl) and "boring tech" in general that is purposefully designed to be minimalist, simple to use, and narrow in scope.
wgcf
-
Wireguard blocked but Cloudflare warp works
I can successfully create wg profiles using wgcf and connect to Cloudflare servers.
- Microsoft Edge users now have 5GB of free built-in VPN
-
Install Cloudflare Warp on Linux Mint 21.1 Vera
I normally don't install Cloudflare Warp client. I just generate WireGuard profile of Cloudflare Warp using wgcf and connect using WireGuard.
-
Vpn gratuita para P2P
Divirta-se: https://github.com/ViRb3/wgcf.
-
Cloudflare warp client in Fedora 37
I'm using https://github.com/ViRb3/wgcf and it works fine. I had to change the "Endpoint" line in the config file tho: Endpoint = 162.159.193.5:2408
-
Need Help with WireGuard HomeKit Access
I'm using Cloudflare's Zero Trust Tunnel with a WireGuard configuration obtained from "https://github.com/ViRb3/wgcf". This configuration includes my private key and DNS settings.
- How to set warp plus on modem/router?
-
Question about Cloudflare Tunnels and Sever Automation
All of my test and deploy scripts have to be encapsulated within docker containers or they’re not compatible. The thing is WARP seems to require some system resources that aren’t allowed from inside a containerwhen it sets up its network. I’ve also tried WCGF, which can run in containers but doesn’t have support for cloudflare Teams.
-
1.1.1.1 Refusing to connect.
If nothing works, generate a WireGuard config file with WGCF: https://github.com/ViRb3/wgcf
-
How to use 1.1.1.1 with truenas scale
Generate a wireguard profile for 1.1.1.1 WARP, then load that profile into your scale WireGuard UI
What are some alternatives?
OpenSSL - TLS/SSL and crypto library
warp-plus-cloudflare - Script for getting unlimited GB on Warp+ ( https://1.1.1.1/ ) [GET https://api.github.com/repos/ALIILAPRO/warp-plus-cloudflare: 403 - Repository access blocked]
wolfssl - The wolfSSL library is a small, fast, portable implementation of TLS/SSL for embedded devices to the cloud. wolfSSL supports up to TLS 1.3!
wg-portal - WireGuard Configuration Portal with LDAP connection
libsodium - A modern, portable, easy to use crypto library.
tunnel-wireguard-udp2tcp - Tunnel WireGuard UDP traffic over TCP using socat
Tink - Tink is a multi-language, cross-platform, open source library that provides cryptographic APIs that are secure, easy to use correctly, and hard(er) to misuse.
WARP-UNLIMITED-ADVANCED - Get unlimited amount of data in Cloudflare's WARP VPN🔥
webpki - WebPKI X.509 Certificate Validation in Rust
wireguard-windows - Download WireGuard for Windows at https://www.wireguard.com/install . This repo is a mirror only. Official repository is at https://git.zx2c4.com/wireguard-windows
istlsfastyet.com - Is TLS fast yet? Yes, yes it is.
go-cloudflare - Cloudflare utilities in Go