Put the setinfo line into that file, add a shortcut to your desktop for DoD and add the following to the target: +exec adminpass.cfg +connect 192.168.2.1
When I do that, it still doesn't work.
Have you tried executing the adminpass.cfg file from the client console? Does that work? What I do is have an alias: alias go "exec adminpass; connect 192.0.2.1"
Oh, the autoexec.cfg file is on the client side.
And what is in that autoexec.cfg on the client? As you are the security conscious, yo do not ever want to set the Admin Mod password in the autoexec.cfg or config.cfg files on the client. Doing so is the same like publishing it on a web page. It will set the password everytime you start the client. If you connect to a server other than the one you have admin access to, that other server now has your password.
Yeah, most of that--after all I do Unix Admin for a living. It'd
be a lot better if they'd use MD5 based hashes, but hell, it's
only a game...
The only difference is that passwords can be longer than 8 characters. But the next Admin Mod version does support MD5 hashes.
I said that as a joke.
I missed that.
See, the adminpass file, if it contains the encrypted password
makes *that* file as risky as the users.ini file on the
server--maybe even more so because it's on a *really* insecure
NT box.
True.
You're not Romanian (as in in Romaina) are you?
Nope.
Florian.
-- Want to produce professional emails and Usenet postings? http://www.netmeister.org/news/learn2quote.html
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
