On Mon, 2011-05-16 at 22:12 -0400, Rob Crittenden wrote:
> Martin Kosek wrote:
> > This patch is based on old Pavel's patch.
> >
> > I am considering applying the patch for master branch only as it changes
> > an API (adds a new flag) and is a sort of new-functionality-ish.
> >
> > --
> > Automatic
On Mon, 2011-03-28 at 11:12 -0400, Rob Crittenden wrote:
> We should gracefully handle the case where no TGT has been forwarded.
> Right now we return a 500 error.
>
> ticket 1101
>
> rob
This works fine on the server, nice error response from RPC server is
returned. However, I was wondering if
Hello,
attached series of patches cleans code a little (mostly removes unused
variables) and makes locking inside bind-dyndb-ldap more readable and
understandable.
Most of the cleanup series gets rid of the ldap_connection->database
reference because there is a reference from "database" variable
Hello all,
this series adds support for loading newly-added zones from LDAP.
Currently you must set `arg "zone_refresh ";` in your
named.conf to enable this feature because by default the plugin doesn't
check for new zones. "rndc reload" is no longer needed to pick new zones.
Note when you delete
On Mon, 2011-04-11 at 17:05 -0400, Rob Crittenden wrote:
> Enable 389-ds SSL host checking by defauilt
>
> Enforce that the remote hostname matches the remote SSL server
> certificate when 389-ds operates as an SSL client.
>
> Also add an update file to turn this off for existing installations.
Please review and ACK.
Kyle Baker
Visual Designer
Desk - 978 392 3116
IRC - kylebaker
From f4ebb6d122a8d00ef89af8a009f90529e6b36bfc Mon Sep 17 00:00:00 2001
From: kylebaker
Date: Tue, 17 May 2011 13:17:44 -0400
Subject: [PATCH] Search Box
---
install/ui/ipa.css | 40 +
Martin Kosek wrote:
On Mon, 2011-03-28 at 11:12 -0400, Rob Crittenden wrote:
We should gracefully handle the case where no TGT has been forwarded.
Right now we return a 500 error.
ticket 1101
rob
This works fine on the server, nice error response from RPC server is
returned. However, I was w
There are a wide variety of install scenarios, so we don't get too
specific on some scenarios. One that is pretty common in the test and
acceptance phase that might not be a real issue in a live deployment
deals with DHCP values for nameservers. For example, when coding on my
laptop, the DHCP
Rob Crittenden wrote:
Martin Kosek wrote:
On Mon, 2011-03-28 at 11:12 -0400, Rob Crittenden wrote:
We should gracefully handle the case where no TGT has been forwarded.
Right now we return a 500 error.
ticket 1101
rob
This works fine on the server, nice error response from RPC server is
ret
