[Nym3-devel] Re: Nymbaron account creation problem

[Jean-René Reinhard]

Le Wed, Nov 09, 2005 at 05:17:24PM +0100, Marco A. Calamari écrivait:
> On Wed, 2005-11-09 at 15:57 +0100, Laurent Fousse wrote:
> > Hello,
> > 
> > * Marco A. Calamari [2005-11-09]:
> > > Hi all,
> > > 
> > > I'm still trying to create an account.
> > > This is the compete log, no message
> > >  returned, and no way to resend.
> > 
> > You can resend a creation request message with the `resend-command'
> > command. For example :
> > 
> > $ nymbaron resend-command -n marcoc02 journal:0
> 
> Good, it worked. Now crossing my finger ....
> Is there any way to have something like the "used" list
>  of alias-type nymserver ?

This functionnality is not present in the nym3 protocol. The
possibility of chosing a nym already attributed is solved in the
current protocol by letting the nymuser propose a list of nyms.
 
> BTW any doc out there apart from man page & source code ...?

You can find in the subversion repository the specification of the
nym3 protocol. We are not yet implementing it fully. Except that,
there isn't any other documentation. What kind of information are you
interested in? We are aware of the lack of documentation and ready to
write more.
 
> > 
> > > marcoc at ordmantell:~$ nymbaron create
> > > How do you want to name this account: marcoc02
> > > At which server do you want to register this account: mbox:nym3 at nowwhat
> > > You need a username for this account.
> > > Enter several choices, one per line, finish by a blank line: marcoc02a
> > 
> > Indeed, marcoc02a got created.
> 
> So it not useful to repeat the create command ?

In our implementation, if the server receives the create command, if
it is properly formatted (see the protocol specification) and if it
finds a non attributed nym in the list proposed, he will create the
account and send an ack. Whether the ack is received or not won't
change anything to the state of the account on the server. Though the
ack is the only 'clean' way for the nymholder to know that the
creation of his account was successful.

> > Someone (presumably you, although of course I can't tell!)
> 
> I hope so .....  ;)
> 
> >  registered
> > marcoc too. Just to let you know that some packets reach the server.
> > We have however a major problem at the server : if the account
> > creation ack cannot be sent immediately (because of a mixminion
> > connect error for example), then the server never retries to send the
> > ack back.
> > 
> > FYI, I don't get replies for my creation request either, because some
> > server in my first SURB path is currently down. So we need to make the
> > server more robust when it comes to sending creation acks.
> 
> What happens if the server get a commend-resend of the create command
>  when the nym is already created (as in marcoc02 case) ?

The server stores at the creation of an account a hash of the
registration command. When using resend-command, you're sending
exactly the same registration command, so the server will be aware
that it has already created the account and will just resend the
ack. If you resend the registration command by reusing the nymbaron
create command, the registration command will be different (different
sequence number at least), the server will consider that the nym that was first
allocated for you is already used by someone else, and will allocate
for this registration command another nym if possible.

> Thanks a lot.   Marco
> 
> -- 
> 
> +--------------- http://www.winstonsmith.info ---------------+
> | il Progetto Winston Smith: scolleghiamo il Grande Fratello |
> | the Winston Smith Project: unplug the Big Brother          |
> | Marco A. Calamari marcoc at dada.it http:// www.marcoc.it     |
> | DSS/DH:  8F3E 5BAE 906F B416 9242 1C10 8661 24A9 BFCE 822B |
> + PGP RSA: ED84 3839 6C4D 3FFE 389F 209E 3128 5698 ----------+
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.noreply.org/pipermail/nym3-devel/attachments/20051109/d1aaace7/attachment.pgp