-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2010 09:41 AM, Jakub Hrozek wrote:
> On 08/23/2010 03:18 PM, Stephen Gallagher wrote:
>> They are no longer used. The toplevel Makefile.am builds
>> everything now. I forgot to remove them when I moved the Makefile
>> commands up to the root.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2010 09:46 AM, Jakub Hrozek wrote:
> On 08/23/2010 03:19 PM, Stephen Gallagher wrote:
>> On 08/16/2010 01:47 PM, Stephen Gallagher wrote:
>>> If the --without-python-bindings argument was passed to configure, the
>>> SSSD would fail to build.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2010 09:19 AM, Stephen Gallagher wrote:
> Two patches submitted by Maxim
>
> I ack them both.
>
Pushed to master.
- --
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software ve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2010 10:57 AM, Stephen Gallagher wrote:
> On 07/27/2010 10:54 AM, Jakub Hrozek wrote:
>
>
>> Right, new patch attached
>
>
>
> Ack.
>
Long overdue, but this was pushed to master several weeks ago.
- --
Stephen Gallagher
RHCE 804006346
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2010 03:19 PM, Stephen Gallagher wrote:
> On 08/16/2010 01:47 PM, Stephen Gallagher wrote:
>> If the --without-python-bindings argument was passed to configure, the
>> SSSD would fail to build. Prior to this patch, it was only controlling
>> w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2010 03:18 PM, Stephen Gallagher wrote:
> They are no longer used. The toplevel Makefile.am builds
> everything now. I forgot to remove them when I moved the Makefile
> commands up to the root.
>
>
ACK
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/16/2010 01:47 PM, Stephen Gallagher wrote:
> If the --without-python-bindings argument was passed to configure, the
> SSSD would fail to build. Prior to this patch, it was only controlling
> whether to build the C bindings (for use with the local
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Two patches submitted by Maxim
I ack them both.
- --
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
-BEGIN PGP SIGNATURE-
Versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
They are no longer used. The toplevel Makefile.am builds
everything now. I forgot to remove them when I moved the Makefile
commands up to the root.
- --
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in va
thanks for the answer
indeed that seems logical.
Le 23/08/2010 13:17, Stephen Gallagher a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/23/2010 06:00 AM, Eric Doutreleau wrote:
>
>>
>> Does enumeration permit to store credentials for people that have never
>> logged in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2010 06:00 AM, Eric Doutreleau wrote:
>
> Does enumeration permit to store credentials for people that have never
> logged in the machine?
>
No, this cannot be done. Assuming that the LDAP server is configured
properly (where the password
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2010 12:00 PM, Eric Doutreleau wrote:
> Does enumeration permit to store credentials for people that have never
> logged in the machine?
No, you have to log in while online to store credentials.
-BEGIN PGP SIGNATURE-
Version: GnuPG v
hi
i m trying to use sssd 1.2.2-19 on my fedora 13 machine and i have some
questions about enumeration.
Here is my sssd.conf ( ldap part )
[domain/default]
ldap_id_use_start_tls = False
ldap_tls_reqcert = never
cache_credentials = True
ldap_search_base = dc=int-evry,dc=fr
ldap_user_search_base
13 matches
Mail list logo