Issues with wget, errors being generated

I just installed Fedora iot, and I am seeing some strange messaging whenever I attempt to use wget:

wget https://code.jquery.com/jquery-3.6.0.min.js

                          [Files: 0  Bytes: 0  [0 B/s] Redirects: 0  Todo: 1  Errors: 0                                                ]
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpmrm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tcm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
WARNING:tcti:src/util-io/io.c:262:socket_connect() Failed to connect to host 127.0.0.1, port 2321: errno 111: Connection refused 
ERROR:tcti:src/tss2-tcti/tcti-swtpm.c:617:Tss2_Tcti_Swtpm_Init() Cannot connect to swtpm TPM socket 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-swtpm.so.0 
WARNING:tcti:src/util-io/io.c:262:socket_connect() Failed to connect to host 127.0.0.1, port 2321: errno 111: Connection refused 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-mssim.so.0 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:263:tctildr_get_default() No standard TCTI could be loaded 
ERROR:tcti:src/tss2-tcti/tctildr.c:477:tctildr_init_context_data() Failed to instantiate TCTI 
ERROR:fapi:src/tss2-fapi/api/Fapi_Initialize.c:233:Fapi_Initialize_Finish() Initializing TCTI. ErrorCode (0x000a000a) 
WARNING: Listing FAPI token objects failed: "tcti:IO failure"
Please see https://github.com/tpm2-software/tpm2-pkcs11/blob/1.9.0/docs/FAPI.md for more details
WARNING: FAPI backend was not initialized.
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpmrm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
ERROR:tcti:src/tss2-tcti/tcti-device.c:455:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tcm0: No such file or directory 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-device.so.0 
WARNING:tcti:src/util-io/io.c:262:socket_connect() Failed to connect to host 127.0.0.1, port 2321: errno 111: Connection refused 
ERROR:tcti:src/tss2-tcti/tcti-swtpm.c:617:Tss2_Tcti_Swtpm_Init() Cannot connect to swtpm TPM socket 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-swtpm.so.0 
WARNING:tcti:src/util-io/io.c:262:socket_connect() Failed to connect to host 127.0.0.1, port 2321: errno 111: Connection refused 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:149:tcti_from_file() Could not initialize TCTI file: libtss2-tcti-mssim.so.0 
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:263:tctildr_get_default() No standard TCTI could be loaded 
jquery-3.6.0.min.js  100% [===========================================================================================================>]   30.15K    --.-KB/s
ERROR: Could not initializ[Files: 1  Bytes: 30.15K [189.63KB/s] Redirects: 0  Todo: 0  Errors: 0                                       ]

The file appears to download just fine, and I did have tpm enabled in the BIOS, but have since disabled it.

Why would wget need your TPM?

Added tpm, wget

Good question… I find it confusing myself. I haven’t made any changes to this system beyond installing a few additional packages (wget was one of them).

A web search told me The TCTI or "Transmission Interface" is the communication mechanism with the TPM.

I think the TPM errors are nothing to do with wget.

Try running wget and redirect its stdout and stderr into a file.
Are the TCPI errors in the wget output or coming from somewhere else?

Check for BIOS/EFI firmware updates from your device manufacturer.

The relationship probably looks like this: Wget > HTTPS > Crypto/RNG > TPM

2 Likes

ahh good point about the https part… that would make sense and I didn’t consider it honestly. Ill see if there’s a BIOS update.

1 Like

Like others have said, these errors don’t seem to be coming from wget. I can’t find any reference to using TPM2 in the wget source, though maybe it is using a library that is trying to use it?

I’m more interested in what is trying to connect to port 2321 on your host.

Could you share the output of rpm-ostree status, ss -tulpn and maybe a paste of journalctl -b?

Minor update to this, I did update my machine to the latest BIOS firmware, and it appears to have helped some, but I’m still seeing additional messaging:

wget https://code.jquery.com/jquery-3.6.0.min.js

                          [Files: 0  Bytes: 0  [0 B/s] Redirects: 0  Todo: 1  Errors: 0                                                ]
WARNING:fapi:src/tss2-fapi/api/Fapi_List.c:228:Fapi_List_Finish() Profile of path not provisioned: /HS/SRK 
ERROR:fapi:src/tss2-fapi/api/Fapi_List.c:81:Fapi_List() ErrorCode (0x00060034) Entities_List 
WARNING: Listing FAPI token objects failed: "fapi:Provisioning was not executed."
jquery-3.6.0.min.js  100% [===========================================================================================================>]   30.15K    1.44MB/s
WARNING: Getting tokens fr[Files: 1  Bytes: 30.15K [115.08KB/s] Redirects: 0  Todo: 0  Errors: 0                                       ]

I don’t know if this is a Fedora specific bug, firmware or both, but very perplexing nonetheless.