nitrokey:arch:start

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
nitrokey:arch:start [16.12.2024 20:26. ] – [erster Test] djangonitrokey:arch:start [16.12.2024 20:35. ] (aktuell) – [erster Test] django
Zeile 152: Zeile 152:
 Authentication key: [none] Authentication key: [none]
 General key info..: [none]</code> General key info..: [none]</code>
- 
- 
- 
-   # pacman -S python-pynitrokey 
- 
- 
-   # nitropy --help 
-<code>Usage: nitropy [OPTIONS] COMMAND [ARGS]... 
- 
-Options: 
-  -h, --help  Show this message and exit. 
- 
-Commands: 
-  fido2    Interact with Nitrokey FIDO2 devices, see subcommands. 
-  list     List Nitrokey devices (in firmware or bootloader mode) 
-  nethsm   Interact with NetHSM devices, see subcommands. 
-  nk3      Interact with Nitrokey 3 devices, see subcommands. 
-  nkpk     Interact with Nitrokey Passkey devices, see subcommands. 
-  pro      Interact with Nitrokey Pro devices, see subcommands. 
-  start    Interact with Nitrokey Start devices, see subcommands. 
-  storage  Interact with Nitrokey Storage devices, see subcommands. 
-  version  Version of pynitrokey library and tool.</code> 
- 
-   # nitropy nk3 test 
-<code>Command line tool to interact with Nitrokey devices 0.6.0 
-THIS COMMAND SHOULD NOT BE RUN AS ROOT! 
- 
-Please install udev rules and run `nitropy` as regular user (without sudo). 
-We suggest using: https://raw.githubusercontent.com/Nitrokey/libnitrokey/master/data/41-nitrokey.rules 
-For more information, see: https://docs.nitrokey.com/software/nitropy/linux/udev.html 
- 
-Set ALLOW_ROOT=1 environment variable to disable this warning. 
- 
-Found 1 NK3 device(s): 
-- Nitrokey 3 at /dev/hidraw0 
- 
-Running tests for Nitrokey 3 at /dev/hidraw0 
- 
-[1/5] uuid      UUID query              SUCCESS  6447F2534D3A582D0000000000000000 
-[2/5] version  Firmware version query  SUCCESS  v1.7.2 
-[3/5] status    Device status            SUCCESS  Status(init_status=<InitStatus: 0>, ifs_blocks=241, efs_blocks=471, variant=<Variant.NRF52: 2>) 
-Running SE050 test: |                                                                                                                                                                                  
-[4/5] se050    SE050                    SUCCESS  SE050 firmware version: 3.1.1 - 1.11, (persistent: (30140,), transient_deselect: (271,), transient_reset: (256,)) 
-Please press the touch button on the device ... 
-Please press the touch button on the device ... 
-[5/5] fido2    FIDO2                    SUCCESS   
- 
-5 tests, 5 successful, 0 skipped, 0 failed 
- 
-Summary: 1 device(s) tested, 1 successful, 0 failed</code> 
- 
-Das Protokoll im Verzeichnis **''/tmp''** von **''nitropy''** zeigt im Zweifelsfall weitere Informationen die bei der weiteren Betrachtung oder Fehlereingrenzung wertvolle Informationen liefern kann. 
- 
-   # ls -al /tmp/nitropy.log.gkod8a3k  
-<code>-rw-r--r-- 1 root root 5795 Dec 16 21:16 /tmp/nitropy.log.gkod8a3k</code> 
- 
-   # cat /tmp/nitropy.log.gkod8a3k 
-<code>368        INFO pynitrokey.cli Timestamp: 2024-12-16 21:16:27.120247 
-368        INFO pynitrokey.cli OS: uname_result(system='Linux', node='pml010074', release='6.6.65-1-lts', version='#1 SMP PREEMPT_DYNAMIC Wed, 11 Dec 2024 15:35:54 +0000', machine='x86_64') 
-368        INFO pynitrokey.cli Python version: 3.12.7 
-369        INFO pynitrokey.cli Cli arguments: ['nk3', 'test'] 
-372        INFO pynitrokey.cli pynitrokey version: 0.6.0 
-373        INFO pynitrokey.cli cryptography version: 43.0.3 
-374        INFO pynitrokey.cli ecdsa version: 0.19.0 
-374        INFO pynitrokey.cli fido2 version: 1.1.3 
-375        INFO pynitrokey.cli pyusb version: 1.2.1 
-376        INFO pynitrokey.cli.trussed.test platform: Linux-6.6.65-1-lts-x86_64-with-glibc2.40 
-376        INFO pynitrokey.cli.trussed.test uname: uname_result(system='Linux', node='pml010074', release='6.6.65-1-lts', version='#1 SMP PREEMPT_DYNAMIC Wed, 11 Dec 2024 15:35:54 +0000', machine='x86_64') 
-512       DEBUG       root print: Found 1 NK3 device(s): 
-512       DEBUG       root print: - Nitrokey 3 at /dev/hidraw0 
-512       DEBUG       root print: Running tests for Nitrokey 3 at /dev/hidraw0 
-520       DEBUG       root print: [1/5] uuid      UUID query              SUCCESS  6447F2534D3A582D0000000000000000 
-528       DEBUG       root print: [2/5] version  Firmware version query  SUCCESS  v1.7.2 
-536        INFO pynitrokey.cli.trussed.tests Device status: Status(init_status=<InitStatus: 0>, ifs_blocks=241, efs_blocks=471, variant=<Variant.NRF52: 2>) 
-536       DEBUG       root print: [3/5] status    Device status            SUCCESS  Status(init_status=<InitStatus: 0>, ifs_blocks=241, efs_blocks=471, variant=<Variant.NRF52: 2>) 
-669       DEBUG       root print: [4/5] se050    SE050                    SUCCESS  SE050 firmware version: 3.1.1 - 1.11, (persistent: (30140,), transient_deselect: (271,), transient_reset: (256,)) 
-1782      DEBUG fido2.server Fido2Server initialized for RP: PublicKeyCredentialRpEntity(name='Example RP', id='example.com') 
-1782      DEBUG fido2.server Starting new registration, existing credentials:  
-1786      DEBUG       root print: Please press the touch button on the device ... 
-1796      DEBUG fido2.client Register a new credential for RP ID: example.com 
-1838      DEBUG fido2.ctap2.base Calling CTAP2 make_credential 
-1996      DEBUG  fido2.hid Got keepalive status: 01 
-2248      DEBUG  fido2.hid Got keepalive status: 01 
-2496      DEBUG  fido2.hid Got keepalive status: 01 
-2748      DEBUG  fido2.hid Got keepalive status: 01 
-2996      DEBUG  fido2.hid Got keepalive status: 01 
-3248      DEBUG  fido2.hid Got keepalive status: 01 
-3496      DEBUG  fido2.hid Got keepalive status: 01 
-3744      DEBUG  fido2.hid Got keepalive status: 01 
-3996      DEBUG  fido2.hid Got keepalive status: 01 
-4244      DEBUG  fido2.hid Got keepalive status: 02 
-4496      DEBUG  fido2.hid Got keepalive status: 01 
-4744      DEBUG  fido2.hid Got keepalive status: 01 
-4996      DEBUG  fido2.hid Got keepalive status: 01 
-5244      DEBUG  fido2.hid Got keepalive status: 01 
-5492      DEBUG  fido2.hid Got keepalive status: 01 
-5744      DEBUG  fido2.hid Got keepalive status: 01 
-5992      DEBUG  fido2.hid Got keepalive status: 01 
-6244      DEBUG  fido2.hid Got keepalive status: 01 
-6492      DEBUG  fido2.hid Got keepalive status: 01 
-6740      DEBUG  fido2.hid Got keepalive status: 01 
-6992      DEBUG  fido2.hid Got keepalive status: 01 
-7240      DEBUG  fido2.hid Got keepalive status: 01 
-7492      DEBUG  fido2.hid Got keepalive status: 01 
-7740      DEBUG  fido2.hid Got keepalive status: 01 
-7992      DEBUG  fido2.hid Got keepalive status: 01 
-8256      DEBUG  fido2.hid Got keepalive status: 01 
-8512      DEBUG  fido2.hid Got keepalive status: 01 
-8796      DEBUG  fido2.hid Got keepalive status: 01 
-9056      DEBUG  fido2.hid Got keepalive status: 01 
-9199      DEBUG fido2.server Verifying attestation of type packed 
-9200       INFO fido2.server New credential registered: a3005878bd496f7f5e7c10b12264abdc7274b8a2a8a1724eab6a6b2cf29737921dfb1c4793c1b3645547b7287ca5cd6087b3cd0c06e03c9115de4aeba206f2cfc14da879c4cf8c2045165008c9b3aa4591cee5b2cb825ee6c86f4ebe2f6bc8c4769902a550d389e11b235485931334234f15bf64de04d075aa27d394014c680a5adb95a30d02ed6d9e7f02505d85c63ba65a973e074ce94856cbb2a0 
-9201      DEBUG fido2.server Starting new authentication, for credentials: a3005878bd496f7f5e7c10b12264abdc7274b8a2a8a1724eab6a6b2cf29737921dfb1c4793c1b3645547b7287ca5cd6087b3cd0c06e03c9115de4aeba206f2cfc14da879c4cf8c2045165008c9b3aa4591cee5b2cb825ee6c86f4ebe2f6bc8c4769902a550d389e11b235485931334234f15bf64de04d075aa27d394014c680a5adb95a30d02ed6d9e7f02505d85c63ba65a973e074ce94856cbb2a0 
-9202      DEBUG       root print: Please press the touch button on the device ... 
-9206      DEBUG fido2.client Assert a credential for RP ID: example.com 
-9237      DEBUG fido2.ctap2.base Calling CTAP2 get_assertion 
-9304      DEBUG  fido2.hid Got keepalive status: 02 
-9552      DEBUG  fido2.hid Got keepalive status: 01 
-9804      DEBUG  fido2.hid Got keepalive status: 01 
-10052     DEBUG  fido2.hid Got keepalive status: 01 
-10328     DEBUG  fido2.hid Got keepalive status: 01 
-10588     DEBUG  fido2.hid Got keepalive status: 01 
-10755      INFO fido2.server Credential authenticated: a3005878bd496f7f5e7c10b12264abdc7274b8a2a8a1724eab6a6b2cf29737921dfb1c4793c1b3645547b7287ca5cd6087b3cd0c06e03c9115de4aeba206f2cfc14da879c4cf8c2045165008c9b3aa4591cee5b2cb825ee6c86f4ebe2f6bc8c4769902a550d389e11b235485931334234f15bf64de04d075aa27d394014c680a5adb95a30d02ed6d9e7f02505d85c63ba65a973e074ce94856cbb2a0 
-10755     DEBUG       root print: [5/5] fido2    FIDO2                    SUCCESS 
-10756     DEBUG       root print: 5 tests, 5 successful, 0 skipped, 0 failed 
-10756     DEBUG       root print: Summary: 1 device(s) tested, 1 successful, 0 failed<code> 
-Im Falle von Fehlern entnehmen Sie bitte die Protokolle dem Verzeichnis /tmp (/tmp/nitropy.log.*). 
- 
  
 ===== Anwendungsfälle - Software ===== ===== Anwendungsfälle - Software =====
  • nitrokey/arch/start.1734380787.txt.gz
  • Zuletzt geändert: 16.12.2024 20:26.
  • von django