关于有效期的设置和周期性检查

[machetelol]

您好，

我在使用限制有效期功能时可能理解错了指令的含义，导致有效期并不会自动检查，请教问题出在哪里：

• 我有一个定时任务，每天5点进行输出传输，启动任务的命令为python start.py，此外代码中有一个关键脚本foo.py

pyarmor gen -e 2024-08-09 --period 1s -b b0:4f:a6:9f:f4:69 --enable-bcc foo.py
pyarmor gen -e 2024-08-09 --period 1s -b b0:4f:a6:9f:f4:69 --enable-bcc start.py

• 分别对两个脚本加密，并从dist中将生成的文件移动到代码目录下，由于runtime目录同名，我更改了foo.py对应的runtime目录名和代码中的import
• 启动任务后，当天日志如下：

{'time': '2024-08-09 05:00:10', 'level': 'INFO', 'message': '数据检查完成.'}
{'time': '2024-08-09 05:05:56', 'level': 'INFO', 'message': '数据处理完成.'}

• 并没有提示许可证过期，如果ctrl+c中断脚本，此时能看到许可证过期的提示
• 之所以要对两个脚本分别加密，原因是之前尝试过对整个目录加密，一样也不会提示许可证过期

pyarmor gen -O data_transfer_enc -e 2024-08-08 --period 1s -b b0:4f:a6:9f:f4:69 --enable-bcc -r data_transfer/

[jondy]

只有当调用加密函数或者导入加密模块的时候才会重新检查许可证，如果函数循环体内部不调用任何加密函数，就会出现这种情况

尝试在循环内部调用一个外部空函数，这个函数使用 exclude 规则不要转化成为 bcc，这样应该可以

[jondy]

这种情况下面，可以在循环体内增加一个调用空的函数，例如:

     def pyarmor_check_license():
         pass

     def main():
         while True:
             check_pyarmor_license()
             sleep(0.01)

如果使用了 BCC 模式加密，还需要使用下面的额外配置不要转换这个函数，例如:

      $ pyarmor cfg bcc:excludes = pyarmor_check_license

e

[machetelol]

您好，按指导做了测试，昨天没有想到可以通过更改linux服务器时间加快测试效率，所以回复比较迟

• 首先设置不要转换pyarmor_check_license

(py310) [hit@localhost data_transfer]$ pyarmor cfg bcc:excludes = pyarmor_check_license
INFO     Python 3.10.13
INFO     Pyarmor 8.5.11 (pro), 005863,####
INFO     Platform linux.aarch64
INFO     change option "excludes" to new value "pyarmor_check_license"

------------------------------------------------------------
Section: bcc

Current settings
no option "excludes"

Global settings

Local settings
  excludes = pyarmor_check_license

• 第二步：整个目录加密：

 pyarmor gen -O data_transfer_enc -e 2024-08-11 --period 1s -b b0:4f:a6:9f:f4:69 --enable-bcc -r data_transfer/

INFO     Python 3.10.13
INFO     Pyarmor 8.5.11 (pro), 005863, ####
INFO     Platform linux.aarch64
INFO     search inputs ...
INFO     find package at data_transfer
INFO     find 1 top resources
INFO     start to generate runtime files
INFO     target platforms {'linux.aarch64'}
INFO     write data_transfer_enc/pyarmor_runtime_005863/pyarmor_runtime.so
INFO     generate runtime files OK
INFO     start to obfuscate scripts
INFO     process resource "data_transfer"
INFO     obfuscating file npy2csv.py
INFO     start to generate bcc code ...
/usr/bin/ld: warning: .pyarmor/bcc/data_transfer.npy2csv.c.o has a LOAD segment with RWX permissions
INFO     generate bcc code successfully
INFO     write data_transfer_enc/data_transfer/npy2csv.py
INFO     obfuscating file start.py
INFO     start to generate bcc code ...
/usr/bin/ld: warning: .pyarmor/bcc/data_transfer.start.c.o has a LOAD segment with RWX permissions
INFO     generate bcc code successfully
INFO     write data_transfer_enc/data_transfer/start.py
INFO     obfuscating file check.py
INFO     start to generate bcc code ...
/usr/bin/ld: warning: .pyarmor/bcc/data_transfer.utils.check.c.o has a LOAD segment with RWX permissions
INFO     generate bcc code successfully
INFO     write data_transfer_enc/data_transfer/utils/check.py
INFO     obfuscating file log.py
INFO     start to generate bcc code ...
/usr/bin/ld: warning: .pyarmor/bcc/data_transfer.utils.log.c.o has a LOAD segment with RWX permissions
INFO     generate bcc code successfully
INFO     write data_transfer_enc/data_transfer/utils/log.py
INFO     obfuscating file __init__.py
INFO     start to generate bcc code ...
INFO     no bcc code generated
INFO     write data_transfer_enc/data_transfer/utils/__init__.py
INFO     obfuscating file utils.py
INFO     start to generate bcc code ...
/usr/bin/ld: warning: .pyarmor/bcc/data_transfer.utils.utils.c.o has a LOAD segment with RWX permissions
INFO     generate bcc code successfully
INFO     write data_transfer_enc/data_transfer/utils/utils.py
INFO     obfuscate scripts OK

• 第三步：进入data_transfer_enc 并将pyarmor_runtime_005863移进该目录下的data_transfer内
• 第四步：执行代码，代码中实际运行的脚本已经提前替换如下：

def pyarmor_check_license():
    pass


if __name__ == '__main__':
    while True:
        logger.info('test')
        pyarmor_check_license()
        time.sleep(1)
        logger.info('test_done')

• 然后，实际脚本输出如下：

...
'time': '2024-08-10 23:59:57', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test_done'}
{'time': '2024-08-10 23:59:57', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test'}
{'time': '2024-08-10 23:59:58', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test_done'}
{'time': '2024-08-10 23:59:58', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test'}
{'time': '2024-08-10 23:59:59', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test_done'}
{'time': '2024-08-10 23:59:59', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test'}
{'time': '2024-08-11 00:00:00', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test_done'}
{'time': '2024-08-11 00:00:00', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test'}
{'time': '2024-08-11 00:00:01', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test_done'}
{'time': '2024-08-11 00:00:01', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test'}
{'time': '2024-08-11 00:00:02', 'level': 'INFO', 'production': 'power_forecast', 'message': 'test_done'}
...
^CTraceback (most recent call last):
  File "<frozen data_transfer.start>", line 249, in <module>
KeyboardInterrupt

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<frozen __main__>", line 3, in <module>
  File "<frozen data_transfer.start>", line 245, in <module>
RuntimeError: 脚本许可证已经过期 (1:11086)

看起来还是有哪里搞错了

[jondy]

我的测试是没有问题的，

脚本如下 foo.py

import time

def pyarmor_check_license():
    pass


if __name__ == '__main__':
    i = 1
    while True:
        print('test', i)
        i += 1
        pyarmor_check_license()
        time.sleep(1)
        print('test_done')

加密之后运行

pyarmor cfg bcc:excludes = pyarmor_check_license
pyarmor gen --enable-bcc --period 1s -e 2024-08-12 foo.py
python3.9 dist/foo.py

然后修改系统时间为 2024-08-15，直接抛出异常

...
test 45
auto recheck
auto recheck
Traceback (most recent call last):
  File "<frozen a>", line 15, in <module>
  File "<frozen a>", line 7, in pyarmor_check_license
RuntimeError: this license key is expired (1:11087)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<frozen __main__>", line 3, in <module>
  File "<frozen a>", line 10, in <module>
RuntimeError: this license key is expired (1:11087)

[machetelol]

感谢，我测试了确实没问题

检查可以发现问题出在这一步：

第三步：进入data_transfer_enc 并将pyarmor_runtime_005863移进该目录下的data_transfer内

对runtime目录的移动操作是引起报错的原因，教程中并没有提到可以这么操作，我之前认为这样做代码可以运行就理应有效期功能起作用