How to compile:
For normal PC desktop/server Linux - just unpack and run make
For routers - target toolchain/build environment/SDK would be required, depends on specific firmware.
GCC and Glibc or derived/compatible libc probably required. I've tested with Glibc and uClibc.
How it works:
EPids are read from config file on every request. Config file path can be configured at compile time via Makefile (INI_FILE variable) or at run-time by -i <path/to/file> command-line option.
Config file format:
INI-like, <product guid> = <epid>, one per line. Example:
http://rghost.ru/50063440
(ñ) http://forums.mydigitallife.info/thr...l=1#post837970
Ï.Ñ. Èñõîäíèêè áóäóò æèòü íà õîñòå ìåñÿö, òàê ÷òî åñëè êîãî çàèíòåðåñóåò, ïåðåçàëåéòå íà áîëåå äîëãîæèâóùèé )
For normal PC desktop/server Linux - just unpack and run make
For routers - target toolchain/build environment/SDK would be required, depends on specific firmware.
GCC and Glibc or derived/compatible libc probably required. I've tested with Glibc and uClibc.
How it works:
EPids are read from config file on every request. Config file path can be configured at compile time via Makefile (INI_FILE variable) or at run-time by -i <path/to/file> command-line option.
Config file format:
INI-like, <product guid> = <epid>, one per line. Example:
Code:
55c92734-d682-4d71-983e-d6ec3f16059f = 05426-00168-152-564055-03-1049-9200.0000-0912013
59a52881-a989-479d-af46-f275c6370663 = 55041-00096-200-026043-03-1049-7601.0000-0162013
0ff1ce15-a989-479d-af46-f275c6370663 = 55041-00096-200-625305-03-1049-7601.0000-0572013(ñ) http://forums.mydigitallife.info/thr...l=1#post837970
Ï.Ñ. Èñõîäíèêè áóäóò æèòü íà õîñòå ìåñÿö, òàê ÷òî åñëè êîãî çàèíòåðåñóåò, ïåðåçàëåéòå íà áîëåå äîëãîæèâóùèé )