× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks, Pete - and others who responded. I think I have a better
understanding of chroot now. In addition to reading the responses and
following the links in this thread, I have reviewed other resources on the
Internet as well.

The mechanics of limiting and granting authorities under IBM i are
significantly different than *nix environments, but I understand the
overall objective of restricting users and protecting "system" objects is
the same.

If I understand correctly, the idea is more than just restricting a user's
"command line access" to the "root" directory. The idea is to use "scripts"
to copy *nix binaries (executables) and data objects to user directories to
create a sand-boxed runtime environment for the user. That's kind of like
creating a VM at AWS from an "image"; Of course there are differences too.

As a follow-up to Vern's question regarding access to /qsys.lib; Without a
chroot setup, would users of the *SSHD daemon be able to access /qsys.lib/*
objects otherwise, from remote *nix shells?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.