-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/09/2013 01:06 PM, Chris Hartman wrote:
> Could you file a bug against pam_mkhomedir?
>
> I can definitely do this, though I'm not exactly sure what the bug
> is because I don't think I understand the problem fully.
> "mkhomedir.so doesn't play n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/09/2013 01:22 PM, Dmitri Pal wrote:
> On 10/09/2013 01:05 PM, Ondrej Valousek wrote:
>> Hi List,
>>
>> I have noticed that since F19 I can not use lines beginning with
>> spaces in sssd.conf - sssd complains otherwise. Was this an
>> intentiona
On 10/09/2013 01:05 PM, Ondrej Valousek wrote:
> Hi List,
>
> I have noticed that since F19 I can not use lines beginning with
> spaces in sssd.conf - sssd complains otherwise.
> Was this an intentional change? I used spaces/white characters to
> ident the config for better readability.
> Thanks,
>
> Could you file a bug against pam_mkhomedir?
I can definitely do this, though I'm not exactly sure what the bug is
because I don't think I understand the problem fully. "mkhomedir.so doesn't
play nice with aliased usernames"? Can you offer a little more guidance
and/or explanation?
When runnin
Hi List,
I have noticed that since F19 I can not use lines beginning with spaces in
sssd.conf - sssd complains otherwise.
Was this an intentional change? I used spaces/white characters to ident the
config for better readability.
Thanks,
Ondrej
___
ss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/09/2013 12:20 PM, Chris Hartman wrote:
> Well, in a related development, it appears there is a hardware
> issue with the testing PC- bad hard disk. Will replace, reinstall
> OS, and re-test.
>
> However, there is definitely a case sensitivity is
Well, in a related development, it appears there is a hardware issue with
the testing PC- bad hard disk. Will replace, reinstall OS, and re-test.
However, there is definitely a case sensitivity issue happening.
My other hosts only have an issue when logging in with Guest as opposed to
guest. Gues
Hmm. This may be host-specific. I'm not able to reproduce this problem on
other hosts.
Does getent use a cache that could be screwing things up? I've disabled
caching and enumerating in SSSD temporarily for troubleshooting.
-Chris
On Wed, Oct 9, 2013 at 11:47 AM, Chris Hartman wrote:
> geten
getent passwd Guest returns:
guest:*:1596000501:1596000514:Guest:/:/bin/bash
Also, I'm wondering if this has something to do with case sensitivity?
`getent passwd Guest` and `getent passwd guest` return the same result.
Also, I can login with either Guest or guest. Just a thought.
-Chris
On W
On Wed, Oct 09, 2013 at 11:25:51AM -0400, Chris Hartman wrote:
> I'm having a problem getting pam_mkhomedir.so to make a user's home
> directory when it's specified using an LDAP attribute. The backend
> directory server is AD on Server 2008. The client is Ubuntu 12.04, sssd
> version 1.11.1.
>
>
I'm having a problem getting pam_mkhomedir.so to make a user's home
directory when it's specified using an LDAP attribute. The backend
directory server is AD on Server 2008. The client is Ubuntu 12.04, sssd
version 1.11.1.
First, my sssd.conf:
[sssd]
config_file_version = 2
debug_level = 0
reconn
On Wed, Oct 09, 2013 at 09:08:05AM +0200, Sumit Bose wrote:
> On Tue, Oct 08, 2013 at 11:33:45PM +, Ondrej Valousek wrote:
> > Looks like this only happens if I specify the ad_server manually. If I let
> > sssd do the DNS SRV discovery, it works OK.
> > I still think it should work OK if I spe
On Tue, Oct 08, 2013 at 11:33:45PM +, Ondrej Valousek wrote:
> Looks like this only happens if I specify the ad_server manually. If I let
> sssd do the DNS SRV discovery, it works OK.
> I still think it should work OK if I specify the AD sever to connect to...
This is a know issue, if you set
13 matches
Mail list logo
