On Tue, Jun 17, 2003 at 09:13:04AM +0200, Florian Zschocke wrote:
> [EMAIL PROTECTED] wrote:
> reserved slot access and want to join into a reserved slot. In
> this case the server needs to have your password while you join
> (not after it) and that is why you have to set it in the client's
> setinfo buffer. The suggested method to do this is to create a
> file in your dod directory (on the cient!), e.g. adminpass.cfg.
> 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
Hmmm...
When I do that, it still doesn't work.
> > I have a file called 'autoexec.cfg' in the dod directory. I
> > cannot get it to execute.
>
> I have a autoexec.cfg file for a Linux DoD server and it works
> fine. You may want to add some diagnostic output to the file which
> will be displayed in your server console to check if it is
> executed. You can find an eample in the stock adminmod.cfg file.
Oh, the autoexec.cfg file is on the client side.
> > I enter the setinfo manually I can authenticate, but I'd prefer
> > to use crypted passwords, and those can be tough to remember.
>
> The encrypted password goes into the users.ini file. It is
> encrypted so that noone can snoop it from the file. That, of
> course, is only a minor protection since bad passwords can be
> cracked within a few minutes with John and friends.
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 client uses plaintext passwords. You don't log into a unix
> machine with the encrypted password either, do you? :)
I said that as a joke.
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. However *this* NT box is more secure because it's behind
a firewall, and has no inbound services routed to it (and i use
it only for games and SSH at this point) so it's fairly secure.
> > (2) how do I set the server to automatically log? I cannot find
> > the instructions for this.
>
> The command is "log on". The best place is the autoexec.cfg file.
> Do not put it into the server.cfg file since that will mess up
> your logging. If your autoexec.cfg file doesn't work, then you can
> add it to the commandline with +log on.
Fuck me raw.
Creating the autoexec.cfg file on the server (in dod) and
putting log on in it worked a fucking charm. Now I've got
output in the logfiles.
Thanks. One problem down.
> Florian.
You're not Romanian (as in in Romaina) are you?
--
"Sure, nine out of ten people would want a Harley if you asked them,
but then again, nine of ten people don't know shit about bikes."
-JGullato
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
