search for: selinux_context

Displaying 7 results from an estimated 7 matches for "selinux_context".

2014 Jan 14
0
[PATCH] builder, edit, fish: use copy-attributes
...^ ".out") file - -and copy_attributes g src dest = - let has_linuxxattrs = g#feature_available [|"linuxxattrs"|] in - - (* Get the mode. *) - let stat = g#stat src in - - (* Get the SELinux context. XXX Should we copy over other extended - * attributes too? - *) - let selinux_context = - if has_linuxxattrs then ( - try Some (g#getxattr src "security.selinux") with _ -> None - ) else None in - - (* Set the permissions (inc. sticky and set*id bits), UID, GID. *) - let mode = Int64.to_int stat.G.mode - and uid = Int64.to_int stat.G.uid and gid = Int64.to...
2012 Feb 08
2
Fix virt-edit so it preserves permissions (RHBZ#788641)
The first patch preserves file mode, UID, GID and SELinux context across edited files. The second patch adds a useful new command in guestfish ('llz') which shows SELinux context (like 'ls -laZ') that was useful when debugging this. Rich.
2014 Jan 07
8
RFC: copy-attributes command
Hi, attached there is a prototype of patch for adding a new copy-attributes command. Such command would allow copy the attributes of a "file" to another, so for example in guestfish: copy-attributes foo bar permissions:true xattributes:false would only copy the permissions of foo to bar, not copying its extended attributes too. Just few notes: - my first daemon command, so
2012 Feb 10
3
[PATCH 0/3] Fix guestfish edit command.
This is a further, more comprehensive fix for https://bugzilla.redhat.com/show_bug.cgi?id=788641 The guestfish 'edit' command (aka 'emacs', 'vi') suffered from the same problems as virt-edit and more. It could have failed and left a partially overwritten file, and it didn't preserve permissions etc from the original file. These three patches fix all this. The first
2018 Mar 22
2
User name / session idin logs
Hello everyone, I have a question about logging. I need to find out whether it is possible to see user id/session id inside logs or somewhere else. It is not passed in structured across the network, so where should I look to find out, which user (which session) is currently performing the actions?
2018 May 07
1
Re: User name / session idin logs
...-server libvirtd --client 1 > id : 1 > connection_time: 2018-04-12 09:53:46+0200 > transport : unix > readonly : no > unix_user_id : 1000 > unix_user_name : eskultet > unix_group_id : 1001 > unix_group_name: eskultet > unix_process_id: 19053 > selinux_context: unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 > > Regards, > Erik >
2018 Apr 12
0
Re: User name / session idin logs
...18-04-12 09:53:46+0200 # virt-admin client-info --server libvirtd --client 1 id : 1 connection_time: 2018-04-12 09:53:46+0200 transport : unix readonly : no unix_user_id : 1000 unix_user_name : eskultet unix_group_id : 1001 unix_group_name: eskultet unix_process_id: 19053 selinux_context: unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 Regards, Erik