On Thu, Jan 31, 2013 at 11:31:35AM +0100, Pavel Březina wrote:
> On 01/29/2013 09:50 PM, Alexander Bokovoy wrote:
> >krb5.conf manual page states that includedir allows to source all
> >files which names are constructed from alpha-numeric chars, dashes and
> >underscores.
> >
> >Files with other ch
On 01/29/2013 09:50 PM, Alexander Bokovoy wrote:
krb5.conf manual page states that includedir allows to source all
files which names are constructed from alpha-numeric chars, dashes and
underscores.
Files with other characters are ignored. So dots as in
domain_realm_example.com are ignored and o
On Tue, Jan 29, 2013 at 10:03:38PM +0100, Jakub Hrozek wrote:
> On Tue, Jan 29, 2013 at 10:50:02PM +0200, Alexander Bokovoy wrote:
> > And here I'm coming to grave error in the SSSD code: the name of
> > explicit mapping file contains non-filtered domain name, which contains
> > dot. krb5.conf manu
On Tue, 29 Jan 2013, Jakub Hrozek wrote:
On Tue, Jan 29, 2013 at 10:50:02PM +0200, Alexander Bokovoy wrote:
And here I'm coming to grave error in the SSSD code: the name of
explicit mapping file contains non-filtered domain name, which contains
dot. krb5.conf manual page states that includedir a
On Tue, Jan 29, 2013 at 10:50:02PM +0200, Alexander Bokovoy wrote:
> And here I'm coming to grave error in the SSSD code: the name of
> explicit mapping file contains non-filtered domain name, which contains
> dot. krb5.conf manual page states that includedir allows to source all
> files which name
Hi!
I've been chasing few bugs in FreeIPA's trusted domains support and
found out some grave bugs in both SSSD and FreeIPA.
On FreeIPA server side we configure krb5.conf using following settings:
-
includedir /var/lib/sss/pubconf/krb5.include.d
[l
