Key luser1.pub
Key luser2.pub
etc.

Keep in mind that names (luser1.pub, etc.) are purely arbitrary. You can use
any name you want. What matters is that file with corresponding name exists
in .ssh2 on remote.

Lets consider an example. Say you have local user luser1 who wants to use
ssh2 to log into remote system as user ruser1.

1) Run ssh-keygen2 (as luser1 on local, as ruser1 on remote).
2) Create ~/.ssh2/identification on both systems with following line:

IdKey   id_dsa_1024_a

3) Create ~/.ssh2/authorization on remote with following line:

Key   luser1.pub

4) Create ~/.ssh2/luser1.pub in home directory of ruser1 (remote user)
with contents of ~/.ssh2/id_dsa_1024_a.pub of luser1 (local user).

5) On local, copy /etc/ssh2/ssh2_config to ~/.ssh2 of luser1 and
modify it to taste. For example, you can enable ssh2 to automatically
use certain Cipher depending on the remote host name.

6) Start sshd2 on remote. On local do "ssh2 -l ruser1 Remote_System_Name".
   That should do it.

Now, if another local user (luser2) wants to use ssh2 to log into remote
system as the same remote user ruser1, s/he would do (on local) all the
steps luser1 did. Then remote user (ruser1) would do steps 3) and 4)
all over again using name luser2.pub instead of luser1.pub. When all
is finished, ~/.ssh2/authorization of remote user (ruser1) should now have
the following two lines:

Key   luser1.pub
Key   luser2.pub

Plus, there should be ~/.ssh2/luser2.pub file on remote.

That is about it.

-mk