{"action":"opened","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/4850","repository_url":"https://api.github.com/repos/systemd/systemd","labels_url":"https://api.github.com/repos/systemd/systemd/issues/4850/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/4850/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/4850/events","html_url":"https://github.com/systemd/systemd/issues/4850","id":194247982,"number":4850,"title":"systemd hardcodes SYS_UID_MAX instead of parsing /etc/login.defs at runtime","user":{"login":"nmiell","id":2183893,"avatar_url":"https://avatars.githubusercontent.com/u/2183893?v=3","gravatar_id":"","url":"https://api.github.com/users/nmiell","html_url":"https://github.com/nmiell","followers_url":"https://api.github.com/users/nmiell/followers","following_url":"https://api.github.com/users/nmiell/following{/other_user}","gists_url":"https://api.github.com/users/nmiell/gists{/gist_id}","starred_url":"https://api.github.com/users/nmiell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nmiell/subscriptions","organizations_url":"https://api.github.com/users/nmiell/orgs","repos_url":"https://api.github.com/users/nmiell/repos","events_url":"https://api.github.com/users/nmiell/events{/privacy}","received_events_url":"https://api.github.com/users/nmiell/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-08T05:04:00Z","updated_at":"2016-12-08T05:04:00Z","closed_at":null,"body":"### Submission type\r\n  - [x] Bug report\r\n\r\n### systemd version the issue has been seen with\r\n> 231\r\n\r\n### Used distribution\r\n> Fedora 25\r\n\r\n### Unexpected behaviour you saw\r\n> systemd parses the build machine's copy of /etc/login.defs for SYS_UID_MAX at compile time and uses the extracted hard-coded value instead of parsing /etc/login.defs on the install machine at runtime.\r\n\r\n> This prevents coredumpctl from allowing users to see their own core dumps because journald doesn't log core dumps (or anything else) in a journal file that the user is allowed to read. \r\n\r\n### In case of bug report: Steps to reproduce the problem\r\n> Crash something as an unprivileged user with a UID less than the value of SYS_UID_MAX that was extracted from /etc/login.defs on the build machine.\r\n"}}
{"actor":{"display_login":"nmiell"}}