On 11/19/2014 4:54 PM, Peter Dufault wrote:
> Are the UID and GID per-thread? I assume two different telnet sessions would
> have different credentials.
They can and do now if you want to try the telnetd example. There is an
rtems
and a root account as I recall. One can't write to parts of the
f
Are the UID and GID per-thread? I assume two different telnet sessions would
have different credentials.
I strongly agree that there is a need for credentials in embedded applications,
but I don't see that they can be tied to the RTEMS shell. I'm not sure how UID
and GID work in a single proc
The goal is to provide different command sets for different users. For
example a system could give the customer a certain command set and the
service personal a different one which includes also maintenance operations.
Most of the infrastructure was already present. There were just some
missi
Could you briefly explain a bit more context about the goals for
implementing access control? That is, is it for compliance to some
standard, to address a security need, or something else?
Thanks,
Gedare
On Tue, Nov 18, 2014 at 9:37 AM, Sebastian Huber
wrote:
> This patch set adds access control
This patch set adds access control to the RTEMS shell. The command visibility
and ability to execute are determined by the current user environment and per
command mode, UID and GID values. The user environment is set up by the
rtems_shell_login_check() handler. Commands to alter the mode, UID a
