On Fri, Feb 02, 2018 at 11:46:03AM +0100, Jakub Hrozek wrote:
On Fri, Feb 02, 2018 at 10:07:08AM +0100, Sumit Bose wrote:
> As an alternative, but even more complicated you can make the SID
> available via D-Bus/InfoPipe and then lookup user and group by ID.
> So it looks like sss_nss_getsidbyuid() and sss_nss_getsidbygid() should
> be added to the interface. Would you mind to open a ticket about this on
or do you prefer me doing this?
Maybe I misread your comment and you're actually proposing what I'm
going to say, but can you think of a reason to not expose the SID (if
availabel) on the D-Bus interface in the set of the default attributes?
no, I just meant that from a C client perspective it might be more
cumbersome and might add additional dependencies using the D-Bus
interface to get this information compared to a library call.
> Is there any information leak by this? I think not, because you can
> always open a python console for example and run the id-to-sid
> sssd-devel mailing list -- sssd-devel(a)lists.fedorahosted.org
> To unsubscribe send an email to sssd-devel-leave(a)lists.fedorahosted.org