How long do I need to keep registering new devices due to hardware ID changes?

[Nakyoung]

I have been using PyArmor sometimes for the past 2-3 years.
My environment is Ubuntu, and it's not a virtual environment.

Since I use it infrequently, I'm not sure exactly what causes this situation, but recently I had to register my device again under the group license in less than about 2 weeks.
Could using a VPN or conda envirnment or upgrading the Ubuntu version be the reason for the device ID changes?

I understand that the group license supports up to 100 devices, and I am currently using 4, so I'm not worried for the time being. However, I'm wondering why this keeps happening. Also, I'm curious about what happens if I end up using all 100 device slots.

Additionally, while searching for issues, it seems that attaching hdinfo is often necessary for diagnosing the cause, so I have added it below:

 (pyarmor)  ~/playground/pyarmor  python -m pyarmor.cli.hdinfo
Machine ID: 'm458cf41634226d6c1900b89af71ace0c'
Default Harddisk Serial Number: Permission denied
Default Mac address: '00:d8:61:bc:7c:17'
Default IPv4 address: '192.168.31.21'
Multiple Mac addresses: <7a:f7:81:52:f3:8b,02:42:d9:b9:8a:d0,00:d8:61:bc:7c:17,52:54:00:b2:c6:96,02:42:ba:f9:9f:c3,02:42:38:04:ee:88,76:7b:a4:65:cb:65,aa:0b:14:f7:a4:62,02:42:6d:75:2d:7c>
Domain: '(none)'
 (pyarmor)  ~/playground/pyarmor  ls /sys/class/net
br-232952f7269b  docker0  lxdbr0  veth1ee806e  veth5870cf4  veth8a6d9d2  vethcab83d3  vethed77554
br-4283221510f7  enp34s0  lxdbr1  veth31abe14  veth5938a97  veth999e9a5  vethdd45e2c  virbr0
br-c1e232a8c42e  lo       lxdbr2  veth33d60df  veth7b9a107  vethb194ec7  vethe862640  wg0

[jondy]

First upgrade Pyarmor to latest version, or at least Pyarmor 9.0+
Second, login ubuntu with same user. root user may get serial number of harddisk, other users may not, it results in different machine id.
For physical machine with latest Pyarmor, machine id should be same. But if using pyarmor in docker container which in the physical machine, the machine id is changed every run.
If there is still problem, please report issue.

[Nakyoung]

I tried to use pyarmor again today, and the device ID has changed again. now I have to generate another group ID to use pyarmor again.
The version was 9.1.5 when I inquired last time as well.
And I have always executed pyarmor commands as a regular user and also, pyarmor is always run on a physical machine, not in a Docker container or a virtual machine.

I previously checked if the machine ID changes after a reboot, but it did not change.
Moreover, it hasn't even been rebooted in the last two weeks.

(pyarmor) $ pyarmor --version
Pyarmor 9.1.5 (group), 000000, xxxxxx

License Type    : pyarmor-group
License No.     : pyarmor-vax-000000
License To      : XXXXXX
License Product : xxxxxx

BCC Mode        : Yes
RFT Mode        : Yes
CI/CD Mode      : No

Notes
* Offline obfuscation
723.4

INFO     this license is for machine: m458cf41634226d6c1900b89af71ace0c
INFO     but this machine id: m0e8d72f01a38298223d3a936b5c71f3f
ERROR    this group license is not for this machine

(pyarmor) $ last
nykim    :1           :1               Wed May 14 17:09   still logged in
nykim    seat0        login screen     Wed May 14 17:09   still logged in
reboot   system boot  6.8.0-1023-gke   Wed May 14 17:08   still running

I attached two hdds to this system for preparing some data lastweek and now they are removed.
Could adding hdds to the system or using a conda environment be the reason why the device ID keeps changing?

[jondy]

Adding hadds will make device ID changed.

[jondy]

And adding new network card also make machine id changed.

[Nakyoung]

I have to repeatedly attach and detach disks for my job.
What would you recommend in this scenario?

[jondy]

I really did not take this into accouts. The temporary solutions is to prepare 2 registration device files for it.

[hodogowsky]

@jondy I have a problem. I have to obfuscate the script every time in the Docker container to keep the Python version consistent. It registers every time. I have the PyArmor Pro version. Can I encounter any trouble with the license working this way?

[jondy]

Use Pro License in CI/CD pipeline or docker container will be problem, each run will be taken as one new machine.
Please check
https://eke.dashingsoft.com/pyarmor/ask/
to get more information about using different licenses.

[hodogowsky]

I am learning this software. At the moment I was getting python version mismatches. Now I will experiment with changing GCC version within Windows WSL. Then I will not have to do it inside the docker. czw., 5 cze 2025, 13:23 użytkownik Jondy ***@***.***> napisał:

…

Use Pro License in CI/CD pipeline or docker container will be problem, each run will be taken as one new machine. Please check https://eke.dashingsoft.com/pyarmor/ask/ to get more information about using different licenses. — Reply to this email directly, view it on GitHub <#2144 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4VUI2LBZNA2QCMGUVUPRAL3CASCNAVCNFSM6AAAAAB5C4D4FWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZXHA3DCMY> . You are receiving this because you commented.Message ID: ***@***.***>