This is the concept of the auth system. The hash is always different.
Only chatbots will accept dcc/msg authing/cmds.

Authing for DCC:

[bot] password?
[you] yourpass
[bot] -Auth i/P"R2*Go1)Cij8$-1tvT&5-8d36/bA3(E.1tHl+s4#2FqNpxg botnick

Now, at this point, you need to know your SECPASS from the bot and the AUTHKEY.
These can be obtained by asking your admin.
Then you would MD5 the three elements together:
  1. i/P"R2*Go1)Cij8$-1tvT&5-8d36/bA3(E.1tHl+s4#2FqNpxg

MD5: i/P"R2*Go1)Cij8$-1tvT&5-8d36/bA3(E.1tHl+s4#2FqNpxgSECPASSAUTHKEY
The hash comes out to be: 8f783879950efd3e71b7de188ebfa1ad
You then paste this back to the bot like so:

[you] +Auth 8f783879950efd3e71b7de188ebfa1ad

If you used the correct SECPASS and AUTHKEY, then it will grant you access.

Authing over IRC is much similar:

/msg bot auth?
[bot] auth. botnick [if the bot responds with "auth!" then your host is not added, this will be used in the future.]
[you] auth yourpass
[bot] -Auth i/P"R2*Go1)Cij8$-1tvT&5-8d36/bA3(E.1tHl+s4#2FqNpxg botnick
From here, the hash is made as described earlier
[you] +Auth 8f783879950efd3e71b7de188ebfa1ad
[bot] -notice- You are now authorized for cmds, see +help

You remain authorized for the following commands until you haven't used a cmd for 60 minutes or when the bot reconnects.

MSG/CHAN cmds (as of version 1.0.10 9/25/03):
[you] +help
[bot] op invite getkey voice channels test
Usage for cmds:

+op/+voice can be used in both channels and msgs.

+voice is same syntax as +op.

In msg:

In chan:

+invite is msg only.

+getkey is msg only.

+channels works in both msg and channel

Now that you have read all of that you deserve some scripts ;)

Type /helpauth in these for further instructions.

Any script without a link is in progress, expect it shortly.
Seeing how the script SHOULD operate, maybe you could write one yourself for your client? ;) [make sure to send it to me so I can post here]

Until then, use this to generate the hashes (Compilable md5 executable for *nix)