See the CHANGES below. The two big ones are the addition of the server_
and client_ printcap entry support and the SSL authentication.
If you have any problems or issues with this release, please send me
a report ASAP as I am trying to make this the next 'stable' release,
and do not want to put any more 'extensions' or additions into the
3.8.X release.
Patrick
Version LPRng-3.8.13 - Mon Jul 22 09:07:57 PDT 2002
Major Enhancement In Printcap and Configuration Functionality
After much consideration, added the 'client.xxx' and 'server.xxx'
facility. Briefly, if you have a printcap entry of the form
client.xxx or server.xxx then this can be used to set the corresponding
xxx variable when the printcap entry is used by the lpd server
or the LPRng client programs lpr, lpq, lprm, checkpc, etc.
Entry Program Type Sets
server.xxx = vvv lpd (server) xxx = vvv
client.xxx = vvv lpr,lpq... (client) xxx = vvv
The purpose of this enhancement is to allow a single printcap
entry to be used for both client and server operation, especially
in situations where the lpd server is forwarding or sending jobs
to another lpd queue.
Example of use:
lp:
# used by clients, forcess them to send to
# specified server
:[EMAIL PROTECTED]:force_localhost@
# used by lpd server
# the server will now send jobs to the
# specified destination
:server.lp=%P@destination
This is equivalent to and replaces the :client and :server
printcap flags, as shown below:
lp:client
:[EMAIL PROTECTED]:force_localhost@
lp:server
:lp=%P@destination
This selection operation also works with values in the
lpd.conf file, allowing global overrides for clients and
servers. (I can't imagine a use for this, but it is there
if somebody wants to use it.)
The lpc client and lpc server commands will display the
selected client.xxx and server.xxx values. They are also
propagated to the PRINTCAP_ENTRY environment variables
for filters.
Typo's in documentation corrected.
(Patch by: Stepan Kasal <[EMAIL PROTECTED]>)
lpr Kerberos authentication failures were not being reported.
(Problem noticed by: Rick Cochran <[EMAIL PROTECTED]>)
Added SSL authentication. See the README.SSL.SECURITY file for
the truly complicated details. Note that testing with certificates
signed by non-root CA indicates that the client is not sending
a certificate, even though one has been requested and the
certificates and signing certs are in the right places.
lpd.conf did not have 'include' functionality working.
(Patch by: Stepan Kasal <[EMAIL PROTECTED]>)
Added Yet Another LPRng Option: user_is_authuser
user_is_authuser:
if( header_info && User_is_authuser_DYN
&& (s = Find_str_value(header_info,AUTHUSER,Value_sep)) ){
Set_str_value(&job->info,LOGNAME,s);
DEBUG1("Check_for_missing_files: authuser '%s'", s );
}
printcap:
lp:auth=kerberos5:user_is_authuser:...
Causes the principle name to be used as the user name.
lpq_in_perl was screwed up
(Patches by: Anthony Thyssen <[EMAIL PROTECTED]>)
generate_banner core dumped. Turned out not to be setting
banner format ("f") when generating entry, so that control
file generation core dumped when generating new control file.
(Problem reported by: "Keith Rinaldo" <[EMAIL PROTECTED]>)
Updated Remove_done_jobs to sort jobs by completion time.
Added 'Set_nz_flag_value' function to stop the ERROR_TIME value
from being gratuitously updated by various routines.
Found possible cause of 'job data files not removed' problem
in the Remove_done_jobs() code. There is a possibility of a
data file being orphaned if a 'done job' is removed by the
spooler at the same time that another processes such as lpq
information gathering examines the print job. Rare, but possible.
Put warnings in the LPRng-HOWTO section on Samba about the
done_jobs option and interaction with SAMBA job status.
(Suggested by: Marcus Manske <[EMAIL PROTECTED]>)
Added yet another wakeup and kick to the master server process
so that printer pools will respond faster. Sigh...
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
