> From [EMAIL PROTECTED] Wed Oct  8 18:55:34 2003
> Date: Wed, 8 Oct 2003 21:55:09 -0400 (EDT)
> From: Geoff Greene <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: LPRng bugs
>
>   This message is in MIME format.  The first part should be readable text,
>   while the remaining parts are likely unreadable without MIME-aware tools.
>   Send mail to [EMAIL PROTECTED] for more info.
>
> --8323328-168535227-1065664509=:8057
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> I've found that using LPRng 3.8.22 from slackware 9.1 with OpenSSL
> 0.9.7c corrupts data in transfer, randomly adding the character '@'
> (ascii 64) throughout the data when using auth_forward=ssl.  I found a
> line of src/common/ssl_auth.c that looked to me to be a bug (patch
> included) that could potentially be responsible for the corruption I was
> seeing.  I haven't done any testing yet, since I don't really have time
> to recompile, install and test it right now, but based on reading the
> man page of SSL_read, it seems like the way things should be.
>
> Another non-critical problem I was seeing was that when using
> auth_forward=ssl, the ssl_id,ssl_forward_id, and ssl_default_client_name
> options were all required for the printcap entry, despite the fact that
> they don't seem to actually do much of anything useful.  I had to peruse
> the source code to find out that I had to add those entries to printcap,
> since I couldn't find them mentioned in any documentation.
>
> Thanks,
> Geoff Greene
> --8323328-168535227-1065664509=:8057
> Content-Type: TEXT/PLAIN; charset=US-ASCII; name="ssl_auth.c.diff"
> Content-Transfer-Encoding: BASE64
> Content-ID: <[EMAIL PROTECTED]>
> Content-Description: 
> Content-Disposition: attachment; filename="ssl_auth.c.diff"
>
> LS0tIHNzbF9hdXRoLmN+CTIwMDMtMDktMDUgMTY6MDc6MjAuMDAwMDAwMDAw
> IC0wNDAwDQorKysgc3NsX2F1dGguYwkyMDAzLTEwLTA4IDIxOjAxOjAyLjAw
> MDAwMDAwMCAtMDQwMA0KQEAgLTY1OCw3ICs2NTgsNyBAQA0KIAlDbGVhcl90
> aW1lb3V0KCk7DQogCXN3aXRjaCggU1NMX2dldF9lcnJvciggc3NsLCByZXQg
> KSApew0KIAkJY2FzZSBTU0xfRVJST1JfTk9ORToNCi0JCQkqbGVuID0gbjsN
> CisJCQkqbGVuID0gcmV0Ow0KIAkJCWJyZWFrOw0KIAkJY2FzZSBTU0xfRVJS
> T1JfWkVST19SRVRVUk46DQogCQkJc3RhdHVzID0gMTsNCg==
>
> --8323328-168535227-1065664509=:8057--
>

Right you are.  It is a bug.  The following is a quick
outline of the general keys.  This has been added to the
Reference Manual (AKA the HOWTO).

# AUTHTYPE is the authentication method -
#  kerberos, ssh, pgp, etc, as described below
authtype=AUTHTYPE  - authentication to be used
                     kerberos, pgp, md5, none, etc
AUTHTYPE_path      - the pathname of a program to be used to support
                     this form of authentication.  For example,
                     for pgp, this would be the pathname of the
                     pgp program
AUTHTYPE_id        - the identification of the server for the
                     authentication method.  For example, the
                     kerberos principal for the server, the PGP
                     key id for the server, and so forth.
AUTHTYPE_server_key - location of a file on the server where a key
                     used to unlock or encrypt a message is kept.
AUTHTYPE_forward_id - the identification of the remote destination,
                    This is used by the server when forwarding a
                    job to a remote destination.  By default, the
                    AUTHTYPE_id value is used by the server as its
                    identification.
AUTHTYPE_default_client - when forwarding a job and the job arrived
                    via an unauthenticated method,  use this as the
                    default client identification. This will
                    be the A record value in the control file.


-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------

Reply via email to