0 I want to install Veyon on the RPi4. I have read about Debian packages and the instructions. I had a look in my /etc/apt/sources.list and it had an entry for buster, so I added the line for Veyon Buster: deb http://ppa.launchpad.net/veyon/stable/ubuntu bionic main I then tried to run the command sudo add-apt-repository ppa:veyon/stable..
@tobydox Not technical enough! Does not the entire internet work through TCP/IP? That's like saying that you can listen to the radio, as long as your radio can pick up the electro magnetic waves.
Though I suppose the caveat "directly" offers some clues. I suppose you mean to suggest that the IP route is unobstructed, and not behind NAT or firewalls, right? Can you elaborate on the security risks or design paradigm a bit? Is all I have to do is forward the 11100 and 11400 ports?
Certain Veyon features can only be disabled globally in the configuration (https://docs.veyon.io/en/latest/admin/reference.html#features) so if student workers work on computers different from the lab management staff, you could deploy a modified Veyon configuration on these computers. Restricting functionalities to certain groups however is currently not possible.
Unfortunately ChromeOS support technically would be very difficult to implement and likely only possible by rewriting Veyon as a native Android app. Linux apps on ChromeOS are running in a sandbox so even if it's possible to start the process itself, it would be impossible for the Veyon Server to access the screen data.
Are you using key file or logon authentication? In case of logon authentication the bottleneck could be your AD server since it has to handle authentication requests from all Veyon clients at the same time (since each client checks the credentials of the teacher to authenticate the connection).
@erict: indeed the authentication key name check is too strict at the moment since it only allows word characters (0-9, a-z, A-Z and underscore). I just committed a fix which will also allow the minus character (https://github.com/veyon/veyon/commit/768feeb53c11d7a1f5e5fa4d8378d795c73cc1ad). It will be part of Veyon 4.5.7 next month. In case you build packages on your own, you can simply do this for the latest 4.5 branch.
Besides that, importing keys via veyon-cli should work with the following command: