Description of problem: Well, Here in Mageia we have a very good tool for kids users of Mageia. Parental controls of Mageia Control Center is a good tool for control the kids users about applications that they can use and network access, and webs access. But this tool don't work fine. I have created a new user and I have configured Parental Controls for the user has a limit access to some applications and webs. The option "Block all network traffic" don't work and the user can navigate from all webs of internet from Firefox that is the predeterminate browser on Mageia 9 Plasma. Version-Release number of selected component (if applicable): Parental Controls of Mageia Control Center How reproducible: Configurar Parental controls and click on "Block all network access" The user can navigate for all webs with Firefox.
Confirming the issue, using drakguard-1.8-2.mga9 and blocking everything with it doesn't work. *If* that was caused by not rebooting (I didn't), then it would be nice to make drakguard inform the user that a reboot is needed. The versions/releases of the other needed packages in cauldron were: perl-Convert-ASN1-0.340.0-1.mga10.noarch.rpm squid-5.9-1.mga9.x86_64.rpm lib64ecap3-1.0.1-5.mga9.x86_64.rpm e2guardian-5.5.2r-1.mga9.x86_64.rpm perl-Crypt-OpenSSL-X509-1.915.0-1.mga10.x86_64.rpm /etc/e2guardian/e2guardian.conf and /etc/squid/squid.conf were both rewritten when changing the setting in drakguard, but I did not manage to find anything in them that could match the "block all network traffic" setting. Assigning to the Mageia tools maintainers.
Source RPM: Mageia Control Center => drakguard-1.8-2.mga9Summary: Parental controls not working correctly => Parental controls "Block all network traffic" option does not workAssignee: bugsquad => mageiatoolsCC: (none) => marja11
Hello, For what I see in the code, the option should affect the file /etc/e2guardian/lists/bannedsitelist and affect line(s) with ** inside The option is also kept in /etc/e2guardian/e2guardianf1.conf
CC: (none) => yvesbrungard
Does the manually edition of /etc/e2guardian/lists/bannedsitelist work, adding: ** on one line in said file?
I have configured the Bannedsitelist file with the two ** as commented on comment 3, but the user with parental control continues to access all the Internet sites. I do not know if then you have to put room on the blacklist. But this would be a very tedious and complicated task. If anyone can confirm if Edguardian does some type of automatic filter?
I have also tried to include the user in the Edguardian group and does not work either.
For what I remember, the problem is that CT acts as a proxy, but the browser is not configured to use the proxy, thus rules of the CT does not affects the navigation.
Flags: (none) => affects_mga9+
(In reply to papoteur from comment #6) > For what I remember, the problem is that CT acts as a proxy, but the browser > is not configured to use the proxy, thus rules of the CT does not affects > the navigation. The browsers follow system configure, so if all the network pass by the proxy should work, but not sure how that works by other users that need freedom in navigation in same system
Hello, I confirm this issue is also present in mageia 10 beta 1. I installed a fresh VM with network installer and choose a plasma installation. In addition of the first user who has the admin rights, I added a second standard user. I activated the parental control from MCC and allow only my first user to bypass the protection. The only thing that is working is when I choose to block an application. The network protection is not working at all. I tried with Firefox and Konqueror, in black list and white list mode, with I level of sensitivity. But I can browse what I want in each case. I also tried the parental controle provided by plasma, but without more success. Firefox is configured to follow the system proxy configuration by default, but Konqueror is configured by default to "No proxy". Source rpm: drakguard-1.9-1.mga10.src.rpm
CC: (none) => mageia
Hello Yann, Yes, there is still problems: - drakguard has not yet any mechanism for dealing https traffic. For that, there is a need for a local certificate to allow squid to be a "man in the middle" - since e2guardian 5, the manner to specify the rules has changed, but drakguard does not take this into account. There is a lot of work to do to have a working tool.
Well, if the tool doesn't work correctly, wouldn't it be better to hide it from users? In my opinion, it is better to have a tool in development, hidden from the user since it does not work correctly, than for the user to try to use it and it does not work, and that generates a bad opinion about the entire distro... which usually happens.
commit 48b1124959f657654b44dfd270bee43ac2dfca94 Author: Papoteur <papoteur@...> Date: Tue May 12 09:09:12 2026 +0200 Suspend the entry for drakguard, broken for the moment (mga#32473) --- Commit Link: https://gitweb.mageia.org/software/control-center/commit/?id=48b1124959f657654b44dfd270bee43ac2dfca94
Is there other broken tools to remove?
Severity: normal => critical
Draksnapshot reported in bug https://bugs.mageia.org/show_bug.cgi?id=32192 But I think we should try to fix this application for the release of mageia 10. It is a very good application for snapshots of the entire system and I don't understand why it hasn't been fixed before (unfortunately I don't have the knowledge to do it). Currently, a snapshot tool is almost essential in any operating system and the truth is that Draksnapshot works very well if the date or periodicity of the system snapshots could be planned.
(In reply to Jose Manuel López from comment #13) > Draksnapshot reported in bug https://bugs.mageia.org/show_bug.cgi?id=32192 Please no, no more time to fix it, let's concentrate to getting mga10 out, we can fix it after with an update if someone would work on it.
CC: (none) => geiger.david68210