Hi!
> On Sun, Jun 23, 2002 at 07:19:20AM -0700, Mike Mimic
> wrote:
> > But won't that broke the use of "shadow" group?
> > Than programs which use that won't be able to read
> > it.
>
> I realised it, tried the group shadow attempt again
> and reset ownership.
> For whatever odd reason, I had t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Jun 23, 2002 at 07:19:20AM -0700, Mike Mimic wrote:
> But won't that broke the use of "shadow" group? Than
> programs which use that won't be able to read it.
I realised it, tried the group shadow attempt again and reset ownership.
For whatev
Hi!
> | But it doesn't work with Pegasus Mail.
>
> Install 'tcpflow' and watch what is sent through the
> socket. You can pipe it through 'base64-decode' to
see
> what it sends as the user/password.
I have solved the problem. I have Norton AntiVirus set
and so username wasn't correct. And it's 1
Hi!
> Originally I tried adding mail to the shadow group,
> but that didn't work, so I took mail back out of
> shadow, and chown root:mail /etc/shadow. This
worked.
But won't that broke the use of "shadow" group? Than
programs which use that won't be able to read it.
Mike
_
Hi!
--- Paul Johnson <[EMAIL PROTECTED]> wrote:
> > I have temporary set it to world readable and now
> > AUTH
>
> H! That defeats the point of shadow passwords!
TEMPORARY!!! :-) Just for debuging process.
Mike
__
Do You Yahoo!?
Yahoo! - Of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jun 22, 2002 at 05:12:38PM -0700, Mike Mimic wrote:
> I have chosen this solution and I have now trivial
> question. How can I make shadow file readable by mail
> user, too (and that it stay so because I think that
> there is some script which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jun 22, 2002 at 02:14:33PM -0500, Derrick 'dman' Hudson wrote:
> 1) Make /etc/shadow readable by the 'mail' user.
> pros: unifies shell/smtp passwords with no extra maintenance
> cons: it widens the access to /etc/shadow
>
>
On Sat, Jun 22, 2002 at 05:12:38PM -0700, Mike Mimic wrote:
| > Here are some solutions to the problem :
| >
| > 1) Make /etc/shadow readable by the 'mail' user.
|
| I have chosen this solution and I have now trivial
| question. How can I make shadow file readable by mail
| user, too
Add the u
Hi!
> Here are some solutions to the problem :
>
> 1) Make /etc/shadow readable by the 'mail' user.
I have chosen this solution and I have now trivial
question. How can I make shadow file readable by mail
user, too (and that it stay so because I think that
there is some script which check files
On Sat, Jun 22, 2002 at 02:14:33PM -0500, Derrick 'dman' Hudson wrote:
|
| Here are some solutions to the exim/auth/pam problem.
Here's some more info I should have included in the last message, if I
had remembered before I hit "send" :-).
1) I haven't tested any of the authenticators with a re
Here are some solutions to the exim/auth/pam problem.
Mark Roach pegged it -- PAM wasn't working because we were (I was)
trying to use "pam_unix.so" but didn't have permission to read
/etc/shadow.
Here are some solutions to the problem :
1) Make /etc/shadow readable by the 'mail' user.
pro
11 matches
Mail list logo
