<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
If you just want the string that identifies the type of client, so you
can use it in region modules, that may be easy to add. But if you want
to add different login procedures, that's a whole other matter... I
just did that, and I'm not happy with the result. We really need to
have a plugin architecture in place for these servers so that we can
start doing these kinds of things systematically and and in an
extensible manner, just like with region modules.But, as MW said a few
days ago, we're less than half-way there. :-/<br>
<br>
James Stallings II wrote:
<blockquote
cite="mid:170fa1780903240936rf01e99albf54d9ff781438ee@mail.gmail.com"
type="cite">Greetings All :D
<div><br>
</div>
<div>I have a need to do some processing of what I will call the
'client signature', or that bit of data that the client sends to
identify itself at login (Version, Channel, and Platform).</div>
<div><br>
</div>
<div>Presently, the only thing done with this information is that it
is logged on the User Server log.</div>
<div><br>
</div>
<div>I am a beginning C# programmer as I am sure many of you know,
though no stranger to programming in general; I am also more than
passingly familiar with the OpenSim source code. That said however, I
have to this point only stretched my C# wings in region modules, and as
this is a fairly central piece of OpenSim, felt it incumbent upon me to
broach this topic here before starting to work on what might be a patch
that many are interested in, thus giving the community an opportunity
to provide guidance and input to the effort.</div>
<div><br>
</div>
<div>Basically, what I'd like to do is provide some functionality to
support a 'black box' of client processing; facilitating optional and
arbitrary login processing in addition to authentication.This will
provide opportunities for grid operators to more proactively manage
connections to their grids based on the strings sent by the client,
including such applications as cryptographic client signing, filtering
of undesirable clients, detailed logging for business purposes, etc.</div>
<div><br>
</div>
<div>My first intuition is to produce a patch to the user server
proper, but if it would be more appropriate to do so, if a server
plug-in or add-in is possible, that is likely the way to go.</div>
<div><br>
</div>
<div>I eagerly look forward to your suggestions and criticisms.</div>
<div><br>
</div>
<div>Cheers!</div>
<div>James/Hiro/daTwitch</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
-- <br>
===================================<br>
<a moz-do-not-send="true" href="http://osgrid.org">http://osgrid.org</a><br>
<a moz-do-not-send="true" href="http://del.icio.us/SPQR">http://del.icio.us/SPQR</a><br>
<a moz-do-not-send="true" href="http://twitter.com/jstallings2">http://twitter.com/jstallings2</a><br>
<a moz-do-not-send="true" href="http://www.linkedin.com/pub/5/770/a49">http://www.linkedin.com/pub/5/770/a49</a><br>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Opensim-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>