[PATCH] bugfix in buildiso

2011-11-01 Thread Jörgen Maas
Hi, There's a bug in buildiso when duplicate kopt keys are used, e.g. duplicate console= options. Attached patch fixes that, reported and tested by Simon Woolsgrove on cobbler-users@ Please apply to master and stable. -- Grtz, Jörgen Maas 0001-Fix-a-bug-in-buildiso-when-duplicate-kopt-keys-are

A couple of things

2011-11-01 Thread James Cammarata
I've written an authn module for PAM (I'll commit it soon), and it got me thinking about the web GUI security. I'd like to propose that we move the GUI stuff to strictly HTTPS, using some rewrite rules. This would also get rid of the VirtualHost stuff in cobbler_web.conf, since typically the ssl.co

Re: [PATCH] Chain load authentication plugin

2011-11-01 Thread James Cammarata
On Wed, Oct 26, 2011 at 1:28 AM, James Clendenan wrote: > Hi All, > > I've attached an updated version of the authentication chain loading plugin. > > It should apply cleanly to 2.2.1 now, as a few directories have been moved > around. > > Let me know if you run into any problems with it. I real

Re: [PATCH] bugfix in buildiso

2011-11-01 Thread James Cammarata
On Tue, Nov 1, 2011 at 3:34 PM, Jörgen Maas wrote: > Hi, > > There's a bug in buildiso when duplicate kopt keys are used, e.g. > duplicate console= options. > Attached patch fixes that, reported and tested by Simon Woolsgrove on > cobbler-users@ > > Please apply to master and stable. Committed an

Re: A couple of things

2011-11-01 Thread James Cammarata
On Tue, Nov 1, 2011 at 7:36 PM, James Cammarata wrote: > I've written an authn module for PAM (I'll commit it soon), and it got > me thinking about the web GUI security. I'd like to propose that we > move the GUI stuff to strictly HTTPS, using some rewrite rules. This > would also get rid of the V

Re: [PATCH] Chain load authentication plugin

2011-11-01 Thread James Clendenan
Hi James, Thanks for the review. I'll look integrating it deeper into the core of authn unless I hear anyone raising concerns on this. The major reason I did it this way was to ensure that users using the existing version weren't going to get stuck with an incompatible config file after an upgra