wolfssl: 3.13.0 -> 3.15.0 #41656
Merged
wolfssl: 3.13.0 -> 3.15.0 #41656
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
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. These checks were done: - built on NixOS - 0 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 3.15.0 in filename of file in /nix/store/gx03mc7m4r07ybly7san7xk3v17pm264-wolfssl-3.15.0 - directory tree listing: https://gist.github.com/79fbf246bbacf1d8014bee57d274625a - du listing: https://gist.github.com/1f19919b71d52208a236a55cf066a003
|
Success on x86_64-darwin (full log) Attempted: wolfssl Partial log (click to expand)
|
|
Success on x86_64-linux (full log) Attempted: wolfssl Partial log (click to expand)
|
|
Success on aarch64-linux (full log) Attempted: wolfssl Partial log (click to expand)
|
|
Thanks for the update! For testing I recompiled curl against wolfssl using the following shell.nix: with import <nixpkgs> {};
let
curlwolfssl = (curl.override {
openssl = wolfssl;
}).overrideDerivation (oldAttrs: {
configureFlags =
(builtins.filter (x: x != "--with-ca-fallback") oldAttrs.configureFlags)
++ ["--with-cyassl=${wolfssl}"];
});
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.orgThe first line gives an error message "curl: (35) CyaSSL does not support SSLv2" confirming that CyaSSL - which is the old name for wolfssl still referred to by curl - is indeed used. |
|
Thanks for testing the update, @mcmtroffaes! Do you approve of these changes (are you happy for this to be merged in)? |
|
Thanks @ryantm ! |
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.
These checks were done:
built on NixOS
0 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 3.15.0 in filename of file in /nix/store/gx03mc7m4r07ybly7san7xk3v17pm264-wolfssl-3.15.0
directory tree listing: https://gist.github.com/79fbf246bbacf1d8014bee57d274625a
du listing: https://gist.github.com/1f19919b71d52208a236a55cf066a003
meta.description for wolfssl is: '"A small, fast, portable implementation of TLS/SSL for embedded devices"'.
cc @mcmtroffaes for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
Test this build: