как ломануть 1C 8.3 for Linux

[Sailas]

Добрый день. Появилась идея сделать резервную машину с дампами ключей, которые будут пробрасываться на сервера с 1с. Но идея наткнулась на суровую реальность. Процесс установки по инструкции ув. localhost2005 прошел корректно, устройства видны.
Вывод lsusb

Bus 003 Device 005: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 003 Device 004: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 003 Device 003: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 003 Device 002: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Проблема как у tormozok

не подскажете, где задается максимальное количество ключей, которое можно раздать. По дефолту только 4

Испробовано на нескольких версиях Debian и Ubuntu, на различных ядрах. Все безрезультатно. Например, текущая машина, с ограничением в 4 устройства

uname -a

Linux hasp-test 5.10.0-15-amd64 #1 SMP Debian 5.10.120-1 (2022-06-09) x86_64 GNU/Linux

uname -r

5.10.0-15-amd64

Кто-нибудь реализовывал подобную схему с использованием более четырех дампов? Есть какие-нибудь идеи? Спасибо

[localhost2005]

TEST HASP 1C v8.3!

lsusb | grep Aladdin
Bus 007 Device 004: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 007 Device 003: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 007 Device 002: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 006 Device 004: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 006 Device 003: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 006 Device 002: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 005 Device 004: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 005 Device 003: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 005 Device 002: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 004 Device 004: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 004 Device 003: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 004 Device 002: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle

systemctl status hasplm

hasplm.service - Sentinel LM
Loaded: loaded (/lib/systemd/system/hasplm.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2022-06-28 15:53:59 MSK; 1h 33min ago
Process: 336 ExecStart=/usr/bin/hasplm -c /etc/hasplm/hasplm.conf (code=exited, status=0/SUCCESS)
Main PID: 345 (hasplm)
Tasks: 1 (limit: 1149)
Memory: 2.1M
CGroup: /system.slice/hasplm.service
345 /usr/bin/hasplm -c /etc/hasplm/hasplm.conf

июн 28 15:53:59 haspkey systemd[1]: Starting Sentinel LM...
июн 28 15:53:59 haspkey hasplm[345]: HASP LM v8.30 loaded
июн 28 15:53:59 haspkey systemd[1]: Started Sentinel LM.

systemctl status haspd

haspd.service - LSB: Hasp keys support
Loaded: loaded (/etc/init.d/haspd; generated)
Active: active (running) since Tue 2022-06-28 16:48:50 MSK; 38min ago
Docs: man:systemd-sysv-generator(8)
Process: 1430 ExecStart=/etc/init.d/haspd start (code=exited, status=0/SUCCESS)
Tasks: 10 (limit: 1149)
Memory: 13.9M
CGroup: /system.slice/haspd.service
1435 aksusbd
1446 hasplmd -s

июн 28 16:48:50 haspkey systemd[1]: Starting LSB: Hasp keys support...
июн 28 16:48:50 haspkey aksusbd[1435]: loaded, daemon version: 8.23.1.119312, key API (USB) version: 3.88 (parallel driver not available)
июн 28 16:48:50 haspkey haspd[1430]: Running aksusbd... [ DONE ]
июн 28 16:48:50 haspkey hasplmd[1446]: HASP LM v25.2.1.119312 loaded
июн 28 16:48:50 haspkey haspd[1430]: Running hasplmd... [ DONE ]
июн 28 16:48:50 haspkey systemd[1]: Started LSB: Hasp keys support.

Делаем раз, два и так далее...
usbhaspd /root/usbhaspd-001.conf
usbhaspd /root/usbhaspd-002.conf
usbhaspd /root/usbhaspd-003.conf
usbhaspd /root/usbhaspd-004.conf

[Sailas]

Вывод основных команд

sailas@hasp-test01:~$ lsusb | grep Aladdin
Bus 003 Device 005: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 003 Device 004: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 003 Device 003: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
Bus 003 Device 002: ID 0529:0001 Aladdin Knowledge Systems HASP copy protection dongle
sailas@hasp-test01:~$ systemctl status hasplm
● hasplm.service - Sentinel LM
   Loaded: loaded (/lib/systemd/system/hasplm.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2022-06-29 07:11:40 UTC; 2min 6s ago
  Process: 809 ExecStart=/usr/bin/hasplm -c /etc/hasplm/hasplm.conf (code=exited, status=0/SUCCESS)
 Main PID: 889 (hasplm)
    Tasks: 1 (limit: 2283)
   CGroup: /system.slice/hasplm.service
           └─889 /usr/bin/hasplm -c /etc/hasplm/hasplm.conf

Jun 29 07:11:40 hasp-test01 systemd[1]: Starting Sentinel LM...
Jun 29 07:11:40 hasp-test01 systemd[1]: Started Sentinel LM.
Jun 29 07:11:40 hasp-test01 hasplm[889]: HASP LM v8.30 loaded
sailas@hasp-test01:~$ systemctl status haspd
● haspd.service - LSB: Hasp keys support
   Loaded: loaded (/etc/init.d/haspd; generated)
   Active: active (running) since Wed 2022-06-29 07:11:42 UTC; 2min 27s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 777 ExecStart=/etc/init.d/haspd start (code=exited, status=0/SUCCESS)
    Tasks: 10 (limit: 2283)
   CGroup: /system.slice/haspd.service
           ├─890 aksusbd
           └─954 hasplmd -s
sailas@hasp-test01:~$ systemctl status usbhaspd.service
● usbhaspd.service - Usbhasp daemon
   Loaded: loaded (/lib/systemd/system/usbhaspd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2022-06-29 14:25:54 UTC; 25min ago
 Main PID: 895 (usbhaspd)
    Tasks: 2 (limit: 2283)
   CGroup: /system.slice/usbhaspd.service
           ├─895 /bin/bash /usr/bin/usbhaspd
           └─960 /usr/bin/usbhasp /etc/usbhaspd/keys/app03clients.json /etc/usbhaspd/keys/app03server.json /etc/usbhaspd/keys/app04clients.json /etc/usbhaspd/keys/app04server /etc/usbhaspd/keys/app05clients.json /etc/usbhaspd/keys/app05server.json /etc/usbhaspd/keys/app06clients.json /etc/usbhaspd/keys/app06server.json

Jun 29 14:25:56 hasp1991 usbhaspd[895]: usbhasp[960]: Set device on port 2 address = 3
Jun 29 14:25:56 hasp1991 usbhasp[960]: Set device on port 2 address = 3
Jun 29 14:25:56 hasp1991 usbhaspd[895]: usbhasp[960]: Port 3 is disabled.
Jun 29 14:25:56 hasp1991 usbhasp[960]: Port 3 is disabled.
Jun 29 14:25:56 hasp1991 usbhaspd[895]: usbhasp[960]: Set device on port 3 address = 4
Jun 29 14:25:56 hasp1991 usbhasp[960]: Set device on port 3 address = 4
Jun 29 14:25:57 hasp1991 usbhaspd[895]: usbhasp[960]: Port 4 is disabled.
Jun 29 14:25:57 hasp1991 usbhasp[960]: Port 4 is disabled.
Jun 29 14:25:57 hasp1991 usbhaspd[895]: usbhasp[960]: Set device on port 4 address = 5
Jun 29 14:25:57 hasp1991 usbhasp[960]: Set device on port 4 address = 5

Jun 29 07:11:40 hasp-test01 systemd[1]: Starting LSB: Hasp keys support...
Jun 29 07:11:40 hasp-test01 aksusbd[890]: loaded, daemon version: 8.23.1.119312, key API (USB) version: 3.88 (parallel driver not available)
Jun 29 07:11:40 hasp-test01 haspd[777]: Running aksusbd... [ DONE ]
Jun 29 07:11:41 hasp-test01 haspd[777]: Running hasplmd... [ DONE ]
Jun 29 07:11:41 hasp-test01 hasplmd[954]: HASP LM v25.2.1.119312 loaded
Jun 29 07:11:42 hasp-test01 systemd[1]: Started LSB: Hasp keys support.

Вывод при запуске usbhaspd

usbhasp[1863]: Loaded key 0: '1С:Предприятие 8.3 КОРП. Клиентская лицензия на 500 рабочих мест (USB)', Created: 12/05/2022 10:00
usbhasp[1863]: Loaded key 1: '1С:Предприятие 8.3 КОРП. Лицензия на сервер (x86-64)(USB)', Created: 12/05/2022 10:00
usbhasp[1863]: Loaded key 2: '1С:Предприятие 8.3 КОРП. Клиентская лицензия на 500 рабочих мест (USB)', Created: 12/05/2022 10:00
usbhasp[1863]: Loaded key 3: '1С:Предприятие 8.3 КОРП. Лицензия на сервер (x86-64)(USB)', Created: 12/05/2022 10:00
usbhasp[1863]: USB device created usb_vhci_hcd.1 (bus# 4)
usbhasp[1863]: Port 1 is powered on -> connecting device.
usbhasp[1863]: Port 1 connected.
usbhasp[1863]: Port 2 is powered on -> connecting device.
usbhasp[1863]: Port 2 connected.
usbhasp[1863]: Port 3 is powered on -> connecting device.
usbhasp[1863]: Port 3 connected.
usbhasp[1863]: Port 4 is powered on -> connecting device.
usbhasp[1863]: Port 4 connected.
usbhasp[1863]: Port 1 is disabled.
usbhasp[1863]: Set device on port 1 address = 2
usbhasp[1863]: Port 2 is disabled.
usbhasp[1863]: Set device on port 2 address = 3
usbhasp[1863]: Port 3 is disabled.
usbhasp[1863]: Set device on port 3 address = 4
usbhasp[1863]: Port 4 is disabled.
usbhasp[1863]: Set device on port 4 address = 5

Меня смущает вывод ls /sys/devices/platform/ | grep vh
как будто я не могу создать больше контроллеров

usb_vhci_hcd.0

Но больше всего смущает вывод nano /usr/bin/usbhaspd
Из того, что можно разобрать

USB (usb_vhci_fetch_work) failed: %s.
Port %d is powered on -> connecting device. USB (usb_vhci_port_connect), port %d failed: %s.
USB (usb_vhci_port_reset_done) port %d failed: %s.
USB (usb_vhci_port_resumed), port %d failed: %s.
USB (usb_vhci_fetch_data) port %d failed: %s.
Set device on port %d address = %d
USB (usb_vhci_giveback), port %d failed: %s.
Got invalid work for port, type %d
Wrong port number %hhu
Port %d is powered off.
Port %d connected.
Port %d is suspended.
Port %d is disabled.
Wrong device address %hhu
Received signal to stop.
?hd^@usbhasp^@Error %s loading keyfile %s.
Error parsing key file %s
Can't catch SIGINT
Unable to setsid.
Usage: #%s [-d] keyfile1.json ... keyfile%d.json
Loaded key %d: '%s', Created: %s
Unable to create USB device. Is vhci_hcd driver loaded?
USB device created %s (bus# %d)
Unable to fork off parent process.
Unable to fork for the second time.
USB device removed %s (bus# %d)
No keys loaded. Nothing to emulate.

Извиняюсь за стену текста, но устал бороться с проблемой. Самое обидное, что один раз все собралось и работало на vm без ограничений и лишнего шаманства, но машина благополучно похерена в истории