On Thu, August 12, 2010 22:26, Petter Reinholdtsen wrote:
> When the freeze was announced, I was working on an updated sssd
> package with code to automatically detect the configuration settings
> during installation, to have this included in Squeeze. The freeze
> caught us a bit by surprise, but
[Julien Cristau]
> Indeed I'm more worried about it outputting garbage than failing
> outright.
I'm not, as it would simply bring the user back to the behaviour in
version 1.2.1-1, where the admin need to replace the config with his
own (the default with local database is not really providing the
On Sat, Sep 4, 2010 at 23:34:46 +0200, Petter Reinholdtsen wrote:
> [Julien Cristau]
> > What's the behaviour of the package installation if ping and host,
> > as used by debian/generate-config, are not installed?
>
> The error handling of the autodetection is simple. If the
> autodetection fai
[Julien Cristau]
> What's the behaviour of the package installation if ping and host,
> as used by debian/generate-config, are not installed?
The error handling of the autodetection is simple. If the
autodetection fail, the old static setup (with a local database only)
is set up instead. In othe
On Mon, Aug 30, 2010 at 15:45:37 +0200, Petter Reinholdtsen wrote:
> Any news on this freeze exception request? I believe the sssd package
> in squeeze is unreleasable with bug #594413 in place, so it would be
> very nice if a fix would make it into squeeze soon.
>
What's the behaviour of the pa
[Petter Reinholdtsen]
> [Petter Reinholdtsen]
>> These are the changelog entries since the version currently in
>> testing:
>
> Since my first request for a freeze exception, a serious security
> issue was discovered and fixed. I just uploaded the fix. This is the
> changelog:
>
> sssd (1.2.1-4)
[Petter Reinholdtsen]
> These are the changelog entries since the version currently in
> testing:
Since my first request for a freeze exception, a serious security
issue was discovered and fixed. I just uploaded the fix. This is the
changelog:
sssd (1.2.1-4) unstable; urgency=low
* Add patc
[Philipp Kern]
> I do see (3) "adhere to standards and prefer SRV records, requiring
> manual configurations on sites that screwed up".
This is really false dichtonomy, as it is not a question of adhering
to standards, but which setup should have priority regarding these
standards. For uio.no, W
On 08/17/2010 02:34 PM, Petter Reinholdtsen wrote:
Well, the options at this time is to (1) release sssd without any
automatic configuration (version 1.2.1-1), ensuring it require manual
configuration at all sites or (2) updating the version in testing with
the version in unstable (version 1.2.1-
[Philipp Kern]
> I still have to align with Russ' reasoning. The SRV handling looks
> totally wrong. To do it this way just to accommodate a certain
> broken site does not look like technical excellence to me. Sorry.
Well, the options at this time is to (1) release sssd without any
automatic co
On 08/13/2010 07:40 AM, Petter Reinholdtsen wrote:
If the new autodetection do not work, the sites will be no worse off
than before, where the the old static default configuration had to be
manually replaced after installation.
So the new version make the package better for some sites, and leave
[Petter Reinholdtsen]
> When the freeze was announced, I was working on an updated sssd
> package with code to automatically detect the configuration settings
> during installation, to have this included in Squeeze. The freeze
> caught us a bit by surprise, but this new autodetection code is now
Petter Reinholdtsen writes:
> [Russ Allbery]
>> It's not uncommon for specific hostnames to be grabbed by some other
>> department or project for legacy reasons, and one of the primary
>> purposes of SRV records is to be the canonical source of data so that
>> people don't do the wrong thing with
[Russ Allbery]
> That's frustrating, but the current code is going to break for a
> bunch of other people and is also going directly against the
> intended purpose for the SRV records.
If the new autodetection do not work, the sites will be no worse off
than before, where the the old static defaul
Petter Reinholdtsen writes:
> [Russ Allbery]
>> You should reverse this logic and check for and prefer the SRV record
>> first, as that's the documented purpose of the SRV record and any site
>> that's configured the SRV record probably knows what they're doing and
>> isn't going to want you to d
First of all, thank you for the feedback. :)
[Russ Allbery]
> You should reverse this logic and check for and prefer the SRV
> record first, as that's the documented purpose of the SRV record and
> any site that's configured the SRV record probably knows what
> they're doing and isn't going to wan
Not a review of the upload, but for the maintainer script implementation
here:
Petter Reinholdtsen writes:
> +# See if we can find an LDAP server. Prefer ldap.domain, but also
> +# accept SRV records if no ldap.domain server is found.
> +lookup_ldap_uri() {
> +domain="$1"
> +if ping -c2
When the freeze was announced, I was working on an updated sssd
package with code to automatically detect the configuration settings
during installation, to have this included in Squeeze. The freeze
caught us a bit by surprise, but this new autodetection code is now
working, and it would be very
18 matches
Mail list logo
