wolfssl: 4.1.0 -> 4.2.0 #72705
Merged
wolfssl: 4.1.0 -> 4.2.0 #72705
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Upstream changelog and https://www.wolfssl.com/docs/security-vulnerabilities/ indicates this fixes 5 vulnerabilities. This probably needs to be backported to r19.09. |
c0bw3b
added
1.severity: security
9.needs: port to stable
|
Thanks for the update! No package currently depends on wolfssl, so for testing I recompiled curl against wolfssl using the following shell.nix: with import <nixpkgs> {};
let
curlwolfssl = (curl.override {
openssl = wolfssl;
}).overrideDerivation (oldAttrs: {
configureFlags =
# --with-ca-fallback does not work with wolfssl
(builtins.filter (x: x != "--with-ca-fallback") oldAttrs.configureFlags)
++ ["--with-wolfssl=${wolfssl}" "--without-ssl"];
});
in
{
my-env = stdenv.mkDerivation {
name = "my-env";
buildInputs = [
curlwolfssl
];
};
}I tested the resulting curl binary and compared its output against my local curl binary provided by Fedora: curl -2 https://nixos.org
curl --cacert /etc/ssl/certs/ca-bundle.crt https://nixos.org > 1.txt
/usr/bin/curl https://nixos.org > 2.txt
diff 1.txt 2.txtThe first line gives an error message "curl: (35) wolfSSL does not support SSLv2" confirming that wolfssl is indeed used. Diff of output of local curl and this new curl shows identical outputs as expected. |
c0bw3b
added
the
8.has: port to stable
|
Backported in fdac1c5 |
c0bw3b
removed
the
9.needs: port to stable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/wolfssl/versions.
meta.description for wolfssl is: '"A small, fast, portable implementation of TLS/SSL for embedded devices"'.
meta.homepage for wolfssl is: '"https://www.wolfssl.com/"
Release on GitHub
Compare changes on GitHub
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 4.2.0 in filename of file in /nix/store/gajfdg4x7wc3blnzyrl1r35hv9m44m8i-wolfssl-4.2.0
directory tree listing: https://gist.github.com/3545a59f8c1a737005e5a4098ae1b4bf
du listing: https://gist.github.com/77ec7db48fc0901b8fb989bd4cfeb6ff
Rebuild report (if merged into master) (click to expand)
4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
wolfssl
Instructions to test this update (click to expand)
Either download from Cachix:
(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Experimental: CVE security report (click to expand)
CVEs resolved by this update:
CVEs introduced by this update:
none
CVEs present in both versions:
none
cc @mcmtroffaes for testing.