[GNUnet-developers] Namespace creation

[LRN]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Right now namespace creation is synchronous (RSA key is created
synchronously).

With the changes to IPC, it now may be possible to use async RSA key
creation securely, thus making namespace creation also asynchronous.

1) Should API users be exposed to key creation? Right now they have no
idea that namespace uses RSA internally (will it be switched to ECC at
some point?). However, if we expose key creation functions to the API
users, they will be able to create a key (synchronously or
asynchronously), and then (with a new FS API function) create a
namespace around that key. That way it will not be necessary to write
yet another namespace creation function that works asynchronously (it
will be synchronous instead; async key creation will be done by the FS
API user).

2) Should namespace creation API keep the "create always" behaviour?
Right now you can only give namespace a name (key is generated
internally), and if a namespace with that name already exists, the
exiting one will be returned immediately, making the whole thing opaque.
If API users are exposed to key generation, they may also take
advantage of more transparent namespace creation from generated keys.
FS API would fail to create a namespace if another namespace with the
same name exists, UI will let user pick a different name.

3) Should namespaces have user-provided names, or is it OK to generate
their names randomly? Is namespace name (as named by user at the
moment) exposed in advertisements by default? If it is, then maybe
using some kind of generated "Namespace-XXXXXXX" name initially would
be better.
Anyway, from UI point of view it's more convenient to generate things,
since no dialogs need to be shown.
The idea is that only one namespace will be used by default, and
initially one will have to be created. Showing the namespace
management dialog (which is relatively large and multi-functional) at
the initial UI startup may not be a good idea. Just generate a key,
pick a dummy name, and be done with it. And if namespace name is not
advertised by default, it doesn't matter what it's named, and since
most users won't have more than one namespace, they won't be confused
by naming anyway.

Something like that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRH4CFAAoJEOs4Jb6SI2CwmnMH/1Q41PvAI9YTZ9RMSiqcLj5h
e8yB3kUkWM8V+OSFGg+FyS48z5+x3Wlyo9HCsPFTw591jHN4JFs/7cj7pHkP55Ns
Bj62PPtuEab2ZmZTTkbQ0FPuqO0lswFaNe+PoE5DkZXHu6rL93CDlFsH8z/LtIBc
2oYLD8VyHQrni5IOC4C3rnnKo7jf/ce54lvTLCGthw5S2usstL+P7d/Kn3ki4NHF
K6SESKe5msNNw4Pr5gyh+KMFW2j5ZJTgkyizvUz28RTW48TPLFvrruvPUGdWH6jj
D2tiVZGS7dvE9Muv3j3eITfM3qxusfbs6uSqK3HVnqtTu4aiV8vilH7ojUzL76w=
=Zc1+
-----END PGP SIGNATURE-----