PDA

View Full Version : Authentication Rejected?



Pascal7
07-18-2004, 08:46 PM
I was having to many problems with my patched version, so I blew it away and reinstalled fresh. Now I'm getting this error when I try to run ShowEQ from my normal account with SU access turned on.


Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
ShowEQ 5.0.0.11, released under the GPL.
SINS 0.5, released under the GPL.
All ShowEQ source code is Copyright (C) 2000-2004 by the respective ShowEQ Developers
ShowEQ comes with NO WARRANTY.

You may redistribute copies of ShowEQ under the terms of
The GNU General Public License.
See: http://www.gnu.org/copyleft/gpl.html for more details...

For updates and information, please visit http://seq.sourceforge.net/
ShowEQ 5.0.0.11, Built from 'main.cpp' on Jul 18 2004 at 22:16:52
CVS: @(#) $Id: main.cpp,v 1.33.6.3 2004/01/16 20:22:10 dohpaz Exp $ $Name: pre_5_0_beta $
Using GCC version: 3.3.2
Using glibc version: 2.3
Using Qt version: 3.2.3
Using headers from linux version: 2.6.0
Using EQItemDB: @(#) $Id: itemdb.cpp,v 1.10.6.1 2003/12/07 06:30:43 dohpaz Exp $ $Name: pre_5_0_beta $
Using GDBM: This is GDBM version 1.8.0, as of May 19, 1999.
Running on Linux release 2.6.3-4mdk for processor i686


If i run ShowEQ from root it works fine. Not sure what the hell I did. Running Mandrake 10 if that makes a difference, but never had this problem before the 7-18-patch.

Dedpoet
07-19-2004, 09:10 AM
As root, try chmod'ing your showeq executible file.

# chmod 7777 /usr/local/bin/showeq

Pascal7
07-19-2004, 05:02 PM
Nope didn't work either. :(

Cryonic
07-19-2004, 06:12 PM
First, this isn't an issue with the SEQ binary... Restore the settings for it back to 711 (rwx--x--x) to keep it from being overwritten by any other non-root user...

Amazing what you can find with Google... I typed in your exact error and found that the problem is with your X disallowing the connection to the current users X display... Couple of possible fixes:

from a terminal as the normal user that is logged in:
xhost +localhost

or here are possible reasons - xdm enable authorization for display
so now every application you want to use have to use probably
this file: ~user_name/.Xauthority

you may solve this by putting something like this in your startup
script:

export XAUTHORITY=/your/home/path/.Xauthority

Dedpoet
07-19-2004, 08:05 PM
I need to just stop answering questions. I've been gone too long... :-P