[6520] in Release_7.7_team
Re: Kerberized printing, the saga continues
daemon@ATHENA.MIT.EDU (Mark W. Manley)
Tue Nov 17 16:29:16 2009
Date: Tue, 17 Nov 2009 16:29:06 -0500 (EST)
From: "Mark W. Manley" <mmanley@MIT.EDU>
To: Geoffrey Thomas <geofft@mit.edu>
cc: Jonathan Reed <jdreed@mit.edu>, Stuart Peloquin <peloquin@mit.edu>,
Garry Zacheiss <zacheiss@mit.edu>,
"release-team@mit.edu" <release-team@mit.edu>
In-Reply-To: <alpine.DEB.1.10.0911171516470.19258@dr-wily.mit.edu>
Message-ID: <alpine.DEB.2.00.0911171625510.23746@green-arrow.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: -2.599
X-Spam-Flag: NO
I haven't retrofitted the dorm printer accounting scripts yet to work with
CUPS. Honestly, I'm not really soliciting *more* printers to be
Kerberized at this juncture for a variety of reasons.
It's just as easy for me to create test queues to existing printers that
are Kerberized for testing. I have such a queue in place, but haven't had
time today to play with it.
-MM
On Tue, 17 Nov 2009, Geoffrey Thomas wrote:
> On Nov 17, 2009, at 12:03 PM, Mark W. Manley wrote:
>
>> I propose, therefore, that we move these DORM Kerberized queues from LPRng
>> to CUPS soon. I'm still testing, but so far that's proven fairly reliable
>> in allowing the quick list to work again in DebAthena, as well as letting
>> people print on the command line using the CUPS client. What I still need
>> to test is making sure that clients can print to any of the CUPS servers
>> and having their server do The Right Thing [tm] in handling the job (the
>> servers bounce jobs between each other so that there is really one server
>> to deliver the job to each printer--one server to handle all the spooling).
>> That kind of testing shouldn't take long to do.
>
> If you'd like to, it would almost certainly make sense to move Next's
> printer, tree-eater, to CUPS and Kerberize it for testing. We've wanted our
> printer to be Kerberized and access-restricted and switched to Kerberized
> printing not much more than a year ago, but we gave that up when moving the
> cluster to Debathena. I can check that Next Exec is okay with this, and I'd
> be able to notice if something goes wrong in advance of moving other dorms'
> printers to CUPS. (I don't particularly care if you only require Kerberos
> auth from any principal, and don't ACL it at the moment.)
>
> Just curious -- will CUPS-native printers still let us get the weekly page
> count reports from errors@?
>
> --
> Geoffrey Thomas
> geofft@mit.edu
>
