Attachment #64786 for bug #100886

Lines 14-20 CFLAGS=-c -g -Wall -O3 Link Here

(-)cmd5checkpw-0.30.orig/Makefile (-1 / +1 lines)
14	LD=gcc	14	LD=gcc
15	LDFLAGS=-g -o ${TARGET}	15	LDFLAGS=-g -o ${TARGET}
16		16
17	default: main man cmd5checkpw	17	default: cmd5checkpw
18		18
19	main: cmd5checkpw.c conf-qmail	19	main: cmd5checkpw.c conf-qmail
20	sed s}QMAILHOME}"`head -1 conf-qmail`"}g cmd5checkpw.c > main.c	20	sed s}QMAILHOME}"`head -1 conf-qmail`"}g cmd5checkpw.c > main.c




.B cmd5checkpw
recalcuates a MD5 digest using the provided plain challenge
and the passwords from
.IR /etc/poppasswd 
and compares it with response (2nd parameter). If they are the same
then
.B cmd5checkpw


.B cmd5checkpw 
additionally compares the supplied password with the password in the 
.IR /etc/poppasswd 
file. Thus it can be used as a plain-text checkpassword
for PLAIN & LOGIN authtype (but we recommend using a crypted version for
security reasons). To use it, simply provide it with clear text password

Before invoking
.BR subprogram ,
.B cmd5checkpw
does not set up anything. Just because users from /etc/poppasswd does not
have to exist in the system so setting their uid,gid etc is not possible.

Other

applications will differ in their requirements.

.SH "FILES"
.IR /etc/poppasswd 
- this file contains pairs of logins and clear text passwords
separated by ":". It looks like this:


Lines 7-13 Link Here

(-)cmd5checkpw-0.30.orig/main.c (-1 / +1 lines)
7	#include <unistd.h>	7	#include <unistd.h>
8		8
9	#define LINE_MAX 256	9	#define LINE_MAX 256
10	#define SASLUSERFILE "/var/qmail/users/authuser"	10	#define SASLUSERFILE "/etc/poppasswd"
11	#define READONLY "r"	11	#define READONLY "r"
12	char up[513];	12	char up[513];
13	int uplen;	13	int uplen;

Return to bug 100886

Lines 26-32 and a cram-md5 challenge terminated by \ Link Here

(-)cmd5checkpw-0.30.orig/cmd5checkpw.8 (-4 / +4 lines)
26	.B cmd5checkpw	26	.B cmd5checkpw
27	recalcuates a MD5 digest using the provided plain challenge	27	recalcuates a MD5 digest using the provided plain challenge
28	and the passwords from	28	and the passwords from
29	.IR /var/qmail/users/authuser	29	.IR /etc/poppasswd
30	and compares it with response (2nd parameter). If they are the same	30	and compares it with response (2nd parameter). If they are the same
31	then	31	then
32	.B cmd5checkpw	32	.B cmd5checkpw
Lines 50-56 exits 111. Link Here
50		50
51	.B cmd5checkpw	51	.B cmd5checkpw
52	additionally compares the supplied password with the password in the	52	additionally compares the supplied password with the password in the
53	.IR /var/qmail/user/authuser	53	.IR /etc/poppasswd
54	file. Thus it can be used as a plain-text checkpassword	54	file. Thus it can be used as a plain-text checkpassword
55	for PLAIN & LOGIN authtype (but we recommend using a crypted version for	55	for PLAIN & LOGIN authtype (but we recommend using a crypted version for
56	security reasons). To use it, simply provide it with clear text password	56	security reasons). To use it, simply provide it with clear text password
Lines 68-74 interface. Link Here
68	Before invoking	68	Before invoking
69	.BR subprogram ,	69	.BR subprogram ,
70	.B cmd5checkpw	70	.B cmd5checkpw
71	does not set up anything. Just because users from /var/qmail/user/authuser does not	71	does not set up anything. Just because users from /etc/poppasswd does not
72	have to exist in the system so setting their uid,gid etc is not possible.	72	have to exist in the system so setting their uid,gid etc is not possible.
73		73
74	Other	74	Other
Lines 78-84 These effects must be documented; Link Here
78	applications will differ in their requirements.	78	applications will differ in their requirements.
79		79
80	.SH "FILES"	80	.SH "FILES"
81	.IR /var/qmail/users/authuser	81	.IR /etc/poppasswd
82	- this file contains pairs of logins and clear text passwords	82	- this file contains pairs of logins and clear text passwords
83	separated by ":". It looks like this:	83	separated by ":". It looks like this:
84		84