Posts by sittich

Done.
Reference link here.
Let's see how the responses are...

Alright, I admit defeat. You can choose an appropriate punishment for me.

Yes, it's quite unfortunate. I always view such responses as a missed opportunity to gain even more reach. This could potentially mean an additional 300,000 users who might have decided to use LibreELEC as a high-performance computing (HPC) solution, especially since the benefits section mentions that "importing server certificates has become even easier with drag and drop."

My concern is not about the simple renaming of a file, but rather the scenario in which users want to utilize more than just a single private certificate from various sources. I know what I would need to do —> merging and renaming. However, all these intermediate steps could be simplified for users who do not understand why they need to perform certain actions for their internet routers, to which their mass storage devices are connected, to work with their HPC. This is precisely the 300,000 users that could have been gained because it can be really simple. Drag and drop. Even a novice can manage that at this point.

How do the other developers see this?
And also the ordinary users, what do you think?

Quote from chewitt

That's the idea.

That works very well with this idea. Even in 2025 with the current versions of LibreELEC

But: Can you take it a step further? What if the user could simply drop in their own issued certificates without needing to change the names, so that the filenames can remain as boxcert.cer, owncert.pem, and mycert.cer, regardless of whether it is a *.cer or a *.pem file?
It should be made as simple as possible for the average user. This is already possible with web browsers and operating systems. Just drop in the certificate and it's done.

Not only that (proper power supply). Additionally, obtain contact spray and contactoil. I have frequently encountered issues with my Raspberry Pi crashing due to poor connections between plugs and sockets. This is often the case when the atmospheric humidity is high. The moisture slowly but steadily infiltrates the contact points over a period of months, causing corrosion, such as sulfide layers, which lead to increased contact resistance, resulting in voltage drops when high currents are drawn.

Spray the plug and/or socket with contact spray (using the long spray tube) and allow it to act according to the manufacturer's instructions. This will dissolve the solid corrosion. It may be necessary to follow up with a contact cleaner, as the contact spray itself leaves residues once it dries.
Finally, lightly mist the plug or socket with contactoil. This ensures that no moisture can seep in between. If too much is accidentally sprayed, excess can be absorbed with toilet paper.

This is my approach, including with connectors for DSL, HDMI connectors, particularly those that have not been used for an extended period, etc.
The use of contactoil at the end of the cleaning procedure is my secret tip!

Okay. Here are the test results for LE13 (alpha):

A query in the adjusted line curl -k --ftp-ssl --user myusername:mypassword ftp://ftpserver.mine:21 on the SSH console resulted in all elements (files and/or folders) being completely listed. Nothing is missing. Everything is present, even in the deeper directory structures. It seems that Kodi is the issue here.

Here is a log with component-specific libcURL debugging enabled, which, however, appears unremarkable. Alternatively, I may have made an error in it.

But back to the current LE12.0.2 with its original curl/8.6.0 version. I now believe I understand why FTPS does not work here. curl version 8.6.0 does not recognize the --ftp-ssl option, which is likely necessary to function with verifypeer=false. Here are two examples that I have tested:

_curl/8.6.0
LibreELEC:~ # curl -k --ftp-ssl --user myusername:mypassword ftp://ftpserver.mine:21
curl: option --ftp-ssl: is unknown
curl: try 'curl --help' for more information
LibreELEC:~ #

Meanwhile, curl version 8.5.0 responds as expected, also with the appropriate warning:
_{curl/8.5.0 (or curl/8.13.0 in LE13 alpha)}
LibreELEC:~ # curl -k --ftp-ssl --user myusername:mypassword ftp://ftpserver.mine:21
Warning: --ssl is an insecure option, consider --ssl-reqd instead
drwxrwxr-x 2 ftp ftp 560 Jan 01 01:02 Folders
-rwxrw-rw- 1 ftp ftp 418 Jan 01 01:01 Files.xyz
LibreELEC:~ #

For those who prefer to extract curl and libcurl themselves, here is the reference from where I obtained them:

Generic(-legacy).x86_64	LibreELEC-Generic.x86_64-12.0-nightly-20240129-40b8914.img.gz
RPi2/3	LibreELEC-RPi2.arm-12.0-nightly-20240201-76bf1fa.img.gz

These are the last versions that contain 8.5.0

After examining the various nightlies, I have found the best possible version for curl and its library that works with LibreELEC 12.0.2 (stable). This applies to both the Generic(-legacy).x86_64 platform, as I have conducted extensive testing with it, and for RPi2/3, as these are my media players. The versions are curl and libcurl 8.5.0. curl&libcurl-8.5.0_Generic(-legacy).x86_64__&__RPi2~3.zip
This version also works well with higher LibreELEC versions. However, it does not work with lower ones!

Note: The file libcurl.so.4.8.0 consists of libcurl/8.5.0. One refers to a versioning for the Application Binary Interface (ABI), while the other pertains to the Application Programming Interface (API). I cannot provide an explanation of the differences, as I am not a coder.

For me, this FTPS issue is quite new. It illustrates how long I have not used it, even though it has been set up in each of my LibreELEC installations for years. A downgrade to LibreELEC 11.0.6 is not an option for me, nor are the latest nightlies of v13, as in this case, FTPS incorrectly lists elements (folders/files).

Through a valuable tip from another post by vpeter on how to overlay files in the file system, I have found a provisional solution. I extracted the files curl and libcurl.so.4.8.0 from the LibreELEC 11.0.6 images (Gen eric.x86_64|RPi2.arm). The two required files are hidden within the archive in the SYSTEM file, located in the directory structures /usr/bin/curl and /usr/lib/libcurl.so.4.8.0. For Windows users, extracting works well with the PeaZip free archiver utility, as the SYSTEM file is also gz compressed.
Once the two files are available, it is time to copy them to your current LibreELEC installation. For this purpose, SSH must be enabled on LibreELEC.

---

_{Default access for ssh/sftp:}
ssh root@<LibreELEC-IP>
user: root
pass: libreelec

---

Via SFTP, the two required files are copied to the /storage/ directory. For Windows users, the tool WinSCP is recommended, but the display of hidden files must be enabled beforehand; otherwise, you will not be able to see the hidden .config directory. The file autostart.sh in /storage/.config/autostart.sh is added with the two commands listed below. Ensure that the file attributes for both files for fully functionallty are set back to rwxr-xr-x. Then reboot the media center, and FTPS should function again.

---

_autostart.sh
#!/bin/sh -e
# curl and libcurl.so.4.8.0 extracted from LibreELEC 11.0.6
mount -o bind /storage/libcurl.so.4.8.0 /usr/lib/libcurl.so.4.8.0
mount -o bind /storage/curl /usr/bin/curl
exit 0

---

_{This is approximately what the contents of the /storage/ directory look like:}

---

For those who do not want to experience any headaches or wish to avoid the entire process of extraction, I am offering these two files. This is of course a matter of trust. libcurl.so.4.8.0 and curl.zip

There is a comparison table that indicates which versions of curl, along with their libraries, are used in the different LibreELEC versions. It is evident that under LibreELEC 12.0.1, 12.0.2, and the current nightly-20250415-e25b5e0 (v12.x), ftps does not function.

LibreELEC Generic.x86_64 and RPi2.arm curl comparison table:


With the current LibreELEC nightly-20250424-067110d (v13.x), ftps is operational again; however, various elements (folders/files) are constantly being omitted. This renders it completely unusable!

Examples pictures for missing Elements (Folder or Files):




My questions are as follows:

- Why is the nightly version (v12.x) still unfixed? The included curl version has been outdated for a year.
- Why are the folders/files not fully listed in the nightly version (v13.x)?