RBAC question


 
Thread Tools Search this Thread
Operating Systems HP-UX RBAC question
# 1  
Old 11-11-2009
RBAC question

hi every one i tried rbac and i made
1- role called GizaRoot
2- group called gizagroup
3- added privlage autherization called "m.k"
/usr/sbin/useradd:dfltSmiliem.k,*):0/0//:dflt:dflt:dflt:

i assigned the role to group and add user to that group then su to user and tried to use the command
privrun useradd maxim it worked and every thing ok but i don't under stand why it uses the euid=0 and ruid=0 and i assigned only to group not user i tried to make the line like this /usr/sbin/useradd:dfltSmiliem.k,*)://107/0:dflt:dflt:dflt:
but it didn't work so i want one to explain to understand and thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

RBAC and LDAP users (AD)

Hello everyone, I am having trouble with something, and I can't find the right answer online. On our company, we are using LDAP Authentication with Active Directory (Windows 2008 Servers) to have a centralized management of AIX 7.1 users. So far so good, but now, we want to implement RBAC on... (7 Replies)
Discussion started by: Janpol
7 Replies

2. Solaris

RBAC related question.....

I am referring Bill Calkins(SCSA exam prep) for RBAC..actually i wanted to make a normal user to get the privilege to run a command through authorization, not through profile files... This is the exact steps given by Bill calkins.. 1.roleadd -m -d /export/home/adminusr -c... (11 Replies)
Discussion started by: saagar
11 Replies

3. Solaris

rbac problem.

Hi all! On backup server with contab my script worked, but one command don't fine to be executed: bash-3.00$ scp itadmin@172.17.0.44:/export/backups/* /bckp1/opencms/bcp_`date +%Y%m%d`/ www-zone.cfg 100%... (0 Replies)
Discussion started by: sotich82
0 Replies

4. Linux

Sudo user vs RBAC

Hi all, What the difference between the sudo users & RBAC when the talk of effects after doing the above comes??? any differences between them ,kindly list ?? (1 Reply)
Discussion started by: saurabh84g
1 Replies

5. UNIX for Dummies Questions & Answers

Unix Rbac

Can anyone help me on "How to change Unix to support RBAC policy"? (4 Replies)
Discussion started by: JPoroo
4 Replies

6. AIX

RBAC in 5.3 Question

I would like to use the Role Based access control to granulize some of the administration of AIX systems in our organization. Across the company we will be using aix 5.3. One of these roles will only have the access to make, change and delete users, something similar to ManageAllUsers. The thing... (1 Reply)
Discussion started by: dgaixsysadm
1 Replies

7. Shell Programming and Scripting

Automating RBAC with IF/Then statement

what would be easier to automate a script if/then ? (0 Replies)
Discussion started by: deaconf19
0 Replies

8. Solaris

RBAC Help

do i have to create a new account to add a role? i want the sysadmin login i have 3 users on my systems sysadmin secman oc01 also 3 profiles SA (goes t0 sysadmin account) SSO (goes to secman account) LMICS (goes to oc01 account) the user accounts are located in /h/USERS/local the... (4 Replies)
Discussion started by: deaconf19
4 Replies

9. Solaris

Rbac

I am trying to let user asillitoe su to the godbrook role to execute commands. I have editted files as follows: user_attr: asillito::::type=normal;roles=godbrook godbrook::::type=role;profiles=Gadbrook,All prof_attr: Gadbrook:::Allow root commands to be used by godbrook: exec_attr:... (0 Replies)
Discussion started by: chrisdberry
0 Replies

10. UNIX for Advanced & Expert Users

RBAC logging

Hi gurus: I have not come accross any links on the internet that shows how to set up logging in RBAC and also is it possible to get the granularity and simplicity of sudo logging in RBAC. I have heard that RBAC logs are complicated to read and not as simple and granular as sudo logs. Your help... (0 Replies)
Discussion started by: geomonap
0 Replies
Login or Register to Ask a Question
LIBPACK(3)						     Library Functions Manual							LIBPACK(3)

NAME
libpack - support for connected components SYNOPSIS
#include <graphviz/pack.h> typedef enum { l_clust, l_node, l_graph, l_array} pack_mode; typedef struct { float aspect; /* desired aspect ratio */ int sz; /* row/column size size */ unsigned int margin; /* margin left around objects, in points */ int doSplines; /* use splines in constructing graph shape */ pack_mode mode; /* granularity and method */ boolean *fixed; /* fixed[i] == true implies g[i] should not be moved */ packval_t* vals; /* for arrays, sort numbers */ int flags; } pack_info; point* putRects(int ng, boxf* bbs, pack_info* pinfo); int packRects(int ng, boxf* bbs, pack_info* pinfo); point* putGraphs (int, Agraph_t**, Agraph_t*, pack_info*); int packGraphs (int, Agraph_t**, Agraph_t*, pack_info*); int packSubgraphs (int, Agraph_t**, Agraph_t*, pack_info*); pack_mode getPackMode (Agraph_t*, pack_mode dflt); int getPack (Agraph_t*, int, int); int isConnected (Agraph_t*); Agraph_t** ccomps (Agraph_t*, int*, char*); Agraph_t** pccomps (Agraph_t*, int*, char*, boolean*); int nodeInduce (Agraph_t*); DESCRIPTION
libpack supports the use of connected components in the context of laying out graphs using other graphviz libraries. One set of functions can be used to take a single graph and break it apart into connected components. A complementary set of functions takes a collection of graphs (not necessarily components of a single graph) which have been laid out separately, and packs them together. As this library is meant to be used with libcommon, it relies on the Agraphinfo_t, Agnodeinfo_t and Agedgeinfo_t used in that library. The specific dependencies are given below in the function descriptions. Creating components Agraph_t** ccomps (Agraph_t* g, int* cnt, char* pfx) The function ccomps takes a graph g and returns an array of pointers to subgraphs of g which are its connected components. cnt is set to the number of components. If pfx is non-NULL, it is used as a prefix for the names of the subgraphs; otherwise, the string ``_cc_'' is used. Note that the subgraphs only contain the relevant nodes, not any corresponding edges. Depending on the use, this allows the caller to retrieve edge information from the root graph. The array returned is obtained from malloc and must be freed by the caller. The function relies on the mark field in Agnodeinfo_t. Agraph_t** pccomps (Agraph_t* g, int* cnt, char* pfx, boolean* pinned) This is identical to ccomps except that is puts all pinned nodes in the first component returned. In addition, if pinned is non-NULL, it is set to true if pinned nodes are found and false otherwise. int nodeInduce (Agraph_t* g) This function takes a subgraph g and finds all edges in its root graph both of whose endpoints are in g. It returns the number of such edges and, if this edge is not already in the subgraph, it is added. int isConnected (Agraph_t* g) This function returns non-zero if the graph g is connected. Packing components point* putGraphs (int ng, Agraph_t** gs, Agraph_t* root, pack_info ip) putGraphs packs together a collection of laid out graphs into a single layout which avoids any overlap. It takes as input ng graphs gs. For each graph, it is assumed that all the nodes have been positioned using pos, and that the xsize and ysize fields have been set. If root is non-NULL, it is taken as the root graph of the subgraphs gs and is used to find the edges. Otherwise, putGraphs uses the edges found in each graph gs[i]. For the modes l_node, l_clust, and l_graph, the packing is done using the polyomino-based algorithm of Freivalds et al. This allows for a fairly tight packing, in which a convex part of one graph might be inserted into the concave part of another. The granularity of the poly- ominoes used depends on the value of ip->mode. If this is l_node, a polyomino is constructed to approximate the nodes and edges. If this is l_clust, the polyomino treats top-level clusters as single rectangles, unioned with the polyominoes for the remaining nodes and edges. If the value is l_graph, the polyomino for a graph is a single rectangle corresponding to the bounding box of the graph. The mode l_node specifies that the graphs should be packed as an array. If ip->doSplines is true, the function uses the spline information in the spl field of an edge, if it exists. Otherwise, the algorithm represents an edge as a straight line segment connecting node centers. The parameter ip->margin specifies a boundary of margin points to be allowed around each node. It must be non-negative. The parameter ip->fixed, if non-null, should point to an array of ng booleans. If ip->fixed[i] is true, graph gs[i] should be left at its original position. The packing will first first place all of the fixed graphs, then fill in the with the remaining graphs. The function returns an array of points which can be used as the origin of the bounding box of each graph. If the graphs are translated to these positions, none of the graph components will overlap. The array returned is obtained from malloc and must be freed by the caller. If any problem occurs, putGraphs returns NULL. As a side-effect, at its start, putGraphs sets the bb of each graph to reflect its initial layout. Note that putGraphs does not do any translation or change the input graphs in any other way than setting the bb. This function uses the bb field in Agraphinfo_t, the pos, xsize and ysize fields in nodehinfo_t and the spl field in Aedgeinfo_t. int packGraphs (int ng, Agraph_t** gs, Agraph_t* root, pack_info* ip) This function takes ng subgraphs gs of a root graph root and calls putGraphs with the given arguments to generate a packing of the sub- graphs. If successful, it then invokes shifts the subgraphs to their new positions. It returns 0 on success. int packSubgraphs (int ng, Agraph_t** gs, Agraph_t* root, pack_info* ip) This function simply calls packGraphs with the given arguments, and then recomputes the bounding box of the root graph. int pack_graph(int ng, Agraph_t** gs, Agraph_t* root, boolean* fixed) uses packSubgraphs to place the individual subgraphs into a single layout with the parameters obtained from getPackInfo. If successful, dotneato_postprocess is called on the root graph. point* putRects (int ng, boxf* bbs, pack_info* ip) putRects packs together a collection of rectangles into a single layout which avoids any overlap. It takes as input ng rectangles bbs. Its behavior and return value are analogous to those of putGraphs. However, the modes l_node and l_clust are illegal. The fields fixed and doSplines of ip are unused. int packRects (int ng, boxf* bbs, pack_info* ip) packRects is analogous to packGraphs: it calls putRects and, if this is successful, it translates the rectangles in bbs appropriately. Utility functions The library provides several functions which can be used to tailor the packing based on graph attributes. pack_mode parsePackModeInfo(char* p, pack_mode dflt, pack_info* pinfo) analyzes p as a string representation of pack mode, storing the information in pinfo. If p is "cluster", it returns l_clust; for "graph", it returns l_graph; for "node", it returns l_node; for "array", it returns l_array; for "aspect", it returns l_aspect; otherwise, it returns dflt. Related data is also stored in pinfo. pack_mode getPackModeInfo(Agraph_t * g, pack_mode dflt, pack_info* pinfo) This function processes the graph's "packmode" attribute, storing the information in pinfo. It returns pinfo->mode. The attribute is pro- cessed using parsePackModeInfo with dflt passed as the default argument. pack_mode getPackMode (Agraph_t* g, pack_mode dflt) This function returns a pack_mode associated with g. int getPack (Agraph_t* g, int not_def, int dflt) This function queries the graph attribute "pack". If this is defined as a non-negative integer, the integer is returned; if it is defined as "true", the value dflt is returned; otherwise, the value not_def is returned. pack_mode getPackInfo(Agraph_t * g, pack_mode dflt, int dfltMargin, pack_info* pinfo) This function calls both getPackModeInfo and getPack, storing the information in pinfo. dfltMargin is used for both integer arguments of getPack, with the result saved as pinfo->margin. It returns pinfo->mode. SEE ALSO
dot(1), neato(1), twopi(1), libgraph(3) K. Freivalds et al., "Disconnected Graph Layout and the Polyomino Packing Approach", GD0'01, LNCS 2265, pp. 378-391. BUGS
The packing does not take into account edge or graph labels. AUTHORS
Emden Gansner (erg@research.att.com). 04 APRIL 2009 LIBPACK(3)