Libfaketime

Latest version: v2.1.0

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 7

0.8.2

- Added support for "limited faking".
You can optionally specify when libfaketime starts to fake the
returned timestamps and when it shall stop doing so. For example,
a program can be started regularly, and after 5 minutes run-time
it will be sent two years into the future. Those limiting
start and stop times can be specified in seconds or as the
number of any time-related function calls within the program.
- Added a feature to spawn an external process after x seconds
or y time-related system calls. This can, for example, be used
to execute an arbitrary shell script x seconds after a program
has been started.

0.8.1

- Added a MacOS port.
Thanks to Daria Phoebe Brashear!
- Added a functional test framework that aids in automatically
determining whether libfaketime works properly on the current
machine. Thanks to Don Fong!

0.8

- Changed directory layout and Makefile structure.
Thanks to Lukas Fleischer!

0.7

- Added support for fstatat() and fstatat64() which were introduced in
Linux kernel 2.6.16 and used in recent coreutils.
Thanks to Daniel Kahn Gillmor for the report!
This can be disabled by passing -DNO_ATFILE in the Makefile.
- Added a simple wrapper shell script and a man page for it. Makes it
easier to run commands under faked system times. It assumes that the
libraries will be copied to /usr/lib/faketime during installation,
please adjust this path if necessary. The "install" target in the
Makefile has been adapted accordingly.
- Added support for fractional time offsets, such as FAKETIME="+1,5h".
Please note that either , or . has to be used as a delimiter
depending on your locale. Thanks to Karl Chen!
- Added support for speeding the clock up or slowing it down. For
example, FAKETIME="+5d x2,0" will set the faked time 5 days into
the future and make the clock run twice as fast for the specified
program. Slowing it down can be done e.g. by using FAKETIME="+0 x0,5".
Again, the delimiter to use for the fraction depends on your locale.
Thanks to Karl Chen!

0.6

Main version 0.7 contributions by David North, TDI:
- Added ability to 'start clock at' a specific time.
- Added pthread synchronization support
- Added a 2 second delay to timetest.c so one can observe if the
clock is relative or absolute
- Added test.sh example of 'start clock at'
- Added ability to disable the FAKE_STAT functionality at library-start
in the case that the library was compiled -DFAKE_STAT, and added another
test case for demonstrating this
- Repaired a bug w.r.t. strptime/mktime wherein 'isdst' was uninitialized
which led to pseudorandom +/- 1 hour results being returned in 'start at'
or absolute time modes

Other enhancements:
- Fixed missing interceptions to libc-internal functions and added notes
about a workaround for running Java programs with faked times in the
future (they worked properly, but often locked up at exiting). Thanks to
Jamie Cameron of Google for in-depth analysis and prototype solution!

0.5.2

-----
released 2018-05-19

- fix a bug causing incorrect times after unpatching under python 3.6+: [43](https://github.com/simon-weber/python-libfaketime/pull/43)
- fix compilation under gcc8: [44](https://github.com/simon-weber/python-libfaketime/pull/44)

Page 3 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.