1 |
Those error messages have been coming up in a few different posts |
2 |
round the forums as of late. It seems the lastest pam update b0rked a |
3 |
few things in terms of remote logins. Nobody has a good answer and a |
4 |
proper fix from what I have seen, but if you need to get in to the box |
5 |
do the following: |
6 |
|
7 |
Edit /etc/security/pam_env.conf |
8 |
Comment out the following lines: |
9 |
REMOTEHOST DEFAULT= OVERRIDE=@{PAM_RHOST} |
10 |
DISPLAY DEFAULT=${REMOTEHOST}:0.0 OVERRIDE=${DISPLAY} |
11 |
XAUTHORITY DEFAULT= OVERRIDE=@{XAUTHORITY} |
12 |
|
13 |
|
14 |
This may somehow be a very evil or Very Bad Thing to do security wise |
15 |
so use at your own risk; but I can say for sure that it solved my |
16 |
problem with logging in remotely. |
17 |
|
18 |
|
19 |
On Thu, 11 Nov 2004 08:37:58 -0800, Ben Munat <bent@×××××.com> wrote: |
20 |
> Hi, |
21 |
> |
22 |
> I've started seeing this repeatedly in my log/messages: |
23 |
> |
24 |
> PAM pam_putenv: delete non-existent entry; XAUTHORITY |
25 |
> |
26 |
> Anyone know what this means? |
27 |
> |
28 |
> Ben |
29 |
> |
30 |
> PS: That vpopmail entry I emailed about the other day turned out to be |
31 |
> because my brother had set up his laptop -- and a couple friends -- |
32 |
> using postmaster to send mail! Not sure why, but that explains all the |
33 |
> log entries with different IP addresses. |
34 |
> |
35 |
|
36 |
|
37 |
-- |
38 |
--------- |
39 |
Woody2143 |