SUMMARY: pop3 and C2

Thanks Ann.
>From your recommendations, I found out that a few
users had u_newcrypt at 2, while others had zero (0).
Correcting that has everyone happy in new qpopper.

Richard

--- Ann Majeske <[email protected]> wrote:

> Maybe the problem is with the encryption method.
> Enhanced Security has a few different built in
> encryption methods and it also has the capability
> to allow the system administrator to add their own
> encryption methods.  Maybe pop3 doesn't recognize
> the encryption method in use on your system.
> 
> Use edauth to look at the value of u_newcrypt in 
> the default file (edauth -d d default).  This is the
> encryption method used to encrypt new passwords
> on the system.  It can also be overridden on a per
> user basis by putting it in the user's
> authentication
> database entry (edauth -g <username> to see if
> it's been defined for that username).  The
> u_oldcrypt
> value in each user's authentication database entry
> is the encryption method used to encrypt the current
> password for that user.
> 
> The default crypt value for Enhanced Security is 0 
> which is  bigcrypt.  The crypt values currently
> defined in Enhanced Security (from
> /usr/include/prot.h:
> 0   AUTH_CRYPT_BIGCRYPT
> 1  AUTH_CRYPT_CRYPT16
>     This one uses crypt16().
> 2  AUTH_CRYPT_OLDCRYPT
>     This one uses crypt() like base security, but
> puts the 
>     result in the Enhanced Security authentication
> database 
>     instead of /etc/passwd.
> 3  AUTH_CRYPT_C1CRYPT
>     This one uses crypt(), but puts the result in 
>     /etc/passwd even though you're running Enhanced
>     Security.  This attempt at a hybrid between
> Enhanced
>     and Base security wasn't implemented very well,
> I 
>     wouldn't recommend trying this!
> 
> If the u_newcrypt value is a negative number it is
> something that has been added by your system
> administrator, you'd have to ask them what it is.
> 
> If you're having trouble getting pop3 to recognize
> Enhanced Security passwords you could try changing 
> the encryption method for one user to each of the 
> above values (then change their password so that the
> 
> password is actually using the encryption method, 
> check that u_oldcrypt for that user is the same as
> the 
> u_newcrypt value you're trying) and then see if you 
> can get that user to authenticate with pop3.
> 
> Just an idea, may not have anything to do with your
> problem.
> 
> Ann
> 
> ----- Original Message ----- 
> From: "Ricardo (Tru64 User)" <[email protected]>
> To: <[email protected]>
> Sent: Wednesday, July 27, 2005 2:26 PM
> Subject: pop3 and C2
> 
> 
> > Hi All,
> > A followup to my own post 4 yrs ago. Still running
> > some tru64 v4.0g servers....problem with
> > qpopper-4.0.8, does not seem to like sia
> > passwords....even though i used ./configure
> > --enable-specialauth as in previous versions, this
> > time it is not working. 
> > Any ideas?
> > 
> > _Thanks
> > 
> > Richard
> > 
> > 
> > --- Tru64 User <[email protected]> wrote:
> > 
> > > Date: Wed, 07 Nov 2001 06:39:28 -0800 (PST)
> > > From: Tru64 User <[email protected]>
> > > Subject: SUMMARY: pop3 and C2
> > > To: [email protected]
> > > 
> > > Hi 
> > > Thanks...........3 seconds later, saw this
> > > 
> > > ./configure --enable-specialauth 
> > > 
> > > in TFM
> > > 
> > > well, its all good.
> > > pop3 works once again.
> > > 
> > > --- Tru64 User <[email protected]> wrote:
> > > > Hi Guys,
> > > > Might be simple to many, but hey....
> > > > I downloaded qualcomm qpopper4.0.3 as
> suggested in
> > > > many previous posts to overcome c2 issues. The
> > > post
> > > > below suggests adding -DAUTH to the Makefile.
> > 
> > 
> > 
> > 
> >
> ____________________________________________________
> > Start your day with Yahoo! - make it your home
> page 
> > http://www.yahoo.com/r/hs 
> >  
> > 
> > 
> 
> 



		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs