Rivoreo Source Code Repositories
src.rivoreo.one / systemd-stable / v239-45
commitfcd9a141d08d521c01dc1a1c06a8d43a2337a392[log] [download]
authorLennart Poettering <lennart@poettering.net>Mon Feb 04 10:23:43 2019 +0100
committerThe Plumber <50238977+systemd-rhel-bot@users.noreply.github.com>Wed Mar 10 16:05:57 2021 +0100
treecf979ca7c432fb4dfb76aa09ff29092280748d10
parent1f3165bda13c8572c8c31d23c998835c4e2ad8f3 [diff]
pam-systemd: use secure_getenv() rather than getenv()

And explain why in a comment.

(cherry picked from commit 83d4ab55336ff8a0643c6aa627b31e351a24040a)

CVE-2019-3842

Resolves: #1687514
1 file changed
tree: cf979ca7c432fb4dfb76aa09ff29092280748d10
  1. .dir-locals.el
  2. .editorconfig
  3. .gitattributes
  4. .github/
  5. .gitignore
  6. .lgtm.yml
  7. .lgtm/cpp-queries/
  8. .mailmap
  9. .mkosi/
  10. .vimrc
  11. .ycm_extra_conf.py
  12. LICENSE.GPL2
  13. LICENSE.LGPL2.1
  14. Makefile
  15. NEWS
  16. README
  17. README.md
  18. TODO
  19. catalog/
  20. coccinelle/
  21. configure
  22. doc/
  23. factory/etc/
  24. hwdb/
  25. man/
  26. meson.build
  27. meson_options.txt
  28. mkosi.build
  29. mkosi.default ⇨ .mkosi/mkosi.fedora
  30. modprobe.d/
  31. network/
  32. po/
  33. presets/
  34. rules/
  35. shell-completion/
  36. src/
  37. sysctl.d/
  38. sysusers.d/
  39. test/
  40. tmpfiles.d/
  41. tools/
  42. travis-ci/
  43. units/
  44. xorg/
  45. zanata.xml
README.md

systemd - System and Service Manager

Build Status
Coverity Scan Status
CII Best Practices
Build Status

Details

General information about systemd can be found in the systemd Wiki.

Information about build requirements are provided in the README file.

Consult our NEWS file for information about what's new in the most recent systemd versions.

Please see the HACKING file for information how to hack on systemd and test your modifications.

Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.

When preparing patches for systemd, please follow our Coding Style Guidelines.

If you are looking for support, please contact our mailing list or join our IRC channel.

Stable branches with backported patches are available in the stable repo.