On (08/10/13 14:02), Michal Židek wrote:
On 10/07/2013 03:32 PM, Jakub Hrozek wrote:
On Fri, Oct 04, 2013 at 12:52:31PM +0200, Michal Židek wrote:
On 10/04/2013 12:37 PM, Michal Židek wrote:
On 10/03/2013 08:42 PM, Jakub Hrozek wrote:
On Tue, Oct 01, 2013 at 07:04:19PM +0200, Michal Židek wrote:
Hi Sumit,
Sorry for the delay, got sidetracked by trying to find an appropriate way
to handle the well known sids etc..
But thanks to your reminder I got over to do the integration into sssd's
autoconf/make now :)
So here is the patch as an attachment.
(as recommended by the contrib page - but if
Hi,
this patch set aims to fix https://fedorahosted.org/sssd/ticket/2105 .
But since I had to touch the libsss_idmap code for this I found an issue
here as well, which is fixed by the first two patches.
bye,
Sumit
From 5e9daa3af6b1d5ef178ad8737e98908543aa66eb Mon Sep 17 00:00:00 2001
From: Sumit
Hi,
I found this while testing the cifs-utils plugin I opened
https://fedorahosted.org/sssd/ticket/2116 to make sure all affected
versions will be fixed.
bye,
Sumit
From 25250b69421f67884e530d7bf9a38e5de10e3d7a Mon Sep 17 00:00:00 2001
From: Sumit Bose sb...@redhat.com
Date: Wed, 9 Oct 2013
Hello,
I came across an interesting behavior that is IMO worth sharing with
other developers.
It turns out that fmemopen() fails with error 22 EINVAL if the buffer
passed in is of length 0.
Imagine situation: I have a file in the directory of 0 length.
I open it with fopen() or with open() and