Skip to content
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

[20.09] limesurvey: mark as insecure #111291

Merged
merged 1 commit into from Jan 30, 2021

Conversation

dotlambda
Copy link
Member

(cherry picked from commit a03847e)

Motivation for this change

fixes #102802

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

(cherry picked from commit a03847e)
@dotlambda dotlambda mentioned this pull request Jan 30, 2021
10 tasks
@SuperSandro2000 SuperSandro2000 merged commit 9e96456 into NixOS:release-20.09 Jan 30, 2021
@dotlambda dotlambda deleted the limesurvey-insecure branch January 30, 2021 15:44
@fernsehmuell
Copy link
Contributor

Hello everyone,
the two issues were fixed in version 3.24.4 and 3.25.0 see https://github.com/LimeSurvey/LimeSurvey/blob/3.x-LTS/docs/release_notes.txt

The latest version is https://github.com/LimeSurvey/LimeSurvey/releases/tag/3.25.17+210309

@dotlambda
Copy link
Member Author

As discussed in #111218, limesurvery needs a new maintainer that upgrades it to the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants