All of lore.kernel.org
 help / color / mirror / Atom feed
* [refpolicy] A likewise.te bug?
@ 2011-05-25  9:38 HarryCiao
  2011-05-25 12:38 ` Christopher J. PeBenito
  0 siblings, 1 reply; 3+ messages in thread
From: HarryCiao @ 2011-05-25  9:38 UTC (permalink / raw)
  To: refpolicy


Hi Chris,

I happened to find the likewise.te calls the seutils_run_semanage() interface in the below way:

seutil_run_semanage(lsassd_t, lsassd_t)

Clearly the 2nd argument should be of some role, rather than the lsassd_t type.

I am not familiar with this module, just raise this potential issue here.

Thanks,
Harry

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.tresys.com/pipermail/refpolicy/attachments/20110525/2eb657b6/attachment.html 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [refpolicy] A likewise.te bug?
  2011-05-25  9:38 [refpolicy] A likewise.te bug? HarryCiao
@ 2011-05-25 12:38 ` Christopher J. PeBenito
  2011-05-25 12:39   ` Daniel J Walsh
  0 siblings, 1 reply; 3+ messages in thread
From: Christopher J. PeBenito @ 2011-05-25 12:38 UTC (permalink / raw)
  To: refpolicy

On 05/25/11 05:38, HarryCiao wrote:
> I happened to find the likewise.te calls the seutils_run_semanage()
> interface in the below way:
> 
> seutil_run_semanage(lsassd_t, lsassd_t)
> 
> Clearly the 2nd argument should be of some role, rather than the
> lsassd_t type.
> 
> I am not familiar with this module, just raise this potential issue here.

Yes, its a bug.  I've fixed it.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [refpolicy] A likewise.te bug?
  2011-05-25 12:38 ` Christopher J. PeBenito
@ 2011-05-25 12:39   ` Daniel J Walsh
  0 siblings, 0 replies; 3+ messages in thread
From: Daniel J Walsh @ 2011-05-25 12:39 UTC (permalink / raw)
  To: refpolicy

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/25/2011 08:38 AM, Christopher J. PeBenito wrote:
> On 05/25/11 05:38, HarryCiao wrote:
>> I happened to find the likewise.te calls the seutils_run_semanage()
>> interface in the below way:
>>
>> seutil_run_semanage(lsassd_t, lsassd_t)
>>
>> Clearly the 2nd argument should be of some role, rather than the
>> lsassd_t type.
>>
>> I am not familiar with this module, just raise this potential issue here.
> 
> Yes, its a bug.  I've fixed it.
> 

Here is the Fedora patch for likewise with a couple of other minor fixes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk3c+IsACgkQrlYvE4MpobO26wCgiktg/GODjpKTSTrAA2WyiD+0
GaYAoOrxEchgFl4btlXsCBRGNCJN14Lc
=yr14
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: services_likewise.patch
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20110525/b0bf1965/attachment.pl 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: services_likewise.patch.sig
Type: application/pgp-signature
Size: 72 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20110525/b0bf1965/attachment.bin 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-05-25 12:39 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-25  9:38 [refpolicy] A likewise.te bug? HarryCiao
2011-05-25 12:38 ` Christopher J. PeBenito
2011-05-25 12:39   ` Daniel J Walsh

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.