From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from goalie.tycho.ncsc.mil (goalie [144.51.242.250]) by tarius.tycho.ncsc.mil (8.14.4/8.14.4) with ESMTP id s4O3CuS0009272 for ; Fri, 23 May 2014 23:12:56 -0400 Received: by mail-pb0-f53.google.com with SMTP id md12so4961113pbc.40 for ; Fri, 23 May 2014 20:12:54 -0700 (PDT) Received: from [192.168.1.2] ([117.201.88.118]) by mx.google.com with ESMTPSA id wp3sm6880246pbc.67.2014.05.23.20.12.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 May 2014 20:12:54 -0700 (PDT) Message-ID: <53800D97.2090103@gmail.com> Date: Sat, 24 May 2014 08:40:15 +0530 From: dE MIME-Version: 1.0 To: selinux@tycho.nsa.gov Subject: Re: SAMBA WITH SELINUX References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------070008060108010205020804" List-Id: "Security-Enhanced Linux \(SELinux\) mailing list" List-Post: List-Help: This is a multi-part message in MIME format. --------------070008060108010205020804 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 05/24/14 01:02, toản cù wrote: > Hi all! > > I just researching policy in selinux and Samba , SELinux has > policy module separate for samba. I only know the label samba_share_t > used to share data when labeled in SELinux enforcing mode. > > I want to use SELinux further intervention on the issue > of decentralization for each user to access data on the samba. How the > same file (*. docx, *. txt), user1 can read, write but user2 is not. > > And one more question: in a group have different users the same > access to the samba. those users have some same rights, and some the > right different. example the rights to read,write on a file is > different. How to make a difference the rights between users in the > same group > > Look forward your help! > > Thanks! > > > -- > Mr.Toan-Cu Xuan > > School of Electronics and Telecommunications > > Hanoi University of Science and Technology > > 1 Dai Co Viet, Ha noi, Viet nam. > > Phone: 01656228762 > > Email:xuantoanbkfet@gmail.com > > > > _______________________________________________ > Selinux mailing list > Selinux@tycho.nsa.gov > To unsubscribe, send email to Selinux-leave@tycho.nsa.gov. > To get help, send an email containing "help" to Selinux-request@tycho.nsa.gov. I don't think smbd spawns a new process when a new user logs in (that's why we have 'force user'), so there's no way for SELinux to identify the login user of the SMB service. Otherwise what could've been done is set the umask to 077 and inherit owner, inherit permissions to yes. So DAC whould've been good enough for the purpose. I dont remember how --------------070008060108010205020804 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

On 05/24/14 01:02, toản cù wrote:

Hi all!

I just researching policy in selinux and Samba , SELinux has policy module separate for samba. I only know the label samba_share_t used to share data when labeled in SELinux enforcing mode.

I want to use SELinux further intervention on the issue of decentralization for each user to access data on the samba. How the same file (*. docx, *. txt), user1 can read, write but user2 is not.

And one more question: in a group have different users the same access to the samba. those users have some same rights, and some the right different. example the rights to read,write on a file is different. How to make a difference the rights between users in the same group

Look forward your help!

Thanks!

--
Mr.Toan-Cu Xuan

School of Electronics and Telecommunications

Hanoi University of Science and Technology

1 Dai Co Viet, Ha noi, Viet nam.

Phone: 01656228762

Email:xuantoanbkfet@gmail.com
_______________________________________________
Selinux mailing list
Selinux@tycho.nsa.gov
To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
To get help, send an email containing "help" to Selinux-request@tycho.nsa.gov.

I don't think smbd spawns a new process when a new user logs in (that's why we have 'force user'), so there's no way for SELinux to identify the login user of the SMB service.

Otherwise what could've been done is set the umask to 077 and inherit owner, inherit permissions to yes. So DAC whould've been good enough for the purpose.

I dont remember how
--------------070008060108010205020804--