Re: [tpop3d-discuss] Compilation trouble on Solaris

[Martin Schmitt]

* Chris Lightfoot wrote/schrieb:

> > What I need is a separate password base for POP3. I'm far from sure about
> > the implementation, but I'm currently favouring a user-maintained
> > "$HOME/.mailpass" that they may update through some custom Perl scripts
> > which check for example if they really aren't using their Unix password for
> > POP3 authentication. 
> 
> Take a look at scripts/dotapopfile, which (with a simple
> tweak) should do exactly what you want.

First of all, thanks for this pointer. 

Since I found that the nested if{}'s make dotapopfile a tough read, I
basically re-did the whole sub()-Block in my own words, made it compile
under strict and kept the supporting stuff from the original script. I have
no idea, how and why this stuff works. I see "@ISA" and go to full dummy
mode in an instant. ;-)

Good god. I need to get a clue wrt OOP.  

So here is what I produced so far:
        http://www.trash.net/~martin/dotpop-secret.txt

The bad news: It doesn't work. Some values for user and pass fields seem to
be carried over between connection attempts. Ocassionally, it will accept
connection with complete bogus credentials, apparently carried over from
the last valid authentication. Other times, it denies access to valid
users, though the credentials are correct, most likely for the same reason,
just the other way around. 

I've added the "password-zeroing" line from dotapopfile, but that didn't 
change anything. I think it's a problem with invocation and my lack of clue 
regarding the OOP stuff. All the variables inside the block should be
lexically scoped only to this block and on next turn, everything should be
clean, from my point of view, so the old data can only come from the data
that's being passed to the subroutine.

Any ideas?

Thanks,

-martin

-- 
$ cd /pub
$ more beer

pgpA98OLc0E_l.pgp
Description: PGP signature