[497] in Enterprise Print Delivery Team
Re: Security issue
daemon@ATHENA.MIT.EDU (David F Lambert)
Mon Sep 4 16:07:01 2000
Message-Id: <10009042006.AA00408@MIT.EDU>
Date: Mon, 04 Sep 00 16:00:38 EDT
From: David F Lambert <LAMBERT@MITVMA.MIT.Edu>
To: "Lynne E. Durland" <durland@MIT.EDU>,
Enterprise Printing Delivery Project Team <printdel@MIT.EDU>
In-Reply-To: Message of Wed, 16 Aug 2000 12:57:25 -0400 from <durland@MIT.EDU>
On Wed, 16 Aug 2000 12:57:25 -0400 Lynne said:
>Hey gang,
>
>the thought bubbled up in my brain during the discussions yesterday with
>Theresa at the demo. We currently have "regular" and "secure" queues
>associated with the mainframe printers. Are we planning to setup similar
>entities within the IPM?
>
>The secure queues cannot be seen by general users and are used for checks
>and other sensitive data.
>
>Lynne
>
>Lynne E. Durland
>Information Systems
>Database Services
>W91-109
>O:258-5857
>C: 617-293-8091
>B: 617-430-8762
>H: KB1FEM
>
> "Happiness often sneaks through a door you didn't know you left open."
>
> --John Barrymore
Absopositively. I don't see this need as being any different than
the needs for other queues - paper size, sim/duplex, special stock, etc.
If there are "special handling" requirements, the ops staff needs to
know that. Is there another way instead of a separate queue to denote
this?
One correction/clarification to Lynne's note. The mainframe's secure
queues are really no different than non-secure queues with regard to
access - owners of those files can manipulate them just like their
own files in the non-secure queues. Ops & systems staff have access
to everything.
-Dave
