Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
History is an internal command, so I don't think you can do it directly. You could put a dummy alias in each user's .bashrc though to execute some useless command.
Functions supersede aliases and are searched for before builtins. Setting the alias in the users shell resources enables users to muck with it so better use system-wide /etc/profile.d/. The question remains though what the reason is for requiring this anyway. If this is about preserving history I'd point to 'rootsh' (again).
Functions supersede aliases and are searched for before builtins. Setting the alias in the users shell resources enables users to muck with it so better use system-wide /etc/profile.d/. The question remains though what the reason is for requiring this anyway. If this is about preserving history I'd point to 'rootsh' (again).
Any alias to command 'command' easily bypassed by user with
Code:
\command
But I failed to see what's a point of disabling history.
Both aliases and functions can be unset or bypassed. I kind of wondered the same and that's why I already asked "the question remains though what the reason is for requiring this anyway".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.