Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Because it's a mil system and yes, we need to severely restrict users from doing anything except run/operate the software that they're allowed to. We shouldn't even allow a right-click menu but we gave up trying to find a way to do that on Rhel8/ We can't use kiosk mode for too many reasons to get into here. We did figure out that we can protect the terminal with a username/password prompt, otherwise the terminal just closes. Cyber said they can live with that.
Just as I thought.
I'm not trying to be snarky or anything, just help you with your actual problem, which has nothing to do with context menus per se, just some of the things it typically allows (all of which can usually also be achieved some other way).
If your users are only allowed to operate a specific set of software (commands), you have to make everything else unavailable for the user. There are several ways to achieve that; look into "kiosk" systems, that would be "linux kiosk" or even "rhel kiosk".
Elaborate, show us what you got, we can help more.
What's a "mil system"?
Quote:
Originally Posted by yelirt5
Because it's a mil system and yes, we need to severely restrict users from doing anything except run/operate the software that they're allowed to. We shouldn't even allow a right-click menu but we gave up trying to find a way to do that on Rhel8/ We can't use kiosk mode for too many reasons to get into here. We did figure out that we can protect the terminal with a username/password prompt, otherwise the terminal just closes. Cyber said they can live with that.
edit: I see that you brought this up earlier. You should've added some context to your OP; I can see most of your questions are lacking it. Anyhow, assuming this already is a changed OS I wonder what changes you implemented and why exactly they aren't sufficient.
a military system. There are just quite a few cyber security requirements - STIG, app whitelisting, firewall, SELinux, etc. The software we run is really not a big deal. But we need to lock the system down as much as possible in order to keep the user (military personnel) from playing around and changing something that would cause the need for a system reload. They're not trained to do it so a team gets dispatched to them and that gets expensive.
I'll look into kiosk mode. But I thought you were restricted to just running one app in kiosk mode? Our software is actually multiple applications running at once, mostly java apps.
I can only re-iterate that whatever you access from the context menu can also be accomplished some other way, so you need to think about that - the what, not the how.
If you want to share these requirements - and what you did so far to accomplish them - we might be able to help you.
I will certainly share what I'm able to do but so far we haven't.
So when you right-click on our RHEL8 desktop a menu comes up with only two choices - Terminal and Help Center. We figured out how to prompt for a username and a password for the terminal, which our cyber folks are ok with that (as opposed to removing the option for terminal altogether). Now I'm just trying to figure out a way to remove Help Center as an option from that menu.
We figured out how to remove everything else from the desktop. There's no Activities button or anything so I'm not sure the users could get to something we've removed by another way. But even if they did, say through the terminal, they don't have root acccess.
That still doesn't tell us the What I requested but I concede that you don't have a choice in this matter, basically somebody else told you to "Remove the Help Center from the context menu"?
Which brings us back to post #2, assuming you use GNOME because that's RHEL's default DE.
I am looking at both links right now, the askubuntu offers a gnome extension that does what you want (and both answer and the question itself hint at some dconf magic you can try).
I definitely won't use gnome in that case. Just a simple X server with the required icons/apps on the desktop and that's all.
Very true.
Instead of installing everything & the kitchen sink, then having to hobble it all again, why not start with a clean slate and configure everything as desired.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.