On Wed, 2011-03-16 at 18:05 -0400, Rob Crittenden wrote:
If a hostname has mixed-case in /etc/hosts or a mixed-case name is
passed into either the client or host installer we need to prevent
installation. The hostname should be lower-case otherwise all sorts of
odd problems will happen.
Martin Kosek wrote:
On Wed, 2011-03-16 at 18:05 -0400, Rob Crittenden wrote:
If a hostname has mixed-case in /etc/hosts or a mixed-case name is
passed into either the client or host installer we need to prevent
installation. The hostname should be lower-case otherwise all sorts of
odd problems
On Thu, 2011-03-17 at 10:24 -0400, Rob Crittenden wrote:
Martin Kosek wrote:
On Wed, 2011-03-16 at 18:05 -0400, Rob Crittenden wrote:
If a hostname has mixed-case in /etc/hosts or a mixed-case name is
passed into either the client or host installer we need to prevent
installation. The
Re-enable ldapi code in ipa-ldap-updater and remove the searchbase
restriction when run in --upgrade mode. This allows us to autobind
giving root Directory Manager powers.
This also:
* corrects the ipa-ldap-updater man page
* remove automatic --realm, --server, --domain options
* handle
I'm trying to figure out what should happen in the following case;
A user goes to a website that they've never visited before.
The site is using Kerberos, and thus the browser gets back a Negotiate
response.
At this point, the browser chops the hostname off the URL and requests
the TXT
From d8c6d615a87a9f8d06260ad06d4caec6ddd55526 Mon Sep 17 00:00:00 2001
From: Adam Young ayo...@redhat.com
Date: Thu, 17 Mar 2011 19:52:52 -0400
Subject: [PATCH] pwpolicy priority
Priority is now a required field in order to add a new password policy. Thus, not having the field present means we
On 3/17/2011 7:04 PM, Adam Young wrote:
Some issues:
1. There's a jslint warning.
2. Try creating a new password policy, then edit and change the
priority. When you click Update the priority will get updated but the
field will become read only.
