automatically set up client?

[bill]

I'd like to automatically setup a client from the command line. At first I was going
to make 2 directories per dual machine, then make a symbolic link to mod_user.xml
which would be shared among all clients.

I was surprised to find no email address stored in the file, and what looks like the starting
points for the search, thus I assume it would be bad to share across clients.

So say I had a bunch of duals what would be a good approach to set them all up for
an email address and a proxy? Hopefully without any per client work. With dnetc I
just make a symbolic link to the dnetc and dnetc.ini and all the per client
info is in the directory (work units downloaded, uploaded, logs, etc).

Currently from what I can tell I have to run the client, answer a few questions,
then submit the mod_user.xml info via a form. Not too much of a bother
for a few machines, but not very reasonable for many.

Am I missing something?

[jlcooke]

Originally posted by bill
I'd like to automatically setup a client from the command line. At first I was going
to make 2 directories per dual machine, then make a symbolic link to mod_user.xml
which would be shared among all clients.

I was surprised to find no email address stored in the file, and what looks like the starting
points for the search, thus I assume it would be bad to share across clients.

So say I had a bunch of duals what would be a good approach to set them all up for
an email address and a proxy? Hopefully without any per client work. With dnetc I
just make a symbolic link to the dnetc and dnetc.ini and all the per client
info is in the directory (work units downloaded, uploaded, logs, etc).

Currently from what I can tell I have to run the client, answer a few questions,
then submit the mod_user.xml info via a form. Not too much of a bother
for a few machines, but not very reasonable for many.

Am I missing something?

I should have added something to http://www.md5crk.com/?sec=client_readme .

As it stands now, the 1.0.7 client and make your life A LOT easier:
http://www.md5crk.com/dl/CHANGELOG.txt


Originally posted by CHANGELOG
- new md5_preset.xml file is consulted at startup to auto-upload your startpoints. Usful for installing in computer labs. Format:
<md5crackPreset>
<proxy>10.1.1.1:8080</proxy>
<address>jdoe@isp.com</address>
</md5crackPreset>
[/B]

I'll add this to the advanced and client-readme sections now.

:spank: NOTE!!! :spank:
Do not use the same md5_user.xml file. This file must be independently generated for each md5crk instance. The md5_preset.xml file should be all you need for mass-deployments.

[bill]

I tried it and I get:
Don't forget to run md5_user_send.html to get credit for your efforts
=================
Mon Jul 5 05:56:30 2004
Could not automatically submit md5_user_send.html file.
Try it manually.

Does that mean my proxy isn't working?

What is the best way to submit 60 ish md5_user.xml files?

Can I just cat them together and submit them as 1?

[jlcooke]

The error means one of two things:
a) you gave an email address that has not yet been registered to a user/password. So you need to create a md5crk login then populate the md5_preset.xml file accordingly.
b) communicating with your proxy didn't work. Make sure you put in "proxy.company.com:8080" and not "http://proxy.company.com:8080/".

As for registering DPs "a la hax0r" yes cat them together like this:

<md5crackUser>
<core>X86SSE2ALU2</core>
<proxy />
<minWorkUnitSize>200</minWorkUnitSize>
<!-- splice in machine A -->
<startPoint1>AAAAADRqzbSQSj5cXmPMRg--</startPoint1>
<startPoint2>AAAAANmVbQqn0c2upV/nFg--</startPoint2>
<startPoint3>AAAAAATgwudHdU3mtfxHIw--</startPoint3>
<startPoint4>AAAAAAXbLcGVPmQbY1JvSQ--</startPoint4>
<startPoint5>AAAAAA7nAUkLCXDgGCy4aQ--</startPoint5>
<startPoint6>AAAAAGrjQjXUme7ckOL8ww--</startPoint6>
<!-- splice in machine B, start numbering from startPoint7 not startPoint1 -->
...
<!-- splice in machine C -->
...
.
</md5crackUser>