2 ms·
libfaketime can be used for nefarious things such as using software past its trial stage (same with using serials attached to MAC addresses + mac spoofing) or r
by Fnoord 9y ago
libfaketime can be used for nefarious things such as using software past its trial stage (same with using serials attached to MAC addresses + mac spoofing) or returning future TOTP data. Its generally useful for QA as well. It could've been used by Apple to avoid the reset bug in iOS 11.1.2
fakechroot is used when you build your own *.deb file.
libeatmydata can be used in environments where you'd destroy the data afterwards anyway, or where you don't need logging or keep state after a reboot. You can also mount a bunch of filesystems such as /tmp and /var/log as tmpfs though.
- rrix2 9y agolibfaketime is also still crucial for reproduceable builds with a lot of compiers embedding compilation date, too, right?
- jwilk 9y agoAt least Debian folks didn't have to resort to using libfaketime. Instead, they patch the embedding tools to use timestamp from environment: https://reproducible-builds.org/specs/source-date-epoch/ https://reproducible-builds.org/specs/source-date-epoch/
- jwilk 9y ago> fakechroot is used when you build your own *.deb file. That's "fakeroot", a different program, which is used for simulating superuser privileges. I was going to mention fakeroot, too, but it doesn't seem have a useful homepage. https://fakeroot.alioth.debian.org/ https://fakeroot.alioth.debian.org/ looks very much uninviting. fakeroot was written for Debian, and it's still developed by Debian developers, although there's nothing Debian-specific about it. Debian has giving back to the free software community in their Social Contract¹, but in practice there's no culture of making Debian software easily accessible to outsiders. :-( ¹ https://www.debian.org/social_contract https://www.debian.org/social_contract §2