aboutsummaryrefslogtreecommitdiff
path: root/debian/arctica-greeter-guest-session.install
diff options
context:
space:
mode:
authorMike Gabriel <mike.gabriel@das-netzwerkteam.de>2019-03-17 17:25:37 +0100
committerMike Gabriel <mike.gabriel@das-netzwerkteam.de>2019-03-17 17:25:46 +0100
commit7aab2968b93387463d4d5d0aabf9c29a76c994b8 (patch)
treee7566a3f1d45cbd6b2ba3c3a52bb93adfd954681 /debian/arctica-greeter-guest-session.install
parent2a0938048e52ff36157cee6e334ed3ec13c94e90 (diff)
downloadarctica-greeter-7aab2968b93387463d4d5d0aabf9c29a76c994b8.tar.gz
arctica-greeter-7aab2968b93387463d4d5d0aabf9c29a76c994b8.tar.bz2
arctica-greeter-7aab2968b93387463d4d5d0aabf9c29a76c994b8.zip
Remove mlockall.
Protect memory from being paged to disk, as we deal with passwords According to systemd-dev, "mlockall() is generally a bad idea and certainly has no place in a graphical program. A program like this uses lots of memory and it is crucial that this memory can be paged out to relieve memory pressure." With systemd version 239 the ulimit for RLIMIT_MEMLOCK was set to 16 MiB and therefore the mlockall call would fail. This is lucky becasue the subsequent mmap would not fail. With systemd version 240 the RLIMIT_MEMLOCK is now set to 64 MiB and now the mlockall no longer fails. However, it not possible to mmap in all the memory and because that would still exceed the MEMLOCK limit. " See https://bugzilla.redhat.com/show_bug.cgi?id=1662857 & https://github.com/CanonicalLtd/lightdm/issues/55 RLIMIT_MEMLOCK = 64 MiB means, arctica-greeter will most likely fail with 64 bit and will always fail on 32 bit systems. Hence we better disable it. Ported from Unity Greeter / Slick Greeter. https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1815493 https://github.com/linuxmint/slick-greeter/pull/127
Diffstat (limited to 'debian/arctica-greeter-guest-session.install')
0 files changed, 0 insertions, 0 deletions