🚀 go-pugleaf

rvh@diva.dgk.ruu.nl (Rudi van Houten) writes:
: We compiled popper on a RS/6000, and it runs OK. But we didn't
: succeed in making a connection. It was always rejected on wrong
: password. We assume that popper doesn't know of password shadowing
: (but we didn't scan the code). Anyone has a clue on this aspect?

I'm running popper 1.831beta here without problems at all, currently
on RS6000 AIX 3.2.2, but also 3.1.5.

(1) build it with CC=bsdcc (see /usr/lpp/bos/bsdport)
(2) defines are -DBIND43 -DHAVE_VSPRINTF -DBIT_ZERO_ON_LEFT
(3) in /etc/inetd.conf, popper must be run under user 'root' in order
    to get the password out of the shadow password file.  Otherwise
    an undecodable '*' is returned.  See the AIX man-page for getpwnam(3).
    Most daemons (other than finger, which is a security hole) run as
    root from inetd.conf.  A typical entry would be:

pop3 stream tcp nowait root /usr/local/etc/popper popper

You probably have to add 'pop3 110/tcp' to /etc/services too, run inetimp,
and if you're running Yellow Plague (NIS) then remake that, too.
--
Doug Sewell, Tech Support, Computer Center, Youngstown State University
doug@cc.ysu.edu	   doug@ysub.bitnet	<internet>!cc.ysu.edu!doug
"Recession: your friend loses his job.  Depression: you lose your job.
Recovery: Bush loses his job" - Bill Davidsen

In article <rvh.720176634@P9070b> rvh@diva.dgk.ruu.nl (Rudi van Houten) writes:
>We compiled popper on a RS/6000, and it runs OK. But we didn't
>succeed in making a connection. It was always rejected on wrong
>password. We assume that popper doesn't know of password shadowing
>(but we didn't scan the code). Anyone has a clue on this aspect?

Which version are you using?  popper 1.831beta has shadow support available
as a configuration option.  Don't recall when it entered the code.

From article <rvh.720176634@P9070b>, by rvh@diva.dgk.ruu.nl (Rudi van Houten):
> We compiled popper on a RS/6000, and it runs OK. But we didn't
> succeed in making a connection. It was always rejected on wrong
> password. We assume that popper doesn't know of password shadowing
> (but we didn't scan the code). Anyone has a clue on this aspect?

I have code to do this on DEC Ultrix with shadow password if anyone
is interested.

While I'm on the subject, are there any papers on how pop works around
anywhere? I am trying to get nupop at the moment, and eudora later,
to work without ethernet or slip through Rudi's srialpop shell.
Anyone else have this working with pc pop clients?

-- 
Dave Rasmussen - SysAdm/Hacker/Consulting Manager, UWM Computing Svcs Div.
Internet:dave@uwm.edu, Uucp:uwm!dave, Bitnet:dave%uwm.edu@INTERBIT
AT&T:414-229-5133 USmail:Box 413 EMS380,Milwaukee,WI 53201  HAM: N9REJ       

Has anyone ported popper to a system V system lacking thr ftruncate()
system call?

If so, is source or diffs available?

Thanks,

-- 
John Alsop

Sea Change Corporation
6695 Millcreek Drive, Unit 8
Mississauga, Ontario, Canada L5N 5R8
Tel: 416-542-9484 Fax: 416-542-9479
UUCP: ...!uunet!uunet.ca!seachg!jalsop  jalsop@seachg.com

In article <1992Oct29.183551.1541@seachg.uucp> jalsop@seachg.UUCP (John Alsop) writes:
>Has anyone ported popper to a system V system lacking thr ftruncate()
>system call?
>
>If so, is source or diffs available?
>
Yes it has been done.  I'm running 1.831beta under such conditions.  There
are two ways to get around this problem.  Roll your own ftruncate() or grab
one from one of the various portable packages that includes one.  Jeff Roth
at the Defense Logistics Agency wrote the one that I use.  I can't seem to
find one in the packages that I thought had it :-(

You can reach Jeff at jroth@dsac.dla.mil

--
LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.3     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
CMC TCP/IP for 3B2 V 2.6.1      |