-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
jasper: 2.0.14 -> 2.0.16 #57681
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jasper: 2.0.14 -> 2.0.16 #57681
Conversation
@GrahamcOfBorg build jasper |
@pSub, please consider adding yourself to the GrahamcOfBorg known users so your PRs can be built automatically. |
@ryantm suggested to myself to known users (NixOS/nixpkgs#57681 (comment)).
@ryantm Thank you for the hint. I've done so NixOS/ofborg#330. |
@pSub Thanks for looking into this.
Looking through the mentioned issues there seem to be a few more patches available and some that can be improved upon. (e.g. jasper-software/jasper#200, jasper-software/jasper#182, jasper-software/jasper#164). I think we can safely merge and backport this change already but should keep an eye out on further patches and releases |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, see my comment for some concerns / thoughts.
@andir Thanks for your feedback. I'll keep and eye on jasper and mark it as insecure if the list of open vulnerabilities stays that long for the longer term. |
I've cherry-picked the commit into staging-{18.09, 19.03}. |
Motivation for this change
Release 2.0.16 fixes CVE-2018-19539. Should be backported to 18.09 and 19.03
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)