Via:        UK.AC.LEEDS.GPS; 17 NOV 92 14:34:59 GMT
Priority:   normal
X-Mailer:   Pegasus Mail v2.3 (R4).
Newsgroups: bit.listserv.novell
Date:         Tue, 17 Nov 1992 14:31:21 GMT
Reply-To:     r.m.whysall@mailer.leeds.ac.uk
From:         Ros Whysall <ECL6ROS@LUCS-01.NOVELL.LEEDS.AC.UK>
Subject:      Novell LPR implementation - problem with banner/usernames

Dear All

We have une petite problemette with the NFS lpr gateway
implementation by Novell concerning usernames and banner names sent
with print jobs.


HERE IS THE SETUP:

Netware -> UNIX printing
Novell users printing to LaserWriters hanging off the back of sun
servers.
Accounting software running on the UNIX system which debits all users
according to their username (uid).


HERE IS THE PROBLEM:

The implementation of lpr which Novell uses ignores the username of
the person sending the job, and only notices the name used for
banner purposes.  Woops, you can alter the banner name and get your
favourite enemies account debited; alternatively, suppress the banner
and hey presto the job won't print as the accounting software has no
account to debit.  I haven't found any fixes for printjobs going in
this direction (Netware->UNIX), but would be pleased to hear of any.


HERE IS THE IMPLEMENTATION

This is an extract from "man lpr" on our sun systems, concerning
information sent in the "header" of the print job

L    Literal.  This line contains identification infor-
     mation  from the password file, and causes a burst
     page to be printed.
P    Person.  Login name  of  the  person  who  invoked
     lpr(1).   This  is  used  to  verify  ownership by
     lprm(1).

UNIX uses the uid of the person who originally logged on in both of
these.  If this is a correct implementation of lpr, then P at least
should really be the Netware user name, not the Netware banner name,
don't you think.  L could then be used for the Netware banner name.


HERE ARE SOME EXAMPLES:

If you send a job which has no banner name specifically entered, the
banner name is derived from the Netware username by default (in all
printing situations, not just NFS stuff).  The following is what
arrives at the UNIX end, in this situation when you send a file
called temp.txt:

    (Job submitted by user ecl6ros no action taken to alter the
    banner)

    Hlucs-01
    Pecl6ros
    JTEMP.TXT
    Lecl6ros
    Clucs-01
    ldfA247lucs-01
    UdfA247lucs-01
    NLUCS-01/USERX:ECL6ROS\TEMP.TXT
    TTEMP.TXT

Both P and L lines read ecl6ros

You can see what happens in other situations from the following two
examples.  When the banner is suppressed the file is never printed,
(accounting software has no account to debit) and when it is altered,
both P and L use the banner name, not the Netware user name.

    Job submitted by user ecl6ros with banner suppressed in
    pconsole

    P
    JTEMP.TXT
    ldfA245lucs-01
    UdfA245lucs-01
    NLUCS-01/USERX:ECL6ROS\TEMP.TXT
    TTEMP.TXT


    This job was submitted by user ecl6ros with a banner of ecl6ph

    Hlucs-01
    Pecl6ph
    JLST:
    Lecl6ph
    Clucs-01
    ldfA236lucs-01
    UdfA236lucs-01
    NLUCS-01/USERX:ECL6ROS\TEMP.TXT
    TTEMP.TXT

Admittedly, our problem stems from the fact that we are using
accounting software, but what does everyone feel about the
implementation?  Does anyone have any suggestions as to how we can
get round this - doing stuff on an individual user basis using
printcon is not secure enough, or viable.  TIA

Ros




******************************************************************
Ros Whysall         Email(Internet) r.m.whysall@mailer.leeds.ac.uk
Computing Service        (JANET) r.m.whysall@uk.ac.leeds.mailer
University of Leeds Tel: (UK) 0532 335837
Leeds, LS2 9JT, UK  Fax: (UK) 0532 335411 (FAO Ros Whysall)
******************************************************************
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU