[EMAIL PROTECTED] wrote:
Marc,
we guess there is no one.
Sreeram said, that he earns a lot of money with projects for industry and Jethuu Rao is even not reading the list here, as he has another project already for tachion. Sreeram wanted to employee a python (jython java) developer for cspace. But I guess it is not done, as it is an invest in open source.
What we need from content:
Just to set the record right,
- Cspace is not decentral, it needs a tachion server for creating an RSA key
and it needs the Cspace-ID for the taychion server to launch the application.
We need to change this.
Though there is a hint of truth to what you're saying, its not entirely
true. This is probably the 3rd time I'm explaining this on cspace-users.
The central server is there just to maintain a persistent mapping
between the Public Keys and the key-ids. There was no way we could
implement atomic increments (like an autoincr field in a DB) securely in
the DHT, and thus we had to use a centralized server for this. This does
not compromise the security of CSpace in any way. This one time
registration process with the can be made optional, and we haven't made
it yet. As with any open source project, patches are always welcome :-)
And the application does not need to connect to the central server,
every time its launched. The central server is only used after creating
a new key pair and while adding a new user with a keyid (you can always
enter the public key directly and avoid the connection to the central
server)
- The question for security is as well, if you permit user "sreeram", if then a
fake could use VNC or your PC, so the RSA-Key has to be inserted into the permission and
not the nicname.
This simply is not possible because of the following constraints:
All nick names in a users buddy list are guaranteed to be unique
For any new user whose pub key is not in the user's buddy list,
CSpace adds a "unknown-" prefix to his nickname
So, if I create a user with a nick "sreeram" and try connecting to your
machine, my nick will be "unknown-sreeram" and the permission rules
wouldn't match.
- We could have Videochat, VOIP or Multi-user-Chatrooms in.
- As well filesharing with the edonkey-hash system woulöd be nice.
At the moment Developer TAZ promised to make a linux source file and spec file,
but he has problems with his machines, dunno, we get here a linux PC for 200
euros.
We need to check, if the linux messernger is running on suse, fedora, debian,
and ubuntu.
then end of january we need the linux source for the fedora 7 release.
The plan is to add all extra packages to the fedora core and give the
distributioin to the users. so... the development will slow down and we need to
get it in. As well Fedora ias the basis for the laptop.org project, where
millions of them are shipped... and they still have no open source messenger
added..
Hope TAZ can create a source file...
Third, there is high interest to port cspace to java, so it is independent from
platforms. See the jython.org newsletter for january 2007, there are already
some coders starting..
The rest is not developed, until sreeram lays his hands on it.
Regards
-------- Original-Nachricht --------
Datum: Wed, 10 Jan 2007 17:12:30 +0100
Von: "Marc Nürnberger" <[EMAIL PROTECTED]>
An: [email protected]
Betreff: [cspace-users] Roadmap
Hello everyone,
I was wondering if there is some kind of roadmap for cspace. It would be
nice to know on what the devs are currently working and which features
are going to be implemented in the next or later releases. I would look
into the source code for changes, but i'm not confident with python. And
I think there are a lot people like me who are not. :)
Greetings
Marc Nuernberger
_______________________________________________
cspace-users mailing list
[email protected]
http://tachyon.in/cgi-bin/mailman/listinfo/cspace-users
_______________________________________________
cspace-users mailing list
[email protected]
http://tachyon.in/cgi-bin/mailman/listinfo/cspace-users
