https://github.com/endlessm/eos-payg
Daemon component of the pay-as-you-go financing option
https://github.com/endlessm/eos-payg
Last synced: 8 months ago
JSON representation
Daemon component of the pay-as-you-go financing option
- Host: GitHub
- URL: https://github.com/endlessm/eos-payg
- Owner: endlessm
- Created: 2018-03-16T16:31:46.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2025-01-09T19:33:39.000Z (over 1 year ago)
- Last Synced: 2025-03-26T15:42:52.723Z (about 1 year ago)
- Language: C
- Size: 1.35 MB
- Stars: 6
- Watchers: 20
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: COPYING.LGPL-2.1+
Awesome Lists containing this project
README
eos-payg
========
eos-payg implements pay-as-you-go support for EOS, providing a way to verify
top-up codes and monitor the amount of time the computer has remaining before
the user next needs to top up its lease.
It provides a daemon to monitor the expiry time for the current code and to
verify new codes, a command line utility for generating new codes, and various
helper libraries. It also supports loading out-of-tree plugins, which implement
alternative code management backends.
All the library APIs are currently unstable and are likely to change wildly.
**NOTE**: eos-paygd has two modes it can run in: (1) when run from the
initramfs, it uses Phase 4+ PAYG security features, and assumes that it's
running from a payg image, and (2) when run from the primary root filesystem,
it does not use the advanced security features and assumes it's running on a
Phase 2 PAYG system or a non-PAYG system.
When running from the initramfs, eos-paygd is unkillable. systemd will leave
it running during the root pivot and shutdown. The reason this is safe, and
that a system shutdown while it's writing to non-volatile storage isn't
considered a risk is that all the non-volatile storage backends in use are
robust against a shutdown during write. This is done either through the
ability to rollback an interrupted write, or writes that are fully atomic.
Since it would be very difficult to enter a timecode at the same time as
a system shutdown (because the UI would not be accessible during shutdown),
the most likely interrupted operation would be time expiry. On the following
boot the time would still be past expiration time, and the system would lock
again.
Dependencies
============
* glib-2.0
* gobject-2.0
* gio-2.0
* peas
* (lib)systemd
* dracut
Licensing
=========
With a couple of exceptions, all code in this project is dual-licensed under
MPL-2.0 and LGPL-2.1+. See debian/copyright and COPYING.* for more details.
Bugs
====
Bug reports and patches should be filed in GitHub.
Contact
=======
https://github.com/endlessm/eos-payg