veyon-configurator
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Logger: "/tmp/VeyonConfigurator.log" is a symlink and will not be written to for security reasons
2024-12-06T10:23:11.405: [ERR] CryptoCore: failed to decrypt password!
2024-12-06T10:23:11.416: [ERR] LinuxPlatformPlugin: Received signal 11
2024-12-06T10:23:11.417: [ERR] BACKTRACE:
/lib/x86_64-linux-gnu/libc.so.6(+0x3d1a0) [0x7ffb2de591a0]
/usr/bin/veyon-configurator(+0x1d945) [0x56319b741945]
/usr/bin/veyon-configurator(+0x22d70) [0x56319b746d70]
/usr/bin/veyon-configurator(+0x129a1) [0x56319b7369a1]
/lib/x86_64-linux-gnu/libc.so.6(+0x27b8a) [0x7ffb2de43b8a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7ffb2de43c45]
/usr/bin/veyon-configurator(+0x134b1) [0x56319b7374b1]
2024-12-06T10:23:11.417: [CRIT] Aborting due to severe error

Reviving this thread as this is the only one i can find on the matter, but i've been having this same issue, too.

At first, staff would log in to veyon Master with their own account, but i realised that students being monitored by Veyon were able to bypass the Student Web Filter on our Fortigate Firewall because the firewall saw the teachers logon session on the DC and it looks like the teacher has now logged on and is assigned the profile.

To bypass this, i have had to create a generic account for use with Veyon which is set as a student, so this retains the student webfilter, however i can see all the different entries from different devices on the firewall from this user.

@tobydox said in Students bypassing filtering:

the Veyon Server/Service on the client computers check the teacher's credentials by performing a temporary internal user logon with the teacher's username and password. However it does not initiate a real user sessions so I wonder why your firewall recognizes the teacher as being logged on

Are you able to expand on this ^^^? Because the veyon user logon event shows up in the DC's event logs (which are monitored by the firewall to assign user sessions) and there seems to be no difference in this logon to any other domain user logon. The workstations are only checked for logoff events, as these don't appear on the DC.

As far as the firewall is concerned, whenever a client computer is connected to, the logged on user has changed, as this is now the latest logon event seen on the DC for that device.

Hello,
Thanks a lot for your answer!! 🙂 I figured it out, I hadn't activated the User Groups with the LDAP Basic (this field was not there in the 4.8.3 Version).

I can't believe I've searched for that long without noticing there was another new field to activate the User Groups in the General menu! I can now set the control access according to LDAP groups. 🙂

Many thanks! 🤘

@vlouvlou Hello, just seen your post and I'd like to ask, How did you solve this?

I'm doing my first installation of Veyon in Ubuntu 22.04, followed these steps:
1.- Install Veyon in PC server, authentication with user / password so this will act as Master. Also installed NEtwork discovery addon to check for clients
2.- Install Veyon in PC client and start service with the GUI.

The network discovery plugin is not able to find any PC, but I don't understand the solution you aplied to solve it. Could you help me?

Thanks a lot!

You can go to top menu and choose view->advance
Then menu webapi will exists on bottom

I have no password in my windows session

Hello

you can use the veyon depot
sudo add-apt-repository ppa:veyon/stable
sudo apt update

sudo apt install -y veyon