Well one last option along those lines is to simply require identd, which
there is already a patch for.
Well the patch retrieves and displays information from the identd daemon on
the client computer, but doesnt
demand it be there, though that's easy to hack.
The difference there is that there are identd programs already done, and
freely distributable for windows, macs, and linux (All linux for the most
part already have ident going).
The downside, is a user on a windows box can pretty much straight out lie
and fill in any username they want, thus you aren't really gonna stop anyone
with it.
That's what IRC servers use btw. MIRc has an identd daemon built into it as
many IRC servers wont let you connect
unless your computer responds to an identd request,
The long and short... good point... you'd have to compile a version for
different operating systems. If it were strictly a command line program
written in C then that same C code would compile on the different platforms
easy enough.
What's harder, is coding it to see what OS its on, and use whatever method
is appropriate to pluck the unique info off the users computer to verify who
they are.
On Unix have have the uname() call and the getuid() calls, windows API
provides a registry to dig through for computer name and usernames, macs?
Beats me what they provide.
----- Original Message -----
From: Mike Bentley <hansolo@io.com>
To: <CIRCLE@post.queensu.ca>
Sent: Monday, January 10, 2000 4:17 PM
Subject: Re: [CIRCLE] Hmm, a general question...
> On Mon, 10 Jan 2000, Ron Hensley wrote:
>
> > The one thing that comes to mind thats potentially viable is to write a
> > small application that the user has to run on their own computer which
> > sends over the name and password they were assigned.
> >
> > If done in Visual Basic or Visual C, you could also pluck the Windows
> > Computer name and perhaps Windows CD OEM number from their registry and
> > send it along.
> >
> > So the user has to be running this small client application when they
> > connect to your mud. When they connect, you code the mud to connect back
> > to them on the port your APP is supposed to be running on. If it can't
> > connect, you display some sort of banner informing them that it has to
be
> > running and where to get a copy.
> >
> > If its running, you get back the name, pass, computer name, OEM and you
> > compare that to some database you maintain. If some hoser tries to
create
> > a second account with a different name and password, your code would see
> > that his/her computer name and windows CD OEM is already associated with
> > some other account, and you dont let them in.
> >
>
> Thats an interesting thought, but what about people that aren't
> gettign to the mud from a Windows machine? I know whenever I mud I telnet
> in from a Unix machine. So therefore I wouldn't be able on this mud from
> a Unix machine because I wouldn't beable to run this client? Just a
> thought...
>
> Mike Bentley
> hansolo@psychoticdreams.com
>
>
> +------------------------------------------------------------+
> | Ensure that you have read the CircleMUD Mailing List FAQ: |
> | http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
> +------------------------------------------------------------+
>
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 04/10/01 PDT