MichaIng

@bradleythughes Okay that is really helpful information. Didn't know that WebRTC encrypts by default, although it makes totally sense since in case of P2P connections there is no TURN server...

@misi I am no c coder, however not hard to understand the code. I am currently very busy on own project but will see if I can have a look...

Just as a side note regarding Nextcloud Talk: - It does not use TURNS (TURN TLS) at all currently, which is also the reason why disabling plain access breaks it:...

The Bullseye `raspimjpeg` binary requires a rebuild against latest `libraspberrypi0` as it does not contain shared libraries named like `libmmal_core.so` anymore but named `libmmal_core.so.0`. Because of this, the binary fails...

It is strange, as at that date the package should be with the new library names already. However, do the following to replicate: ``` cd /tmp curl -sSfLO 'https://github.com/silvanmelchior/RPi_Cam_Web_Interface/raw/master/bin/raspimjpeg' ldd...

They are compatible, it's really only the names. Creating symlinks for all those without `.0` pointing to the ones with `.0` works around the issue. On Buster, the userland/package contains...

Ah okay, that explains it, I guess 🙂. However, those are not content of and not created via `libraspberrypi0` package maintainer script, so would be good to have a build...

> I checked the lib folder and the libraries were there with the links. I just checked the Raspberry Pi OS Bullseye image, and you are right the links are...

FYI: https://github.com/raspberrypi/userland/issues/715 When the symlinks are added to the package, all is fine, as the `.0` suffixes are as well specific to the package while the upstream blobs do not...

@roberttidey Maybe the presence of the symlinks is not an issue: https://github.com/raspberrypi/userland/issues/715#issuecomment-981665724 But actually that contradicts the fact that the current binaries are indeed linked against paths without the `.0`...