On Wed, 2003-08-20 at 10:37, Peter Palmreuther wrote:
> > Is there docs on running vchkpw so I could see how it works ? Yes, the
> > code does have bits & pieces like;
> > 
> >  printf("vchkpw: what the hell are you doing running vchkpw on the
> > command line!! It's only for talking with qmail-popup and
> > qmail-pop3d.\n");
> 
> printf "[EMAIL PROTECTED]" | \
>  strace -f -s 4096 -o /tmp/vchkpw.log ~vpopmail/bin/vchkpw /bin/true 3<&0
> 
> and search for a "chdir" system call in '/tmp/vchkpw.log'.
> If you're not on Linux but e.g. *BSD use 'truss' or anything else that
> enables you to trace system calls.

 Thanks for a speedy reply!

 OK, as expected, that looks like it's working fine;

6485  chdir("/hsphere/local/var/vpopmail/domains/hosting365.ie") = 0
6485  getcwd("/var/vpopmail/domains/hosting365.ie", 156) = 36
6485  getpid()                          = 6485
6485  brk(0x8057000)                    = 0x8057000
6485  open("/hsphere/local/var/vpopmail/domains/hosting365.ie/vpasswd.cdb", O_RDONLY) 
= 4

 down the end, it has;

6485  munmap(0x40015000, 4096)          = 0
6485  getpid()                          = 6485
6485  rt_sigaction(SIGPIPE, {0x420e46e0, [], 0x4000000}, {SIG_DFL}, 8) = 0
6485  socket(PF_UNIX, SOCK_DGRAM, 0)    = 4
6485  fcntl64(4, F_SETFD, FD_CLOEXEC)   = 0
6485  connect(4, {sin_family=AF_UNIX, path="/dev/log"}, 16) = 0
6485  send(4, "<21>Aug 20 10:42:22 vpopmail[6485]: vchkpw: password fail [EMAIL 
PROTECTED]:", 77, 0) = 77
6485  rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0
6485  _exit(3)                          = ?

 Which, as I mentioned is strange, as courier imap authenticates off the same vpasswd 
file...

John

Reply via email to