03-05-2025, 04:15 PM
(03-05-2025, 01:56 PM)the_bertrum Wrote: There were Linux instructions in my linked doc, but they dealt with a pem rather than a cer, other than that, they matched what you detailed Kent, so all good there.
A handy command for verifying it worked:
Code:awk -v cmd='openssl x509 -noout -subject' '/BEGIN/{close(cmd)};{print | cmd}' < /etc/ssl/certs/ca-certificates.crt | grep <whatever the cert was called>
1. Since moOde downloads a .cer file, that's what I went with.
2. Good verification script. I just trusted update-ca-certificates to do what it's supposed to

Quote:As for the Android phone issue, I have this recorded in my document:
Firefox Android
Not sure if that is relevant in this case though since it seems to be not just (or even) Firefox in your case. I'm flashing a vanilla image with no "legacy" certificate baggage to try it out again on my Pixel 6.
- Open the Firefox browser on your phone, and from the three dot menu, choose "about".
- Tap the firefox logo five times to enable the "debug menu", then tap the back arrow and scroll down the "secret settings".
- In there you will find a toggle for "trust third party CAs" which you should enable.
Yeah, the fancy finger-tapping had been done. Did I mention this problem occurs in both Firefox and Chrome on my phone? I may have to run a remote debugger to figure out how the browsers are trying to reach the player.
As Roseann Rosannadanna would say, "it's always something!"
Regards,
Kent